28. Community Governance
28.1 Subnational Nexus Governance
28.1.1 Subnational Nexus Governance is the state, provincial, territorial, cantonal, devolved, district, county, metropolitan, island, corridor, or other intermediate layer through which Planetary Nexus Governance becomes operational below the national level and above the most local surfaces. It is the governance layer where national doctrine meets the administrative, ecological, infrastructural, cultural, and political realities of place.
28.1.2 Subnational Nexus Governance is necessary because many risks are governed neither adequately at national scale nor solely at community scale. Energy grids, water systems, health systems, land-use planning, transport corridors, disaster response, public utilities, industrial facilities, data centres, housing, climate adaptation, biodiversity, emergency management, cyber-physical infrastructure, and public services often sit within subnational authority or shared national-subnational competence.
28.1.3 A subnational Nexus surface may include subnational councils, state or provincial working groups, territorial desks, regional competence cells, public authority interfaces, community observatories, university or utility hosts, local evidence systems, public-safe dashboards, protected participation routes, and correction channels. Its form should follow local law and institutional reality, not a rigid template.
28.1.4 Subnational governance must preserve the common rail. It should use Case IDs, publication classification, public authority capacity records, safeguards review, monthly or periodic evidence packs, public-safe reporting, maturity states, routeability boundaries, and correction records. It may localize terms and workflows, but it must not weaken role separation.
28.1.5 Subnational Nexus Governance must not become a substitute for national public authority, local public authority, Indigenous governance, community consent, technical verification, recognition, finance-readiness, or downstream execution. It may coordinate, deliberate, record, support evidence, route matters, and escalate. It may not claim powers it has not lawfully received.
28.1.6 Subnational governance is often where authority ambiguity is most acute. A provincial ministry may control one matter, a municipality another, a national regulator another, an Indigenous government another, a utility another, and a local authority another. The subnational Nexus rail must classify each public authority’s capacity precisely and prevent one actor’s participation from being overstated as system-wide approval.
28.1.7 Subnational governance must protect local difference. A province, state, territory, island, border zone, rural region, industrial district, coastal area, mountain region, or peri-urban corridor may face distinct hazards and institutional conditions. Subnational Nexus Governance should make these differences visible to the national and regional rail.
28.1.8 The doctrine is direct:
Subnational Nexus Governance translates the common rail into intermediate territorial reality, making risk governable where law, infrastructure, ecology, and community consequence meet below the national level.
28.2 City and Municipal Governance
28.2.1 City and Municipal Nexus Governance is the urban and local-government layer through which Nexus principles are applied to cities, towns, metropolitan regions, districts, neighbourhoods, public utilities, local infrastructure, public health systems, emergency services, housing systems, transport networks, parks, waterways, data systems, and community-facing services.
28.2.2 Cities are critical Nexus surfaces because they concentrate people, infrastructure, risk, innovation, public trust, public services, data, energy demand, water demand, waste systems, mobility, housing, social inequality, heat exposure, flood exposure, cyber-physical systems, and political visibility. A planetary governance model that cannot operate at city scale cannot govern lived compound risk.
28.2.3 City and Municipal Nexus Governance may include municipal Nexus councils, mayoral or council interfaces, city working groups, local data zones, resilience offices, community observatories, utility interfaces, emergency-management desks, public-safe dashboards, local priority registers, municipal evidence packs, and neighbourhood participation processes.
28.2.4 Municipal governance should be forms-first and evidence-bearing. A city should not govern climate, infrastructure, AI, cyber, housing, water, energy, food, health, biodiversity, and public trust through fragmented departments and meeting minutes alone. It should use structured intake, baselines, public authority capacity, community evidence, technical verification, public-safe reporting, and correction.
28.2.5 City governance must respect municipal law and public authority boundaries. A Nexus city council or municipal Nexus desk may support municipal decision-making, but it does not replace elected councils, municipal administrations, regulators, public utilities, courts, procurement authorities, emergency officials, or other lawful bodies.
28.2.6 City governance must protect neighbourhood-level equity. Public-safe dashboards, resilience pathways, infrastructure finance, data-centre planning, heat adaptation, mobility changes, housing-related interventions, or digital services can benefit some areas while burdening others. City Nexus processes must ask who benefits, who is displaced, who is exposed, who pays, who controls data, and who can correct the record.
28.2.7 City governance should connect upward and downward. Upward, it should feed national priority registers, regional corridor records, and public authority learning. Downward, it should provide understandable public-safe outputs, grievance routes, local observatories, and community feedback loops.
28.2.8 The doctrine is direct:
City and Municipal Nexus Governance makes the rail operational where public services, infrastructure, people, data, ecology, and trust collide most visibly: in the places where daily life is governed.
28.3 Bioregional Assemblies
28.3.1 Bioregional Assemblies are place-based deliberative and evidence surfaces organized around living systems rather than only administrative boundaries. They may be formed around watersheds, forests, coastlines, mountain systems, agricultural regions, biodiversity corridors, wetlands, river deltas, island systems, drylands, migration corridors, or other ecological and socio-ecological regions.
28.3.2 Bioregional Assemblies are necessary because nature does not obey administrative lines. Water flows across municipalities and countries. Species move across territories. Fire, drought, flood, pollution, disease, soil decline, coastal erosion, and biodiversity loss follow ecological logic. Governance that sees only jurisdictional boundaries often misses living-system reality.
28.3.3 A Bioregional Assembly may include public authorities in recorded capacities, Indigenous governments and knowledge holders where applicable, local communities, farmers, fishers, utilities, researchers, conservation actors, civil society, operators, public-health actors, infrastructure managers, youth, elders, and technical experts. Its composition should reflect the living system and affected communities, not only institutional status.
28.3.4 Bioregional Assemblies must not become ecological technocracy. Ecological science is essential, but bioregional governance must also include rights, culture, livelihoods, public authority, protected knowledge, land relations, water relations, historical harm, and community dignity. Nature is not only a dataset.
28.3.5 Bioregional Assemblies may support baselines, public-safe maps, ecological monitoring, community observations, watershed evidence packs, restoration pathways, biodiversity safeguards, drought and flood preparedness, food-water-energy-health-biodiversity planning, and place-based correction. Their outputs should feed national and regional records where appropriate.
28.3.6 Bioregional Assemblies must respect legal authority. A watershed assembly does not override statutory water authorities, Indigenous rights, land-use law, environmental regulators, public utilities, or municipal decision-making unless a lawful instrument grants a role. Its legitimacy is deliberative, evidentiary, ecological, and community-based unless otherwise authorized.
28.3.7 Bioregional Assemblies must protect sensitive ecological and cultural knowledge. Public-safe mapping must not expose sacred sites, protected species locations, vulnerable habitats, community resources, or Indigenous knowledge without permission and safeguards.
28.3.8 The doctrine is direct:
Bioregional Assemblies allow the rail to hear living systems, not only institutions, by organizing evidence and deliberation around ecological reality while preserving law, culture, protection, and correction.
28.4 Watershed, Basin, Corridor, and Ecosystem Surfaces
28.4.1 Watershed, basin, corridor, and ecosystem surfaces are specialized place-based governance surfaces for risk systems that move through water, land, infrastructure, ecology, mobility, trade, energy, data, disease, migration, or supply-chain pathways. They are the operational geography of many compound risks.
28.4.2 A watershed or basin surface may govern water quality, water quantity, flood risk, drought, groundwater, wetlands, agriculture, biodiversity, public health, industrial discharge, hydropower, drinking water, sanitation, and upstream-downstream justice. A corridor surface may govern transport, logistics, migration, energy, data, telecommunications, critical minerals, industrial development, ecological movement, or disaster evacuation. An ecosystem surface may govern habitats, species, restoration, climate resilience, cultural landscapes, and living-system thresholds.
28.4.3 These surfaces should be organized around Case IDs, baselines, monitoring indicators, public authority maps, affected communities, safeguards, technical verification, public-safe reporting, and correction. They should not rely only on periodic consultations or project documents.
28.4.4 Watershed, basin, corridor, and ecosystem surfaces must map authority carefully. Multiple jurisdictions may hold partial authority. Public utilities, regulators, Indigenous governments, municipalities, national agencies, private operators, landholders, and community bodies may all be implicated. The rail must record who has authority over what.
28.4.5 These surfaces must include upstream and downstream effects. A decision that benefits one location may create risk elsewhere. Water extraction, industrial siting, data-centre clusters, transport corridors, flood control, ecological offsets, and energy infrastructure can shift burdens across space and time. Evidence packs must include distributional and cumulative effects.
28.4.6 These surfaces should use multi-sensor, multi-actor, and multi-modal evidence where appropriate: field observations, community reports, satellite and Earth observation, sensors, utility data, ecological monitoring, public health signals, digital twins, hydrological models, public authority records, and historical knowledge. Machine assistance may support analysis, but human accountability and protected knowledge controls remain required.
28.4.7 Public-safe communication is critical. Maps and dashboards can create harm if they expose infrastructure vulnerabilities, sacred sites, sensitive habitats, informal settlements, disputed land, or vulnerable communities. Publication must be classified and reviewed.
28.4.8 The doctrine is direct:
Watershed, basin, corridor, and ecosystem surfaces make compound risk governable along the pathways where harm actually travels, while preventing maps, models, and regional abstractions from overriding people, law, and living systems.
28.5 Community and Indigenous Nodes
28.5.1 Community and Indigenous Nodes are local or territorial governance nodes through which communities, Indigenous peoples, local knowledge holders, territorial stewards, cultural authorities, neighbourhoods, rural settlements, vulnerable groups, workers, youth, elders, and affected persons may contribute evidence, deliberate, protect knowledge, raise grievances, monitor change, and seek correction within the Nexus rail.
28.5.2 These nodes are necessary because the people closest to consequence often see risk first and most clearly. They know where water fails, where heat is unbearable, where infrastructure breaks, where trust has collapsed, where land is contested, where ecological change is visible, where public services fail, where industrial impacts are felt, and where official records do not match reality.
28.5.3 Indigenous Nodes require particular respect. Indigenous peoples, governments, nations, communities, and knowledge holders may have distinct rights, legal status, territorial relationships, knowledge protocols, data sovereignty, governance systems, and consent requirements. Nexus Governance must not treat Indigenous participation as ordinary stakeholder consultation.
28.5.4 Community and Indigenous Nodes must be protected participation surfaces. They should allow confidential submission, assisted participation, local-language engagement, culturally appropriate process, disability access, non-retaliation, protected knowledge controls, community review, and withdrawal or correction of misrepresented knowledge where applicable.
28.5.5 Community and Indigenous Nodes may operate independently, through local institutions, through community-run networks, through universities or trusted hosts, through local labs, through Indigenous governance bodies, or through protected interfaces with the National Desk. The form should be chosen by the community context and lawful conditions, not imposed externally.
28.5.6 These nodes must not be used to manufacture consent. Participation, testimony, data contribution, workshop attendance, mapping, or local hosting does not equal consent unless the applicable legal, cultural, ethical, or institutional consent standard is met and recorded. Non-consent, refusal, silence, or withdrawal must be recordable.
28.5.7 Community and Indigenous Nodes should have feedback rights. If they submit evidence, they should know how it was classified, whether it was used, what public-safe output resulted, what was protected, what changed, and how to request correction. Extraction without feedback violates the rail’s public-good doctrine.
28.5.8 The doctrine is direct:
Community and Indigenous Nodes bring lived truth and protected knowledge into the rail while ensuring that local participation remains safe, non-extractive, consent-disciplined, and correctionable.
28.6 Local Labs and Community Observatories
28.6.1 Local Labs and Community Observatories are place-based evidence and learning surfaces that support local sensing, public-good experimentation, community monitoring, participatory research, technical assistance, public-safe mapping, local dashboards, data stewardship, and issue escalation. They convert local experience into governed evidence without detaching it from the community that produces it.
28.6.2 A Local Lab may be hosted by a university, school, library, community organization, local government, utility, cooperative, Indigenous institution, public-good consortium, or trusted local body. A Community Observatory may monitor water, air, heat, biodiversity, infrastructure, public health, food systems, energy reliability, cyber access, public services, industrial impacts, or social trust indicators.
28.6.3 Local Labs and Community Observatories are necessary because many national and global systems are too distant from local change. Sensors, satellites, models, and administrative records may miss lived reality. A local observatory can validate, challenge, or enrich external data with grounded context.
28.6.4 Local Labs must follow research integrity, data governance, and safeguards. Community evidence should be collected with permission, purpose limitation, data minimization, privacy protection, protected knowledge controls, public-safe publication review, and correction rights. Local enthusiasm must not become informal extraction.
28.6.5 Community Observatories should use appropriate technologies: low-cost sensors, mobile reporting, field notes, interviews, public authority records, satellite interpretation, participatory mapping, data trusts, community dashboards, AI-assisted classification where permitted, and local verification. Technology should fit the local context and capacity.
28.6.6 Local Labs and Observatories should connect to Nexus Competence Cells and TMDs where technical validation is needed. A local water reading, air-quality sensor, biodiversity observation, or infrastructure report may need calibration, verification, or expert review before it supports public claims, public authority action, or routeability.
28.6.7 Local Labs and Observatories must be public-safe. They should not publish maps or data that expose vulnerable people, protected species, sacred sites, security-sensitive infrastructure, private information, or conflict-sensitive locations. Public communication must be reviewed according to classification.
28.6.8 The doctrine is direct:
Local Labs and Community Observatories turn place-based knowledge into governed evidence, allowing communities to see, test, learn, and correct without surrendering control over their data, knowledge, or public meaning.
28.7 Universities, Utilities, and Host Institutions
28.7.1 Universities, utilities, public agencies, hospitals, libraries, cooperatives, civil society organizations, Indigenous institutions, research centres, municipal offices, technical institutes, and other trusted host institutions may support subnational, local, bioregional, and community Nexus Governance by providing space, expertise, data stewardship, technical infrastructure, convening capacity, research support, training, or administrative continuity.
28.7.2 Host institutions are valuable because local governance needs infrastructure. A university may support methods, students, labs, ethics review, and technical assistance. A utility may support infrastructure data and operational insight. A library may support public access and digital inclusion. A municipal office may support public authority interface. An Indigenous institution may support knowledge protocols and territorial governance. A community organization may support trust.
28.7.3 Hosting does not create ownership. A university hosting a lab does not own the community’s knowledge. A utility sharing data does not control the public-good rail. A municipality providing space does not convert a community node into municipal approval. A donor supporting a local observatory does not govern its outputs. Hosting is support, not authority.
28.7.4 Host arrangements must be written and role-bounded. They should define purpose, space, data access, confidentiality, IP, public claims, staffing, safety, equipment, records, publication classification, conflicts, costs, duration, exit, and correction. Apparent authority by hosting must be prohibited.
28.7.5 Host institutions must disclose conflicts. A university may have research interests. A utility may be subject of monitoring. A municipality may be implicated in a decision. A technical institute may have vendor relationships. A community organization may represent some but not all local actors. Host value and host conflict must both be recorded.
28.7.6 Host institutions should support capacity formation rather than dependency. The goal is to strengthen local ability to participate, monitor, interpret, and correct. A host should not become indispensable in ways that prevent community ownership, public-good portability, or continuity after funding changes.
28.7.7 Host institutions must respect publication classification and protected knowledge. Local trust can be destroyed if a host publishes, shares, or processes sensitive information beyond permission. Host access must be role-keyed and revocable.
28.7.8 The doctrine is direct:
Universities, utilities, and host institutions may strengthen local Nexus Governance, but hosting remains a bounded service role and never becomes ownership, consent, recognition, public authority, or control.
28.8 Community-Run Networks
28.8.1 Community-run networks are locally governed physical, digital, sensor, communications, energy, data, observability, knowledge, or resilience networks operated or stewarded by communities, cooperatives, Indigenous bodies, neighbourhood groups, local institutions, or trusted public-good structures. They are a critical component of bottom-up Nexus Governance.
28.8.2 Community-run networks may include community broadband, mesh networks, sensor networks, local energy microgrids, water monitoring networks, community data trusts, public-health reporting networks, disaster-response networks, ecological monitoring groups, local AI and data stewardship groups, food distribution networks, or local resilience hubs.
28.8.3 These networks are necessary because centralized systems often fail to reach, understand, or protect local realities. Community-run networks can provide redundancy, trust, local ownership, rapid sensing, degraded-mode operation, and culturally appropriate governance. They help shift communities from passive consultation subjects to active governance participants.
28.8.4 Community-run networks must be governed with safeguards. Local control does not eliminate privacy, security, conflict, representation, data, AI, or inclusion risks. A community network may be captured by local elites, expose vulnerable people, mishandle data, exclude marginalized groups, or become dependent on a vendor. Governance must be explicit.
28.8.5 Community-run networks should connect to the national and regional rail only through consented, classified, and purpose-bound interfaces. A local sensor feed, community report, or protected dataset should not automatically flow upward. Local actors should decide what is public, public-safe, controlled, or restricted, subject to law and safeguards.
28.8.6 Community-run networks may support degraded-mode governance. During disasters, cyber outages, grid failures, conflict, extreme weather, or communications breakdown, local networks may maintain evidence, coordination, warnings, and public-safe communication. Nexus Governance should design for resilience, not only normal operation.
28.8.7 Community-run networks should have technical support without technical domination. GCRI-aligned methods, TMD guidance, universities, utilities, or technology partners may help, but the network’s local governance should not be displaced by outside technical providers.
28.8.8 The doctrine is direct:
Community-run networks make the rail resilient from below, giving communities governed technical capacity to observe, communicate, protect, and correct without becoming data sources for external extraction.
28.9 Local Evidence and Public-Safe Communication
28.9.1 Local evidence is the record-valid knowledge produced or held at local, community, municipal, bioregional, or subnational level. It may include lived experience, sensor data, public authority records, photographs, field notes, community testimony, Indigenous and local knowledge where permitted, utility data, environmental observations, health signals, infrastructure reports, social trust signals, and local history.
28.9.2 Local evidence is essential because national and global systems often see too slowly or too abstractly. Local evidence may reveal early warning, hidden harm, cumulative burden, false assumptions, ecological change, public authority gaps, or public mistrust. It can challenge official records and improve technical models.
28.9.3 Local evidence must be classified. Some evidence may be public. Some may be public-safe. Some may be community-sensitive, protected knowledge, personal, cyber-sensitive, public authority-sensitive, commercially sensitive, legally privileged, or unsafe to publish. Evidence value does not justify uncontrolled disclosure.
28.9.4 Local evidence should be connected to Case IDs where it informs a governance matter. It should identify source capacity, date, location or protected location class, method, confidence, restrictions, consent or permission status where relevant, public-safe use, and correction rights. This prevents local evidence from being detached from its context.
28.9.5 Public-safe communication at local level must be understandable and protective. Communities need to know what is happening, what is known, what is uncertain, what is being reviewed, what public authorities have or have not done, what safeguards exist, and how to seek correction. Local communication should avoid technical opacity and institutional overclaim.
28.9.6 Local public-safe communication must not expose people or places to harm. Maps, alerts, dashboards, reports, media statements, and community summaries should be reviewed for risks: retaliation, stigma, land pressure, panic, misinformation, protected knowledge exposure, cyber vulnerability, or infrastructure security.
28.9.7 Local evidence should be allowed to correct higher-level records. If a national dashboard says a system is functioning but local evidence shows failure, the local record must have an escalation route. If a public-safe report misstates community position, local actors must be able to correct it.
28.9.8 The doctrine is direct:
Local evidence gives the rail ground truth; public-safe communication gives communities trustworthy meaning. Both must be classified, protected, contextual, and correctionable.
28.10 Local Safeguards and Grievance Routes
28.10.1 Local safeguards and grievance routes are the protections and pathways that allow individuals, communities, Indigenous peoples, local organizations, workers, vulnerable groups, and affected persons to participate safely, report harm, challenge records, object to misuse, seek correction, and trigger escalation within Nexus Governance.
28.10.2 Local safeguards are necessary because harm is often felt locally before it is visible institutionally. A public-safe report may misrepresent a community. A data project may expose personal information. A sensor network may create surveillance concerns. A finance-readiness pathway may increase land pressure. A public authority process may intimidate participants. A dashboard may stigmatize a place. Local grievance routes allow the rail to hear and correct these harms.
28.10.3 Local safeguards should include non-retaliation, confidentiality, accessible reporting, language support, disability access, culturally appropriate process, protected knowledge protocols, public-safe mapping review, privacy controls, conflict management, community representation discipline, and emergency escalation.
28.10.4 Grievance routes should allow multiple forms of submission: written, oral, digital, offline, mediated, anonymous where appropriate, confidential, community-submitted, or submitted through trusted intermediaries. A governance system that only accepts formal digital complaints excludes many affected people.
28.10.5 Local grievance records should identify the issue, affected matter or Case ID where known, requested protection, confidentiality status, urgency, public authority implications, safeguards concerns, evidence supplied, and requested correction. Sensitive details should be protected.
28.10.6 Grievance routes must have response and closure. A grievance should not disappear into intake. The system should acknowledge, classify, route, investigate or review where appropriate, act or explain non-action, and provide public-safe or confidential response. Repeated grievances should trigger systemic review.
28.10.7 Local safeguards must include stop-the-line escalation where harm risk is serious. A local safeguards concern may require pausing publication, restricting data access, suspending a dashboard, halting a proof-pack release, correcting public claims, or notifying public authorities where required.
28.10.8 The doctrine is direct:
Local safeguards and grievance routes make correction reachable from the ground, ensuring that people closest to consequence can challenge the rail before harm becomes normalized.
28.11 Local-to-National Escalation
28.11.1 Local-to-national escalation is the pathway through which local, community, municipal, bioregional, watershed, corridor, ecosystem, university-hosted, utility-hosted, or subnational Nexus surfaces bring matters to the National Desk, National Council, National Working Grid, National Helix Councils, National Leadership Council, National Investor Councils, public authority interfaces, TMDs, GCRI, GRF, GRA, regional boards, or other competent bodies.
28.11.2 Escalation is necessary because local systems may identify matters beyond their authority or capacity. A local water signal may require national regulator review. A community grievance may require safeguards escalation. A data-centre concern may require energy, water, cyber, AI, and public authority review. A public-safe communication error may require GRF-aligned claims correction. A finance-readiness misuse may require GRA boundary enforcement. A technical issue may require TMD review.
28.11.3 Local-to-national escalation should be structured but accessible. The submitting local surface should identify the matter, location or protected location class, affected actors, evidence, urgency, requested action, safeguards concerns, public authority relevance, data sensitivity, and public-safe communication needs. Where local actors cannot complete formal forms, the National Desk should assist.
28.11.4 Escalation must preserve local meaning. National actors should not strip local evidence of context, culture, dissent, uncertainty, or restrictions. A community objection must not become a generic “stakeholder comment.” Protected knowledge must not become public data. Local refusal must not become unresolved consultation.
28.11.5 Escalation must include feedback. Local actors should know whether the matter was docketed, how it was classified, where it was routed, what action occurred, what remains pending, and how to request correction. Escalation without feedback becomes extraction.
28.11.6 Escalation should allow emergency pathways. Where harm is imminent, the local surface should be able to trigger incident mode, safeguards hold, public authority notification, or technical containment through appropriate channels.
28.11.7 Escalation must also allow national-to-local return. National findings, public-safe reports, maturity updates, proof-pack implications, or public authority clarifications should return to local surfaces in understandable form. Governance flow must be two-way.
28.11.8 The doctrine is direct:
Local-to-national escalation ensures that local truth can reach national authority and capacity without losing context, protection, or correction rights in transit.
28.12 Place-Based Correction
28.12.1 Place-based correction is the process by which local, community, municipal, bioregional, watershed, corridor, ecosystem, or subnational records correct errors, overclaims, omissions, outdated baselines, unsafe maps, public authority misstatements, technical inaccuracies, community misrepresentations, data misuse, AI errors, and public-safe communication failures affecting a specific place.
28.12.2 Place-based correction is necessary because higher-level systems often misread place. A national dashboard may show resilience where a community experiences failure. A regional map may omit protected knowledge. A public authority capacity record may overstate local approval. A proof pack may describe site truth incompletely. A technical baseline may ignore seasonal realities. A public-safe report may misrepresent community participation.
28.12.3 Place-based correction should be available to local public authorities, communities, Indigenous bodies, local labs, observatories, universities, utilities, civil society, workers, and affected persons. Correction should not be limited to institutions with formal power. People closest to consequence must be able to challenge records.
28.12.4 Place-based correction may take several forms: correction of a local record, amendment of a public-safe summary, restriction of a map, public authority capacity clarification, maturity downgrade, proof-pack revision, dashboard update, evidence reclassification, protected knowledge takedown, apology or public clarification, routeability hold, or escalation to national or regional bodies.
28.12.5 Place-based correction must propagate upward where dependent records exist. If a local baseline changes, national evidence packs may need update. If a public-safe map is corrected, regional dashboards may need update. If community participation was misrepresented, GRF-aligned public-facing records may need correction. If site truth affects routeability, GRA-aligned proof packs may need revision.
28.12.6 Place-based correction must be timely. Local harm can intensify if correction is delayed. The rail should define urgency categories and response times for high-risk corrections involving safety, protected knowledge, public authority overclaim, finance misuse, or public panic.
28.12.7 Place-based correction should preserve dignity. Correction is not only technical amendment. It may require recognizing harm, restoring trust, clarifying misuse, protecting participants, or changing process. A corrected record should not blame local actors for institutional misreading.
28.12.8 The doctrine is direct:
Place-based correction ensures that the rail can be corrected from where reality is lived, not only from where governance is administered.
28.13 Local Governance Records
28.13.1 Local Governance Records are the place-based records through which subnational, city, bioregional, watershed, ecosystem, community, Indigenous, local lab, community observatory, host-institution, and community-run network activities become valid within the Nexus rail. They are the local memory of evidence, participation, safeguards, public authority interface, public-safe communication, escalation, and correction.
28.13.2 Local Governance Records may include local Case IDs, intake records, community evidence records, protected knowledge permissions, public-safe summaries, local council records, local lab records, observatory data, sensor records, community meeting records, dissent records, grievance records, public authority capacity records, local dashboard records, host agreements, community-run network records, escalation records, correction records, and closeout records.
28.13.3 Local records must be classified. Some may be public. Some may be public-safe. Some may be community-controlled, Indigenous-protected, confidential, personal, cyber-sensitive, public authority-sensitive, legally restricted, or unsafe to disclose. Local records should not be forced into national visibility without classification and permission.
28.13.4 Local records must preserve source and context. A local observation should identify who submitted it or the protected source class, when, where or protected-location category, how it was observed, what restrictions apply, what confidence exists, whether verification is needed, and how correction may be requested. Context is part of truth.
28.13.5 Local records must distinguish participation states. Attendance, testimony, consultation, objection, consent, refusal, non-consent, withdrawal, silence, representation, and protected knowledge-sharing must not be collapsed. This is especially important for Indigenous and community records.
28.13.6 Local records must be interoperable without being extractive. They should be capable of informing national and regional evidence packs, dashboards, public-safe reports, proof packs, and maturity records, but only through purpose-bound, publication-classified, and safeguards-reviewed pathways.
28.13.7 Local records should be accessible to the communities they concern. Where safe, communities should be able to see public-safe versions of records, understand how their inputs were used, and request correction. A local record system that communities cannot access becomes another external archive.
28.13.8 The final doctrine of this chapter is direct:
Local Governance Records are the ground memory of Planetary Nexus Governance. They ensure that local truth, community participation, protected knowledge, public authority capacity, evidence, safeguards, escalation, and correction remain valid, protected, and connected to the wider rail without being extracted from place.
Last updated
Was this helpful?