Release inventory¶

This inventory is rendered from the canonical release manifest at .ai/runtime/_meta/release-manifest.json in the source checkout. Counts and agent identifiers are generated together during the documentation build; they are not a separately maintained catalogue. An installed runtime places the corresponding manifest under ~/.ai/it-role-house/_meta/.

Component	Registered count
Role definitions	286
Agent procedures	34
Shared skills	24
Enterprise workflow chains	24
Artifact types	28
Registered schemas	33
Renderer entries	4
Registered qualification checks	32
Provider adapters	2

Registered agent procedures¶

Agent identifier
`architecture-repository-engineer`
`artefact-governor`
`authority-liaison`
`codebase-reviewer`
`commercial-coordinator`
`defect-analyst`
`docs-author`
`document-reviewer`
`engagement-authorisation-guard`
`enterprise-publication-editor`
`evidence-rationale-reviewer`
`experiment-engineer`
`fabric-auditor`
`gate-auditor`
`l1-intent`
`l2-meaning`
`l3-policy`
`l4-design`
`l5-realisation`
`l6-evidence`
`library-approver`
`library-author`
`library-release`
`model-consistency-reviewer`
`research-analyst`
`role-advisor`
`role-author`
`role-engineer`
`role-router`
`sabsa-architect`
`sabsa-reviewer`
`sod-reviewer`
`source-docs-engineer`
`visual-quality-reviewer`

How to interpret the inventory¶

Agents are the behavioural/operator definitions shipped by JAI, including specialised coordinators and reviewers. They are distinct from business roles, which describe enterprise responsibilities and are selected through role-category skills. A listed agent is not evidence that a provider has instantiated it or qualified its isolation controls.

The qualification-check count identifies checks registered in the release manifest. It is not the total number of unit-test cases, individual assertions, provider executions or passed deployment gates. Source availability and generated configuration likewise do not establish live qualification; consult the commercial implementation matrix and validation controls for those boundaries.

For responsibilities and role selection, use Roles and disciplines and the full role catalogue. Source behavioural contracts are under .ai/agents/; their installed equivalents are under ~/.ai/it-role-house/agents/. The agent contract reference explains contract/tool-tier concepts and explicitly marks its earlier-release illustrative subset. Current canonical contracts and provider configuration determine effective permissions.

Start with How to use JAI for method selection and complete worked cases; use this page for package inventory lookup.