Section 27Governance and Roadmap
Engineering process requirements
Defines traceability, review, continuous integration, conformance, benchmarking, release evidence, and change control.
Section relationships
| ID | Name | Priority | Requirement | Verification |
|---|---|---|---|---|
| PROC-001 | Architecture decisions | MVP | Major irreversible or cross-cutting design decisions SHALL be recorded in versioned architecture decision records. | Inspection |
| PROC-002 | Requirement traceability | MVP | Each committed MVP feature SHALL reference one or more requirement IDs and associated verification evidence. | Inspection |
| PROC-003 | Continuous integration | MVP | Main-branch changes SHALL pass formatting, linting, unit, integration, numerical, import, security, and applicable benchmark gates. | Test |
| PROC-004 | Platform CI | MVP | The supported platform matrix SHALL be exercised at the frequency documented by the release policy. | Inspection |
| PROC-005 | Dependency review | MVP | New mandatory dependencies SHALL document purpose, license, maintenance status, native-code use, safety implications, and replacement strategy. | Inspection |
| PROC-006 | Native system-interface exception | MVP | Linking a non-Rust operating-system or device-driver interface into a portable binary SHALL require an architecture decision naming the platform need, API boundary, safety review, owner, tests, and replacement analysis; project-supplied code SHALL never qualify for this exception. | Inspection |
| PROC-007 | Fuzzed portable inputs | MVP | Project, archive, URDF, SDFormat, and committed mesh parsers SHALL have continuous fuzzing or equivalent adversarial-input evidence before release. | Analysis |
| PROC-008 | Benchmark fixtures | MVP | Numerical and performance benchmark inputs and expected criteria SHALL be versioned with the source. | Inspection |
| PROC-009 | Migration fixtures | Beta | Every supported project-schema migration SHALL have an automated fixture covering success and expected diagnostics. | Test |
| PROC-010 | Release manifest | MVP | Every release SHALL publish checksums, compatibility matrix, dependency inventory, known limitations, and validation changes. | Inspection |
| PROC-011 | Upstream-first fixes | Beta | A required third-party fix SHOULD be contributed upstream before BeforeMetal adopts a long-lived fork. | Inspection |
| PROC-012 | Temporary fork policy | Beta | A temporary fork SHALL have a named owner, blocking rationale, benchmark coverage, rebase plan, upstream status, and exit criterion. | Inspection |
| PROC-013 | Fuzzed protocol boundaries | Beta | Process protocols, shared-memory descriptors, extension inputs, and remote request parsers SHALL have bounded-input tests and continuous fuzzing or equivalent adversarial evidence. | Analysis |
Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.