LAB Technical work
Evidence lives
one level deeper.
Selected demonstrations, measurements, and methodology from AZIRE AI’s active development. Detailed enough to inspect; bounded enough not to overclaim.
01 Governed cycle
Follow one harmless request through the authority boundary.
This browser-only demonstration is illustrative. It does not contact Castor, issue real authority, run a model, or modify a repository.
“Update a README heading.”
01Conductor plansInspect
The request is classified and routed into a proposal-only workflow. Planning does not itself create permission.
workflow: smith_proposal_only02Authority narrowsInspect
Registry limits, task authorization, workflow constraints, and environment policy intersect. Authority can only become narrower.
effective = ceiling ∩ task ∩ workflow ∩ environment03HEKATE grantsInspect
A short-lived opaque grant binds the exact context and step. Redemption is checked before repository or model work begins.
status: active → consumed04Smith proposesInspect
Smith creates a patch and evidence package. The proposal may be reviewed, but it cannot silently become an applied change.
result: proposal_created05Human reviewsInspect
Forge presents the bounded proposal and its evidence. Apply, commit, and push remain separate decisions.
apply_authority: falseNo repository change. No implicit apply. Replay rejected.
02 Model Lab evidence
Models earn roles
through tests.
A bounded continuity bakeoff ran every candidate twice on the same Castor case at the same 64-token limit.
These results answer a narrow question: whether each model could satisfy this specific continuity case under identical constraints. They are not claims of general model superiority.
2 runs each · identical prompt · committed 64-token limit