Company
The authority and provenance surface
Doctrine Industries defines and preserves the models, principles, rights, ventures, and institutional structures from which the wider ecosystem is constructed.
Why Doctrine exists
Implementation always contains a doctrine.
Software, process, policy, and institutions all encode assumptions about evidence, authority, identity, acceptable states, and permissible action. Leaving those assumptions implicit does not remove them. It makes them harder to inspect.
Doctrine Industries exists to make those structures explicit before they harden into products, ventures, or institutional practice.
- What Doctrine produces
- Formal models, charters, system definitions, registries, governance contracts, decision records, publications, and intellectual-property structures.
- What Doctrine controls
- Canonical terminology, system identity, governing specifications, publication status, institutional relationships, and rights positions within its declared scope.
- What Doctrine does not control
- External law, public authority, independent evidence, professional judgement, or implementation merely because Doctrine defined the system.
- How Doctrine relates to Nilsoft
- Doctrine defines and governs the specification surface. Nilsoft constructs and operates technology under explicit implementation and release authority.
- How Doctrine relates to The Garden Institute
- Doctrine may define reusable structures, while the Institute retains its own ethical, custodial, community, and human-continuity obligations.
Public charter
Definition does not create unlimited authority.
Doctrine remains bounded by evidence, explicit ownership, versioned publication, implementation separation, and the mandates of the entities that actually operate.
Read the charter