Skip to content
StandardsCities and the built environmentStandards that apply
Cities and the built environment

Cities and the built environment: standards that apply

The 6 standards listed for cities and the built environment in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Cities and the built environment
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-0, NS-3, NS-5, NS-9, NS-10, NS-11.
  • Open standards: Sendai Framework for Disaster Risk Reduction 2015–2030; Making Cities Resilient 2030 resilience roadmap and scorecard; OGC CityGML 3.0; OGC API – Features; SpatioTemporal Asset Catalog (STAC) 1.0.
  • Data and feeds: Global Human Settlement Layer; WorldPop gridded population; Overture Maps buildings theme; OpenStreetMap; World Development Indicators.
  • Couples with: Construction and real estate; Water utilities and basins; Public sector and government; Energy utilities and grids.
Nexus Standards
6
NS-0, NS-3, NS-5
Standardên vekirî
5
named, never copied
Data and feeds
5
listed for reference
Girêdan
4
with other areas
01NS-0

Destûr û prensîb

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.

RêgezNivîs
NS0-P1Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied.
NS0-P2Machine-readable first · Every normative element exists as data (registry, schema, clause) before it exists as prose; prose explains, data governs. A standard with no machine form is not a Nexus Standard.
NS0-P3Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone.
NS0-P4Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes.
NS0-P5Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate.
NS0-P6Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant.
NS0-P7Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten.
NS0-P8Honest · A UNI identifies and resolves; it never certifies. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge.
NS0-P9Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class.
NS0-P10Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark.
NS0-P11Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed.
NS0-P12Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass.

Read NS-0 in full

02NS-3

UNIyên tomara xetereyê (rêzimanî, nexşeya veguhastina ji pergala kevin, desthilata veqetandinê)

Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.

NS-3 states its requirements in sections rather than in a table of rules.

Read NS-3 in full

03NS-5

Standarda wêne, nexşe û dîtbarkirinê (bi kîta UI/UX)

Status proposed · earth observation and digital twins; visual composition and workflows · NXS-STD-ST-000011.

RêgezNivîs
NS5-R1Every visual artefact shall carry a UNI in its metadata and in its caption.
NS5-R2Every rendered value shall trace to record UNIs and to a time of evaluation.
NS5-R3Missing, degraded and insufficient-evidence states shall be rendered explicitly; no such state shall be coerced to a value.
NS5-R4Licence-restricted or withheld features shall be counted and declared on the figure or map.
NS5-R5Every visual artefact shall carry the accessibility and cartographic declarations of section 4 that apply to it.

Read NS-5 in full

04NS-9

UNI yên çarçoveyî (belavkirin, mînak, mînakên bernameyê)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.

RêgezNivîs
NS9-R1Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve.
NS9-R2Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand.
NS9-R3The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context.
NS9-R4Closing a context shall not delete it: context.validUntil is set and the status becomes WITHDRAWN an SUPERSEDED bi supersededBy.
NS9-R5Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere.

Read NS-9 in full

05NS-10

Polîtîka û xal (erkên ku makîne dikare bixwîne: pênase, girêdanî, nirxandin û sepandin)

Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.

RêgezNivîs
NS10-R1Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it.
NS10-R2Subjects shall be contextual UNIs; names, labels or free text shall not bind.
NS10-R3The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs.
NS10-R4External obligations shall be cited, not copied.
NS10-R5Failure effects shall be typed; refuse is the default for blocking clauses in production contexts.
NS10-R6A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review.
NS10-R7Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record.

Read NS-10 in full

06NS-11

Piştrastkirin û çavdêrî (delîl, erêkirin, çavdêriya lihevhatina zero-trust)

Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.

RêgezNivîs
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.

Read NS-11 in full

07Pirs

Pirs û bersiv.

Are these all the rules for cities and the built environment?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
Standards

Shape the standards for cities and the built environment.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

Rewş û bikaranîn. Nexus Standards standardên pêşniyarkirî ne ku bi pêvajoyeke vekirî di bin NS-13 de hatine pêşxistin û ji bo bikaranîna dilxwazî hatine weşandin; ew ne belgename, ne akreditasyon û ne pejirandina rêkxistinê ne, û pejirandin biryara Encûmena Standardên Cîhanî û, li her welatî, ya Encûmena Standardên Neteweyî ya wê dimîne. UNI (Unique Nexus Identifier) berhemekê nas dike; wê belgename nake. Navên desteyên standardan û standardên wan aîdî parêzvanên wan in û tenê ji bo naskirina belgeyan têne bikaranîn; tu nivîsa standardeke derve li vir nayê dubarekirin. Nexus Standards bi tu desteya standardan a li vir hatiye binavkirin ve ne girêdayî ye, ji aliyê wê ve nayê piştgirîkirin û belgename nekiriye.

Lîsans: CC BY 4.0 ji bo nivîsa standardan, tomargeh, şema û daneyan; Apache-2.0 ji bo koda referansê. Standardên derve bi nav, hejmar û girêdanê di bin lîsansên xwe de têne jêgirtin. Dane, pirtûkxane û fontên aliyê sêyem lîsansên xwe diparêzin: binêre Agahdariyên aliyê sêyem.