Spec maintenance
Platform spec area
Spec maintenance
No architecture decision records under adr/ for this feature yet. Standard features must
publish at least one ADR or keep a ## Decisions summary on the hub.
- No directly attached article pages for this node.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
scope | yes | yes |
features | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Scope
Maintenance policy for keeping platform-spec pages synchronized with code and release evolution.
Feature policies
Section titled “Feature policies”- Specification authority and embedded decisions - Language law vs implementation domains, Proposed/Standard maturity, and embedded decision records.
- Release and versioning policy - Git as version axis; v0.x bands as delivery scope, not URL segments.
- Domain, Area and Feature template bundle - Mandatory markdown-first structure and section contracts for all levels.
- Domain, Area, Feature, and Article frontmatter templates - Canonical YAML templates aligned with schema and CI validation.
- Non-normative bridge docs policy - Rules for migration mapping pages and canonical destination linking.
- Last reviewed policy - Requirements for
lastReviewedmetadata on high-change pages. - Project inception decisions - Cross-cutting ADRs from project inception (
D-INC-0001–D-INC-0008, reader ADRs tab).
Maintenance policy features above publish closed choices under each feature’s adr/ (D-COMM-* identifiers, reader ADRs tab).
Feature index
Use the tiles below for normative feature contracts in this area.
Features
- Domain, Area, Feature, and Article frontmatter templatesCanonical frontmatter templates aligned with platform-spec validators and Zod contracts.
- Domain, Area and Feature template bundleMandatory markdown-first template set for Domain, Area and Feature pages, including required section contracts and optional article bundles.
- Last reviewed policyPolicy for `lastReviewed` metadata and drift detection in high-change feature pages.
- Non-normative bridge docs policyPolicy for migration and bridge documents, including mandatory canonical destination links for non-normative mapping pages.
- Release and versioning policyGit as the canonical version axis; v0.x bands label delivery scope, not alternate documentation URLs or parallel normative trees.
- Specification authority and embedded decisionsNormative rules for language law vs implementation domains, maturity (Proposed/Standard), and embedded decision records in feature hubs and articles.