RENAR Reference¶
Why a reference¶
The standard is for reading sequentially and for an assessor. The reference is for targeted lookup: one term, one field schema, one checklist before an audit, one ISO 29148 trace row.
You should not arrive here "from scratch." Start with Core and guide/00-quickstart; come back here when you need a table, a schema, or a printable kit.
Table of contents¶
| # | Document | Link | When to open |
|---|---|---|---|
| 01 | Glossary | 01-glossary.md | You need a term with an example and a mapping to ISO 29148 / SENAR |
| 02 | Schemas (formal) | 02-schemas.md | Frontmatter validation, cross-field rules, TC schema |
| 03 | AI Risk Register | 03-ai-risk-register.md | SPEC-AI, eval, provenance — 14 risks and mitigations |
| 04 | AI Style Guide | 04-ai-style-guide.md | System prompt and citation rules for the AI artifact generator |
| 05 | Knowledge Graph Schema | 05-knowledge-graph-schema.md | KG node/edge types, federated queries |
| 06 | EN Style Guide | 06-en-style-guide.md | Editorial rules for the EN corpus (for maintainers) |
| 07 | ISO 29148 — matrix | 07-iso29148-trace-matrix.md | External ISO 29148 claim; audit evidence |
| 08 | Conformance self-assessment | 08-conformance-self-assessment.md | Printable checklist + RENAR-CONFORMANCE.yaml template |
| 09 | Pedagogical density | 09-pedagogical-density.md | Which chapters of the standard are dense — where to go for a quickstart |
| 10 | Agent implementation profile | 10-agent-implementation-profile.md | Abstract contract for a runtime / agent implementer |
| 11 | Catalog of external standards | 11-external-standards-mapping.md | Extended mapping for SAFe, BDD, CMMI, and others (overflow from §02) |
| 12 | Document templates | 12-document-templates.md | Copy-paste skeletons for BR / SR / TR / TC (frontmatter + body) |
| 13 | Recommended TZ form | 13-tz-form.md | The client writes the TZ — 11 sections derived from the finding typology (informative) |
| 14 | Acceptance-programme form | 14-acceptance-program.md | The trial programme for the client: fields, completeness, verdict by defect class (informative) |
Three common scenarios¶
| Scenario | Document |
|---|---|
| "What does this term mean?" | 01-glossary |
| "How do I fill in the TC frontmatter?" | 02-schemas §8 |
| "Preparing the manifest before a release" | 08-conformance-self-assessment |