Tracker
Roadmap search
Versions, deliverables, workstreams, tasks, and pages
Spec maintenance
area
src/content/docs/platform-spec/community/spec-maintenance/index.mdx
import SpecPageHeader from '@beskid/beskid-ui/platform-spec/SpecPageHeader.astro'; import SpecSection from '@beskid/beskid-ui/platform-spec/SpecSection.astro'; import DomainTiles from '@beskid/beskid-ui/platform-spec/DomainTiles.astro';
<SpecPageHeader ownerName="Piotr Mikstacki" ownerEmail="pmikstacki@cybernomad.it" submitterName="Piotr Mikstacki" submitterEmail="pmikstacki@cybernomad.it" /> <SpecSection title="Scope" id="scope"> Maintenance policy for keeping platform-spec pages synchronized with code and release evolution. </SpecSection>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).