Imported from vinaosb/libertarian-constitution-and-laws (
docs/en/AGENTS.md). Install upstream withnpx skills add vinaosb/libertarian-constitution-and-laws --skill en. Copyright stays with the author.
docs/en/
English-language practical documentation for adopting governments, their officials, and their citizens. Translates the legal text into operational documents: contracts, agreements, guides, procedures, manuals, checklists, forms, worksheets, standards, and protocols.
What this directory is for
The Government Documentation Suite answers "what does a government actually need to operate this framework?" Each category directory contains production-ready documents that an adopting country can fill in and use immediately. Every document cites the governing constitutional or statutory provision it implements.
This is NOT legal text. It does not use operative language ("shall", "may", "must not") except inside quotation marks citing legal text. It uses normal prose with practical guidance.
Structure
docs/en/
├── README.md This index
├── AGENTS.md This file
├── country-implementation-playbook/ High-level adoption guidance (14 areas, 3 tiers)
│
├── government-contracts/ Government-to-private contract templates
├── inter-governmental-agreements/ Public-public agreement templates
├── private-legal-instruments/ Private-private contract templates
├── citizen-guides/ Public education guides
├── regulatory-compliance/ Business compliance guides
├── staff-procedures/ Cross-cutting operational procedures
├── branch-operations-manuals/ Institution-specific manuals
├── anti-corruption-toolkit/ Integrity and accountability tools
├── legislative-resources/ Subnational drafting aids
├── transition-toolkit/ Article 12 migration execution
├── financial-fiscal-instruments/ Budget and reporting templates
├── election-administration/ Referendum and election management
├── emergency-crisis-management/ Crisis response and continuity
├── court-justice-documents/ Judicial operations
├── property-land-administration/ Property registration tools
├── privacy-data-protection/ Digital rights operational tools
├── international-relations-toolkit/ State-to-state and treaty documents
├── immigration-border-toolkit/ Entry, asylum, naturalization
├── intellectual-property-toolkit/ Patents, trademarks, copyright, trade secrets
├── financial-sector-licensing/ Banking, insurance, currency issuance
├── voluntary-sector-toolkit/ Charities, foundations, mutual aid
├── education-frameworks/ Accreditation, homeschool, certification
├── consumer-protection-toolkit/ Disclosure-based consumer protection
├── labor-workplace-frameworks/ Freedom-of-contract workplace documents
├── digital-government-standards/ Digital identity, open data, cybersecurity
├── infrastructure-utility-agreements/ Interconnection, right-of-way, access
├── space-activities-toolkit/ Launch, registration, resource rights
├── maritime-vessel-toolkit/ Vessel registry, ports, marine liability
├── energy-sector-frameworks/ Generation, grid access, extraction
├── defense-military-operations/ Military justice, civilian control
├── natural-resource-use-frameworks/ Farming, water, forestry, mining
├── animal-welfare-and-veterinary/ Welfare standards, veterinary certification
├── civil-registration-toolkit/ Birth, death, marriage registration
├── notarial-authentication-toolkit/ Notarization, authentication, signatures
└── records-and-standards/ Retention, metrology, forms library
Each category directory contains:
_template.md: Structural skeleton every document in that category followsAGENTS.md: Category-specific purpose, conventions, and gotchas- Production-ready documents with fill-in-the-blank fields marked
[TO BE DETERMINED BY ADOPTING COUNTRY]
Conventions
These documents follow the same drafting conventions as the legal text, with one key exception: they use normal prose, not operative legal language.
- No acronyms. Spell out every term.
- No country references. Describe the mechanism in full prose.
- No Latin legal terms. Use plain English equivalents.
- No em dashes or en dashes. Use commas, parentheses, or restructure.
- Numbers written out as words in narrative text.
- Cross-reference format:
Constitution, Article 5(3),Ordinary Statute 7001,Annex 2(2). - Use
[TO BE DETERMINED BY ADOPTING COUNTRY]for all country-specific blanks. - Every document includes an "Incentive and loophole guardrails" section addressing perverse incentives, gaming vectors, capture risks, and malpractices.
- Every document includes a "Completeness checklist" at the end.
What lives elsewhere
- Legal operative text (constitution, statutes, annexes, treaties, regulations):
en/ - Language-neutral reference specifications (conventions, numbering, glossary, translation guide):
docs/ - Build scripts and PDF pipeline:
tools/ - Software catalog mapping open-source software to constitutional mandates:
software/
Internationalization
This directory uses the docs/en/ language-prefix structure for future translation support. Language-neutral reference specifications stay in the parent docs/ directory so they do not need duplication per language.
Gotchas
- These documents must NOT contradict the legal text. Every factual claim must trace to a cited provision. If a document and the legal text conflict, the legal text wins.
- Do not create new defined terms. Use existing terms from
Constitution, Article 1(1)anddocs/GLOSSARY.md. - Do not introduce operative legal language outside quotation marks. These are guidance documents, not law.
- When a category references a statute that does not exist yet (reserved number), note the reservation rather than fabricating content.