Governance · Section 10 and canonical files
Tokens and canonical source
The canonical system, derived files, semantic tokens, machine endpoints and future MCP resource contract.
Authority
Where any value disagrees with another artifact, v6.1-system.json is right. Tokens and the manifest are derived outputs.
| Version | 6.1.0 |
|---|---|
| Status | Approved Core |
| Supersedes | Edition 06 |
| Released | 2026-08-06 |
Semantic tokens
Use roles in implementation so brand changes remain governed and raw palette values stay exceptional.
surface.paperparchment.50surface.paper.sunkparchment.100surface.screennocturne.950surface.screen.raisednocturne.900surface.brandsapphire.950ink.primary.lightparchment.900ink.secondary.lightparchment.700ink.primary.darknocturne.100ink.secondary.darknocturne.400rule.defaultsapphire.800rule.default.onDarksapphire.400rule.hairlinesapphire.100accent.defaultaqua.700accent.default.onDarkaqua.400focus.ringaqua.500status.readyaqua.700status.riskamber.700status.breachrowan.700status.noneparchment.700status.ready.onDarkaqua.400status.risk.onDarkamber.400status.breach.onDarkrowan.400status.none.onDarknocturne.400Machine endpoints
Stable, versioned public resources support websites, generators, document systems and automated quality checks.
MCP readiness
The portal and future MCP server are designed to consume the same canonical source, not copy content from the rendered website.
Resources
System, tokens, manifests, navigation and individual guidance pages.
Prompts
Artifact-specific instructions can assemble rules from versioned resources.
Validation
Future tools can test assets, colour roles, claims and required metadata.