Public-safe use case
Build a public-safe glossary page for institutional coordination without borrowing terms from agent identity.
CivilOntology Reference System
Ontology Use Cases
Public-safe use cases for CivilOntology. These examples keep the site anchored to governance semantics, institutional coordination, civic workflows, public infrastructure, and machine-readable governance.
Sibling sites are boundary references. CivilOntology remains focused on governance and institutional semantic coordination.
This Site Owns
- institutional coordination
- governance semantics
- public services
- jurisdictions
- policy objects
- civic workflows
- public infrastructure
- machine-readable governance
This Site Does Not Own
- agent identity
- JSON runtime
- generic graph AI
- human philosophy
- customer support
Use Cases
Public-safe use case
Create SEO landing sections around Institutional Memory and Civic Workflow using only CivilOntology terms.
Public-safe use case
Tag synthetic examples with ownership rules before linking to sibling ontology sites.
Public-safe use case
Review draft content for accidental drift into JSON runtime.
Public-safe use case
Generate internal editorial briefs that distinguish public services from neighboring ontology domains.
Public-safe use case
Create examples that name concrete semantic objects while avoiding private operational logic.
Public-safe use case
Map expansion items to core items for richer explorer filtering.
Public-safe use case
Use anti-overlap rules as checklist items before publishing public copy.
Public-safe use case
Create canonical-reference links to sibling sites when a topic belongs elsewhere.
Public-safe use case
Audit long-form essays for duplicate content and site-boundary leakage.
Anti-Overlap Rules
- CivilOntology owns institutional coordination; link elsewhere when the page primarily explains agent identity.
- Do not rename JSON runtime as a CivilOntology feature.
- Do not import another site's ontology items into CivilOntology data files.
- Use sibling sites only as canonical references, not as copied source content.
- Examples must be synthetic, public-safe, and free of private operational logic.
- Definitions must name the CivilOntology semantic role, not generic AI benefits.
- Expansion relationships must connect local expansion items only.
- SEO keywords must reinforce institutional coordination and governance semantics.
- If a term primarily concerns generic graph AI, mark it out of scope.
- Never flatten CivilOntology into a shared ecosystem landing page.