stratt://docs/
13 units across 5 types: chain, role, rule, supply, task
| Slug | Type | Status | Fingerprint | Description |
|---|---|---|---|---|
| doc-publish-pipeline | chain | draft | ●Verified | Three-step documentation publication chain: draft creation, quality review, and editorial gate approval. Ensures all published documentation meets accuracy, completeness, and style standards before publication. |
| editor | role | draft | ●Verified | Gate authority for the Athena council. Approves documentation for publication to external-facing channels. All external documentation must pass editorial review. |
| information-architect | role | draft | ●Verified | Designs documentation structure, navigation patterns, and content hierarchy. Ensures users can find information through multiple discovery paths — search, navigation, cross-links, and contextual help. |
| knowledge-manager | role | draft | ●Verified | Organises the documentation knowledge base. Maintains content taxonomy, cross-references, and tracks documentation coverage gaps across all domains and services. |
| reviewer | role | draft | ●Verified | Protected documentation reviewer. Enforces quality standards, technical accuracy, and consistency across all documentation. Cannot be bypassed in documentation publication chains. |
| writer | role | draft | ●Verified | Primary documentation author. Writes clear, accurate, and maintainable technical documentation including API references, architecture guides, and onboarding tutorials. |
| audience-statement-required | rule | draft | ●Verified | Every documentation page must include an explicit audience statement defining who the content is for and what prerequisite knowledge is assumed. |
| code-examples-must-compile | rule | draft | ●Verified | All code examples in documentation must be verified to compile and produce expected output before publication. |
| api-doc-template | supply | draft | ●Verified | Reusable template structure for API reference documentation pages. Provides consistent formatting for endpoints, parameters, examples, and error codes. |
| approve-editorial | task | draft | ●Verified | Final editorial gate for documentation publication. Verifies brand alignment, legal compliance, accessibility requirements, and publication readiness. Only the gate authority (EDITOR-04) can approve. |
| coverage-audit | task | draft | ●Verified | Analyse the documentation coverage across a service or domain. Identify gaps by comparing the API surface and features against existing documentation. |
| draft-api-reference | task | draft | ●Verified | Generate structured API reference documentation from source code, OpenAPI specs, or interface definitions. Produces per-endpoint documentation with examples, error codes, and authentication details. |
| review-documentation | task | draft | ●Verified | Perform quality review of documentation content. Check accuracy, completeness, code example validity, cross-reference integrity, and adherence to style guidelines. |