4. Formatting Standards
4. Formatting Standards
← Structure | Index | Next →
4.1 Document Header
Each file in a Specification RFC MUST begin with:
RFC-SPEC--NNNN Section N Category: Specification
4.2 Prerequisite Format
Prerequisites MUST be formatted as tables:
Types:
| Type | Meaning |
|---|---|
| Required | Implementation fails without this |
| Optional | Implementation works but with reduced functionality |
| Conditional | Required only if specific feature is enabled |
4.3 Phase Format
Phases MUST follow the task → test → iterate structure:
4.4 Resource Table Format
Resources MUST be defined in tables, not code:
NOT permitted:
4.5 Validation Criteria Format
Validation criteria MUST be tabular and deterministic:
4.6 Test Category Format
Test requirements MUST be organized by category:
4.7 Risk Format
Risks MUST be documented with likelihood, impact, and mitigation:
4.8 Navigation and Footer
Same as other RFC kinds:
- Navigation links after header
- Footer with RFC identifier at end
End of Section 4 — RFC-RFCSTD-0003