LIAN PoA HCB Tokens Replay Guard Audit
Admissibility Graph · N0 → N4
N0
Intake
N1
Advisory
N2
Draft · Stage
N3
HCB Gate
N4
Execute
Awaiting request
⬡ LIAN Admission Engine
6 structural questions · sequential · deterministic
Q1Intent mapped?
Is action in admissible taxonomy?
Q2Transition in graph?
Does admissible edge exist for this path?
Q3Authority sufficient?
Does principal hold required authority class?
Q4Scope allowed?
Data/tool scope within permitted bounds?
Q5Commit/presence valid?
If required: tokens present and valid?
Q6Within risk bounds?
Transition stays in viable state space?
Token Vault
Presencenone
not issued
Short-lived · scope-bound · single use
Commitnone
not issued
Single-use · intent-bound · replay blocked
Action Taxonomy
AAdvisory · summarize · explain · draft
BBounded · write · stage · update record
CConsequence · send · publish · commit
Forbidden: N1→N4 · N0→N4 · N2→N4
Class C always requires N3 (HCB)
Commit token: single-use only
Select a scenario to begin
Scenarios
A
Summarize + Draft
ADMITTED
B
Send Email · Full HCB
HCB GATE
C
Export + Post External
BLOCKED
D
Wrong Authority
BLOCKED · Q3
E
Replay Attack
TOKEN REPLAY
Proposed Transition Object
Select a scenario
Governance Audit Log
No requests evaluated
Forbidden Edges
N1 → N4 direct execute · forbidden
N0 → N4 intake → execute · forbidden
N2 → N4 stage → execute · forbidden

Class C must pass N3 (HCB).
No model can bypass this.
No authority can shortcut this.
Five Hard Rules
Rule 1: Model has no authority
Rule 2: Model creates no path
Rule 3: Every request = transition
Rule 4: Admissibility before execution
Rule 5: Fail → path does not exist

execution_path: false
≠ "model refused"
≠ "filter triggered"
= path never constructible
Interlink Bridge
© 2026 Alexanja Senke
Architect of Admissible Autonomous Systems
AlexanjaGT5S@proton.me
doi.org/10.5281/zenodo.19138098