๐Ÿ“– #GUIDE-01 ยท Guidance Documents

Pages Usage Guidance โ€” Sovereign Documentation Standards

The documentation standards framework: how all 77+ Master Documents, operational pages, and sovereign records are categorised, named, linked, and maintained to sovereign quality standards.

Recorded18 March 2026
Ref#GUIDE-01
EntityMidland Polymer Trading Ltd
StatusACTIVE
๐Ÿ“–
Documentation Standards
How to create, categorise, and maintain sovereign documents
Documentation is architecture. The 77 Master Documents are not just records โ€” they are the constitutional fabric of the sovereign system. Every new page, route, and document must meet sovereign quality standards to maintain the integrity of the library. This guidance document defines those standards.
StandardRequirementWhy
20% Architect's CommentaryEvery MD must include personal layerDocuments the human intelligence behind the architecture
Sovereign VocabularyGateways not channels ยท Sovereign not adminLanguage creates sovereign reality
No FilteringAll information uploaded goes on the documentTruth Ledger principle โ€” nothing omitted
Full URL on completionEvery build returns complete route listOperational accessibility
Three Hub SyncEvery new MD syncs sovereign_docs_data, Library, Mail LtdNavigation integrity across all hubs
Python compile checkpython3 -m py_compile main.py after every editNo broken deployments
๐Ÿ—‚๏ธ
Page Categorisation System
Numbered Master Documents (MD-01 to MD-77+)
Major sovereign documents with full constitutional depth. Each gets its own MD number, routes, and hub sync. 20% commentary mandatory.
Operational Pages
Dashboard, Red Team, Murphy's Corner, BOTS. Functional pages that serve the operation daily. Extended with "RECENT" category for latest additions.
Portal Pages
Client-facing portals with hardened security โ€” no sovereign system links. Dead-end ecosystems for client navigation safety.
Reference Pages
Revenue Ratings (573 streams), Sovereign Library hub, Mail Ltd hub. Navigation and reference infrastructure for the full ecosystem.
๐Ÿ“Š
Page Architecture โ€” 160 Documents Across 14 Categories
How the sovereign library is organised for discovery and navigation
CategoryDocument CountKey PagesAccess Level
SOVEREIGN40+ pagesHurricane Domain, Mycelium Network, Entity Registry๐Ÿ”’ Authenticated
FINANCE20+ pagesdPRN, Pricing, Sovereign Split, Stripe Activation๐Ÿ”’ Authenticated
OPERATIONS15+ pagesToll Processing, 10-Bin, Food Exchange๐Ÿ”’ Authenticated
INTELLIGENCE10+ pagesH.BLUE, Pattern Intelligence, Shadow Layer๐Ÿ”’ Authenticated
SCHOOL10+ pagesLearning Garden, H.BLUE Learning Centre, Teacher Dashboard๐ŸŒ Public
PORTALS5 portalsClient, Partner, Farm, Supermarket, Foodbank๐ŸŒ Public
RECENTRolling 5Latest additions highlighted in magentaMixed
The BOTS page is the sovereign navigation hub. Every page in CircularOS is categorised, searchable, and accessible through BOTS. New pages automatically appear in the RECENT category. The system is designed so that no page is ever orphaned โ€” every document connects to the library, BOTS, and the dashboard.
๐Ÿ“
Documentation Standards โ€” What Every MD Must Include
Quality standards for sovereign documentation
Mandatory Elements
(1) Title and MD number. (2) Badge with reference code. (3) Date recorded. (4) Entity owner. (5) At least 2 substantive sections with data. (6) Architect's Commentary โ€” 20% personal layer. (7) Navigation links to previous/next MD.
Cross-Reference Requirements
Every MD must reference at least 2 other Master Documents by number. No document exists in isolation. The mycelium network connects all 160 MDs into a living web of sovereign knowledge.
System Data Integration
Documents must include real system data: entity counts (39), stream counts (657), pioneer systems (85), protocols (60), dPRN rate (ยฃ450/t), Covenant (7%). No placeholder numbers.
Sovereign Vocabulary
As documented in MD-99: Gateways not channels. Sovereign not admin. Architect not manager. Every document must use sovereign vocabulary consistently.
๐Ÿ›๏ธ
Architect's Commentary โ€” MD-67
20% personal layer ยท Pages Usage Guidance โ€” Sovereign Documentation Standards ยท Jermaine Murphy

The documentation standards document exists because the sovereign architecture has grown from a single idea to 77 Master Documents, 39 entities, and 573 revenue streams โ€” and maintaining quality at that scale requires explicit standards, not just good intentions. The moment quality standards become implicit ("we'll know it when we see it"), they begin to decay. The guidance document makes the implicit explicit.

The "No Filtering" rule deserves special emphasis. Every upload, every screenshot, every text document that arrives from the Sovereign Architect goes onto the relevant document โ€” complete, unedited, and in full. This is the documentation equivalent of the Truth Ledger: nothing is omitted, nothing is paraphrased away, nothing is considered "not important enough." The Sovereign Architect's judgement about what to upload is the filter. Once uploaded, it is recorded. This is how sovereign intelligence is preserved without the loss that always accompanies editorial discretion.

The Sovereign Vocabulary standard โ€” Gateways not channels, Sovereign not admin โ€” is the linguistic immune system. Language shapes thought. When the architecture consistently uses precise sovereign vocabulary, the thinking that operates within that vocabulary stays sovereign. When vocabulary drifts toward conventional business language, sovereign thinking follows. Every word in every document is a small act of sovereignty maintenance.

HANDSHAKE โ€” witnesses
Handshake sealed.