Delivery model¶
AI IT House separates work into clearly different concerns.
For the practical reading order—method, provider interaction and a complete case—start with How to use JAI. This page explains the delivery model; it is not a command sequence.
Why this matters¶
A common failure mode in AI-assisted work is to blur authorship, review, approval and publication into one model conversation. AI IT House intentionally avoids that pattern.
- Authors produce or analyse.
- Reviewers inspect, challenge and record findings.
- Publication editors improve audience fit without changing semantic truth.
- Approvers remain human.
This is one of the reasons the outputs are more suitable for enterprise environments.
Semantic truth vs publication¶
The platform's publication chain ensures that the final presentation can be polished without severing traceability to approved semantic content.
Consequential delivery¶
When a decision may later need defence — for example external exposure of a risky service, a residual security exception, or a high-impact architecture choice — /layered and the Justifiable Fabric preserve the full justification chain.
Two delivery modes share the same governance model¶
The current release supports both ordinary specialist delivery and fully supervised consequential delivery.
Standard specialist path¶
Use this for normal enterprise work where the full Fabric episode is not required.
Layered consequential path¶
operator intent
→ L1–L6 typed contracts
→ evidence and bottom-up review
→ bounded rework/reformulation/escalation
→ L0 authority when required
→ strict release
Use this when the organisation must later defend why a result was allowed for a particular consequential use.
The second path is not merely "more agents". Its value is the preserved requirement/evidence/authority state and deterministic recovery ladder.
Important routing boundary¶
The current release makes JAI the normative semantic architecture, but it does not claim that every direct role invocation is automatically forced through a layered Fabric engagement. Where an organisation requires that property, enforce the consequential-task classification/routing rule at the deployment entry boundary.
See Running a layered justifiable engagement for the concrete operator cycle.