Research note · how the runtime governs a workflow
High-stakes work: the runtime abstains and records — it does not decide.
In medical, legal, and financial workflows, the dangerous failure is not a wrong answer — it is a confident wrong answer with no record of how it was reached. Phionyx does not decide the clinical, legal, or financial question. It decides whether the system is competent to answer at all, makes it abstain when it is not, and signs the decision so a human can review what happened.
This is a research note on the runtime, not a product offering — Phionyx is not for sale yet. Profiles involved: Evidence Runtime, Abstention & Boundary, and the Safety Gate.
How a decision flows
- 1
Boundary check
Is this decision inside what the system can evidence? The knowledge-boundary check runs first.
- 2
Evidence sufficiency
Is the retrieved or derived evidence enough to stand behind an answer — or is it thin?
- 3
Risk class
How costly is being wrong here? The risk tier sets how strict the rest of the path is.
- 4
Hedge / defer / deny
Out of depth or under-evidenced → the system hedges, defers, or refuses — with a calibrated confidence, not a guess.
- 5
Signed record
Whatever it does, it writes a signed, hash-chained record — input, basis, verdict, and the abstention.
- 6
Human review
The record routes to a responsible human with the full handoff trail. The human decides; the system never pretends to.
What the record contains
One signed record per interaction:
- ▸The abstention decision (proceed / hedge / defer / deny, with confidence)
- ▸The evidence-sufficiency check
- ▸The human-handoff trail
- ▸The signed, replayable decision record
What it is not
- × Not a clinician, lawyer, or financial adviser — it does not produce the answer.
- × Not a correctness oracle — it cannot tell you the model was right, only what it did and whether it should have answered at all.
- × Not a replacement for the human decision-maker — the record is for them, not instead of them.
- × Not for sale — this is research from Phionyx Research.
The signed record is the Evidence Runtime; the calibrated “out of depth” is Abstention & Boundary. How a record verifies is on the evidence page.