Ontology Explorer

Institution — an institutions-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Institution" to connect institutions with accountability, eligibility, or response obligations.

Anti-slop: Keep Institution anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Institutional Memory — an institutions-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Institutional Memory" to connect institutions with accountability, eligibility, or response obligations.

Anti-slop: Keep Institutional Memory anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Authority Chain — an institutions-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Authority Chain" to connect institutions with accountability, eligibility, or response obligations.

Anti-slop: Keep Authority Chain anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Public Mandate — an institutions-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Public Mandate" to connect institutions with accountability, eligibility, or response obligations.

Anti-slop: Keep Public Mandate anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Agency Role — an institutions-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Agency Role" to connect institutions with accountability, eligibility, or response obligations.

Anti-slop: Keep Agency Role anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Governance Dependency — a governance-semantics-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Governance Dependency" to connect governance semantics with accountability, eligibility, or response obligations.

Anti-slop: Keep Governance Dependency anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Policy Object — a governance-semantics-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Policy Object" to connect governance semantics with accountability, eligibility, or response obligations.

Anti-slop: Keep Policy Object anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Authority Scope — a governance-semantics-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Authority Scope" to connect governance semantics with accountability, eligibility, or response obligations.

Anti-slop: Keep Authority Scope anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Public Outcome — a governance-semantics-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Public Outcome" to connect governance semantics with accountability, eligibility, or response obligations.

Anti-slop: Keep Public Outcome anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Obligation Term — a governance-semantics-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Obligation Term" to connect governance semantics with accountability, eligibility, or response obligations.

Anti-slop: Keep Obligation Term anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Civic Workflow — a civic-systems-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Civic Workflow" to connect civic systems with accountability, eligibility, or response obligations.

Anti-slop: Keep Civic Workflow anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Resident Journey — a civic-systems-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Resident Journey" to connect civic systems with accountability, eligibility, or response obligations.

Anti-slop: Keep Resident Journey anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Service Boundary — a civic-systems-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Service Boundary" to connect civic systems with accountability, eligibility, or response obligations.

Anti-slop: Keep Service Boundary anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Civic Event — a civic-systems-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Civic Event" to connect civic systems with accountability, eligibility, or response obligations.

Anti-slop: Keep Civic Event anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Public Record Link — a civic-systems-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Public Record Link" to connect civic systems with accountability, eligibility, or response obligations.

Anti-slop: Keep Public Record Link anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Public Service — a public-services-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Public Service" to connect public services with accountability, eligibility, or response obligations.

Anti-slop: Keep Public Service anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Eligibility Rule — a public-services-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Eligibility Rule" to connect public services with accountability, eligibility, or response obligations.

Anti-slop: Keep Eligibility Rule anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Service Request — a public-services-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Service Request" to connect public services with accountability, eligibility, or response obligations.

Anti-slop: Keep Service Request anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Service Channel — a public-services-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Service Channel" to connect public services with accountability, eligibility, or response obligations.

Anti-slop: Keep Service Channel anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Benefit Pathway — a public-services-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Benefit Pathway" to connect public services with accountability, eligibility, or response obligations.

Anti-slop: Keep Benefit Pathway anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Jurisdiction — a jurisdictions-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Jurisdiction" to connect jurisdictions with accountability, eligibility, or response obligations.

Anti-slop: Keep Jurisdiction anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Geographic Scope — a jurisdictions-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Geographic Scope" to connect jurisdictions with accountability, eligibility, or response obligations.

Anti-slop: Keep Geographic Scope anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Interlocal Agreement — a jurisdictions-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Interlocal Agreement" to connect jurisdictions with accountability, eligibility, or response obligations.

Anti-slop: Keep Interlocal Agreement anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

District Boundary — a jurisdictions-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "District Boundary" to connect jurisdictions with accountability, eligibility, or response obligations.

Anti-slop: Keep District Boundary anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Authority Overlap — a jurisdictions-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Authority Overlap" to connect jurisdictions with accountability, eligibility, or response obligations.

Anti-slop: Keep Authority Overlap anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Regulation — a regulations-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Regulation" to connect regulations with accountability, eligibility, or response obligations.

Anti-slop: Keep Regulation anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Compliance Requirement — a regulations-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Compliance Requirement" to connect regulations with accountability, eligibility, or response obligations.

Anti-slop: Keep Compliance Requirement anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Permit Condition — a regulations-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Permit Condition" to connect regulations with accountability, eligibility, or response obligations.

Anti-slop: Keep Permit Condition anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Rule Version — a regulations-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Rule Version" to connect regulations with accountability, eligibility, or response obligations.

Anti-slop: Keep Rule Version anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Exemption Clause — a regulations-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Exemption Clause" to connect regulations with accountability, eligibility, or response obligations.

Anti-slop: Keep Exemption Clause anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Infrastructure Asset — an infrastructure-assets-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Infrastructure Asset" to connect infrastructure assets with accountability, eligibility, or response obligations.

Anti-slop: Keep Infrastructure Asset anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Asset Operator — an infrastructure-assets-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Asset Operator" to connect infrastructure assets with accountability, eligibility, or response obligations.

Anti-slop: Keep Asset Operator anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Lifecycle State — an infrastructure-assets-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Lifecycle State" to connect infrastructure assets with accountability, eligibility, or response obligations.

Anti-slop: Keep Lifecycle State anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Maintenance Obligation — an infrastructure-assets-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Maintenance Obligation" to connect infrastructure assets with accountability, eligibility, or response obligations.

Anti-slop: Keep Maintenance Obligation anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Critical Dependency — an infrastructure-assets-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Critical Dependency" to connect infrastructure assets with accountability, eligibility, or response obligations.

Anti-slop: Keep Critical Dependency anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Emergency Response Node — an emergency-response-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Emergency Response Node" to connect emergency response with accountability, eligibility, or response obligations.

Anti-slop: Keep Emergency Response Node anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Incident Command Role — an emergency-response-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Incident Command Role" to connect emergency response with accountability, eligibility, or response obligations.

Anti-slop: Keep Incident Command Role anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Resource Request — an emergency-response-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Resource Request" to connect emergency response with accountability, eligibility, or response obligations.

Anti-slop: Keep Resource Request anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Mutual Aid Link — an emergency-response-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Mutual Aid Link" to connect emergency response with accountability, eligibility, or response obligations.

Anti-slop: Keep Mutual Aid Link anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Continuity Function — an emergency-response-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Continuity Function" to connect emergency response with accountability, eligibility, or response obligations.

Anti-slop: Keep Continuity Function anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Compliance Evidence — a compliance-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Compliance Evidence" to connect compliance with accountability, eligibility, or response obligations.

Anti-slop: Keep Compliance Evidence anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Audit Check — a compliance-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Audit Check" to connect compliance with accountability, eligibility, or response obligations.

Anti-slop: Keep Audit Check anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Reporting Duty — a compliance-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Reporting Duty" to connect compliance with accountability, eligibility, or response obligations.

Anti-slop: Keep Reporting Duty anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Risk Register — a compliance-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Risk Register" to connect compliance with accountability, eligibility, or response obligations.

Anti-slop: Keep Risk Register anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Remediation Action — a compliance-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Remediation Action" to connect compliance with accountability, eligibility, or response obligations.

Anti-slop: Keep Remediation Action anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Interagency Bridge — an interagency-coordination-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Interagency Bridge" to connect interagency coordination with accountability, eligibility, or response obligations.

Anti-slop: Keep Interagency Bridge anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Referral Path — an interagency-coordination-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Referral Path" to connect interagency coordination with accountability, eligibility, or response obligations.

Anti-slop: Keep Referral Path anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Data Sharing Agreement — an interagency-coordination-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Data Sharing Agreement" to connect interagency coordination with accountability, eligibility, or response obligations.

Anti-slop: Keep Data Sharing Agreement anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Coordination Cadence — an interagency-coordination-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Coordination Cadence" to connect interagency coordination with accountability, eligibility, or response obligations.

Anti-slop: Keep Coordination Cadence anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Shared Case Context — an interagency-coordination-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Shared Case Context" to connect interagency coordination with accountability, eligibility, or response obligations.

Anti-slop: Keep Shared Case Context anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Public Trust Signal — a public-trust-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Public Trust Signal" to connect public trust with accountability, eligibility, or response obligations.

Anti-slop: Keep Public Trust Signal anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Transparency Record — a public-trust-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Transparency Record" to connect public trust with accountability, eligibility, or response obligations.

Anti-slop: Keep Transparency Record anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Accountability Path — a public-trust-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Accountability Path" to connect public trust with accountability, eligibility, or response obligations.

Anti-slop: Keep Accountability Path anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Public Feedback Loop — a public-trust-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Public Feedback Loop" to connect public trust with accountability, eligibility, or response obligations.

Anti-slop: Keep Public Feedback Loop anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Legitimacy Marker — a public-trust-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Legitimacy Marker" to connect public trust with accountability, eligibility, or response obligations.

Anti-slop: Keep Legitimacy Marker anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Machine-Readable Rule — a machine-readable-governance-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Machine-Readable Rule" to connect machine-readable governance with accountability, eligibility, or response obligations.

Anti-slop: Keep Machine-Readable Rule anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Rule Source Link — a machine-readable-governance-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Rule Source Link" to connect machine-readable governance with accountability, eligibility, or response obligations.

Anti-slop: Keep Rule Source Link anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Structured Guidance — a machine-readable-governance-domain concept for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Structured Guidance" to connect machine-readable governance with accountability, eligibility, or response obligations.

Anti-slop: Keep Structured Guidance anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Semantic Policy Model — a machine-readable-governance-domain construct for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Semantic Policy Model" to connect machine-readable governance with accountability, eligibility, or response obligations.

Anti-slop: Keep Semantic Policy Model anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Governance Interface Term — a machine-readable-governance-domain element for modeling public authority, service delivery, institutional responsibility, or civic accountability in machine-readable form. It belongs here because it clarifies coordination between public systems rather than developer runtime mechanics.

Example: A synthetic city service map uses "Governance Interface Term" to connect machine-readable governance with accountability, eligibility, or response obligations.

Anti-slop: Keep Governance Interface Term anchored to CivilOntology's ownership boundary; do not rewrite it as JSON developer runtime, generic graph AI, or generic AI platform copy.

Institutional Memory Unit — an institutional-memory-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Institutional Memory Unit" to show institutional memory without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Institutional Memory Unit owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Agency Precedent — an institutional-memory-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Agency Precedent" to show institutional memory without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Agency Precedent owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Mandate Memory — an institutional-memory-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Mandate Memory" to show institutional memory without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Mandate Memory owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Public Record Continuity — an institutional-memory-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Public Record Continuity" to show institutional memory without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Public Record Continuity owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Institutional Stewardship — an institutional-memory-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Institutional Stewardship" to show institutional memory without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Institutional Stewardship owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Civic Workflow Step — a civic-workflow-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Civic Workflow Step" to show civic workflow without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Civic Workflow Step owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Eligibility Workflow — a civic-workflow-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Eligibility Workflow" to show civic workflow without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Eligibility Workflow owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Resident Service Journey — a civic-workflow-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Resident Service Journey" to show civic workflow without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Resident Service Journey owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Workflow Status Term — a civic-workflow-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Workflow Status Term" to show civic workflow without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Workflow Status Term owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Service Closure State — a civic-workflow-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Service Closure State" to show civic workflow without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Service Closure State owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Jurisdiction Map — a jurisdiction-mapping-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Jurisdiction Map" to show jurisdiction mapping without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Jurisdiction Map owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Authority Boundary — a jurisdiction-mapping-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Authority Boundary" to show jurisdiction mapping without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Authority Boundary owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

District Crosswalk — a jurisdiction-mapping-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "District Crosswalk" to show jurisdiction mapping without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep District Crosswalk owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Interlocal Scope — a jurisdiction-mapping-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Interlocal Scope" to show jurisdiction mapping without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Interlocal Scope owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Place Authority Link — a jurisdiction-mapping-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Place Authority Link" to show jurisdiction mapping without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Place Authority Link owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Public Trust Marker — a public-trust-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Public Trust Marker" to show public trust without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Public Trust Marker owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Transparency Signal — a public-trust-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Transparency Signal" to show public trust without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Transparency Signal owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Accountability Claim — a public-trust-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Accountability Claim" to show public trust without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Accountability Claim owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Public Notice Link — a public-trust-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Public Notice Link" to show public trust without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Public Notice Link owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Feedback Obligation — a public-trust-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Feedback Obligation" to show public trust without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Feedback Obligation owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Governance Dependency — a governance-dependency-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Governance Dependency" to show governance dependency without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Governance Dependency owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Policy Dependency — a governance-dependency-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Policy Dependency" to show governance dependency without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Policy Dependency owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Service Dependency — a governance-dependency-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Service Dependency" to show governance dependency without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Service Dependency owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Funding Dependency — a governance-dependency-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Funding Dependency" to show governance dependency without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Funding Dependency owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Operational Dependency — a governance-dependency-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Operational Dependency" to show governance dependency without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Operational Dependency owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Regulatory Semantic — a regulatory-semantics-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Regulatory Semantic" to show regulatory semantics without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Regulatory Semantic owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Rule Applicability — a regulatory-semantics-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Rule Applicability" to show regulatory semantics without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Rule Applicability owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Compliance Scope — a regulatory-semantics-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Compliance Scope" to show regulatory semantics without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Compliance Scope owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Regulatory Exception — a regulatory-semantics-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Regulatory Exception" to show regulatory semantics without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Regulatory Exception owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Policy Version Link — a regulatory-semantics-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Policy Version Link" to show regulatory semantics without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Policy Version Link owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Public Asset Semantic — a public-infrastructure-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Public Asset Semantic" to show public infrastructure without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Public Asset Semantic owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Infrastructure Steward — a public-infrastructure-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Infrastructure Steward" to show public infrastructure without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Infrastructure Steward owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Critical Asset Link — a public-infrastructure-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Critical Asset Link" to show public infrastructure without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Critical Asset Link owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Maintenance Responsibility — a public-infrastructure-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Maintenance Responsibility" to show public infrastructure without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Maintenance Responsibility owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Asset Risk Context — a public-infrastructure-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Asset Risk Context" to show public infrastructure without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Asset Risk Context owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Interagency Coordination Point — an interagency-coordination-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Interagency Coordination Point" to show interagency coordination without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Interagency Coordination Point owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Shared Service Context — an interagency-coordination-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Shared Service Context" to show interagency coordination without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Shared Service Context owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Referral Agreement — an interagency-coordination-domain construct for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Referral Agreement" to show interagency coordination without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Referral Agreement owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Mutual Aid Semantic — an interagency-coordination-domain element for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Mutual Aid Semantic" to show interagency coordination without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Mutual Aid Semantic owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.

Coordination Record — an interagency-coordination-domain concept for public institutions, jurisdictional meaning, civic workflows, policy objects, infrastructure obligations, or machine-readable governance. It stays inside civic coordination and does not define agent identity or JSON runtime tooling.

Example: A public-safe CivilOntology example uses "Coordination Record" to show interagency coordination without exposing private operational logic or crossing into agent identity.

Anti-slop: Keep Coordination Record owned by CivilOntology; reject rewrites that turn it into agent identity, JSON runtime, generic graph AI.