Skip to content

Implementation Gaps in the DIA Constitutional Layer

Document Status

Field Value
policy-id DIA-CONST-GAPS-001
type Architectural review / backlog of implementing documents
version 0.1.0-draft
date 2026-03-10

Purpose of the Document

This document collects the gaps that remain after completion of the Constitution and the first documents under doc/normative/50-constitutional-ops/. It has no normative force; it serves to organize the next implementation steps.

Recently Closed

FEDERATION-MEMBERSHIP-AND-QUORUM.md

Closed on 2026-03-10 by document DIA-FED-001, which defines:

  • the statuses of active, dormant, suspended, and retired federations,
  • the minimum activity criteria,
  • electorate snapshot, quorum, and decision classes,
  • the rules for losing veto rights by a dead federation.

PROCEDURAL-REPUTATION-SPEC.md

Closed on 2026-03-12 by document DIA-PROC-REP-001, which defines:

  • reputation domains and signal types,
  • the definition of an active node for reputation purposes,
  • bootstrap and bootstrap restrictions,
  • a portable evidence package instead of naked score transfer,
  • cartel-detection hooks and connection to health metrics M1-M5.

PANEL-SELECTION-PROTOCOL.md

Closed on 2026-03-12 by document DIA-PANEL-SEL-001, which defines:

  • panelist eligibility,
  • entropy source and auditable panel draw,
  • COI, veto, and composition-replacement procedure,
  • escalation to an inter-federation pool,
  • panelist identity-disclosure levels and relation to appeal.

ABUSE-DISCLOSURE-PROTOCOL.md

Closed on 2026-03-12 by document DIA-ABUSE-DISC-001, which defines:

  • prohibition on general investigation without a credible present-day signal,
  • conditions for entering the full case history,
  • stake-level and evidence-level thresholds,
  • multisig roles, disclosure scope, retention, appeal, and jurisdictional notifications.

ROOT-IDENTITY-AND-NYMS.md

Closed on 2026-03-12 by document DIA-ROOT-ID-001, which defines:

  • the separation of root-identity, anchor-identity, node-id, nym, station-id, and agent-id,
  • identity assurance levels (IAL0-IAL4),
  • the rule "greater influence -> greater disclosure and stronger confirmation",
  • a multisig attestation model for jurisdictions without strong eID,
  • limits on multiplying influence through many nyms from one anchor source.

IDENTITY-ATTESTATION-AND-RECOVERY.md

Closed on 2026-03-12 by document DIA-ID-REC-001, which defines:

  • first attestation of root-identity,
  • memory of prior attestation for anchor-identity,
  • the role of the recovery phrase, salt, and KDF parameters,
  • reconstruction of anchor-identity without repeated full attestation,
  • the procedure for identity-data update and revocation.

ATTESTATION-PROVIDERS.md

Closed on 2026-03-12 by document DIA-ATTEST-PROVIDERS-001, which defines:

  • the attestation-strength classes weak / strong,
  • the default mapping from methods to maximum IAL,
  • restrictions for phone numbers and other low-evidence sources,
  • weak -> strong upgrade rules without loss of anchor continuity.

IDENTITY-UPGRADE-ANOMALY-SIGNALS.md

Closed on 2026-03-12 by document DIA-ID-UPGRADE-ANOM-001, which defines:

  • signal classes A1-A8 for attestation upgrade,
  • minimum response levels monitor, soft_hold, manual_review, hard_block,
  • the default profile for phone -> strong,
  • the relation between attestation upgrade and procedural dispute.

IDENTITY-UNSEALING-BOARD.md

Closed on 2026-03-12 by document DIA-SEAL-BOARD-001, which defines:

  • the Federation of Sealed Chambers as a redundant IRL organ,
  • thresholds U1-U3 for descent nym -> node-id -> root-identity,
  • multi-chamber and cross-jurisdictional quorum,
  • split knowledge for mapping node-id -> root-identity,
  • appeal from full-unsealing decisions.

UNSEAL-CASE-MODEL.md

Closed on 2026-03-12 by document DIA-UNSEAL-CASE-001, which defines:

  • a shared unseal_case model for thresholds U1-U3,
  • a separate decision record with scope, side effects, and appeal window,
  • minimal fields for retention, COI, panel, and notifications,
  • the rule that scope escalation does not overwrite case history.

ROLE-TO-IAL-MATRIX.md

Closed on 2026-03-12 by document DIA-ROLE-IAL-001, which defines:

  • the minimum map from role classes to IAL0-IAL4,
  • the rule that IAL is mainly a gate, not an influence multiplier,
  • the fixed_power_bonus cap of <= 1%,
  • default minimums for panels, sealed chambers, and high-stake roles.

FIP-MEMBERSHIP-AND-QUORUM.md

Closed on 2026-03-12 by document DIA-FIP-QUORUM-001, which defines:

  • chamber statuses from candidate to retired,
  • minimum conditions for active status,
  • default quorum 2 of 3 for U2 and 3 of 5 for U3,
  • emergency mode, composition snapshot, and jurisdictional diversity rules.

SWARM-ECONOMY-SUFFICIENCY.md

Closed on 2026-03-21 by document DIA-SUFF-001, which defines:

  • the operational model of the sufficiency threshold and tapering band,
  • permissible classes of concentration brakes and the anti-pyramid test,
  • the minimal data model of federation economic policy,
  • common circulation of surpluses and their destination classes,
  • the barrier between economic reward and procedural power.

RAW-SIGNAL-POLICY.md

Closed on 2026-03-21 by document DIA-RAW-001, which defines:

  • the modes raw / structured / transformed / redacted,
  • permissible bases for signal transformation,
  • mandatory meta-markers for AI intervention,
  • the minimal audit trace for utterance transformation,
  • compliance tests against hidden aestheticization and professionalization.

UNIVERSAL-BASIC-COMPUTE.md

Closed on 2026-03-21 by document DIA-UBC-001, which defines:

  • the minimal Proof-of-Personhood model without default de-anonymization,
  • the non-withdrawable minimum of compute for communication, orientation, and protective modes,
  • limited cross-federation portability: unlimited emergency plus limited communication and care,
  • the data models proof_of_personhood_attestation, ubc_allocation, and ubc_settlement,
  • public funding sources for UBC and compliance tests against hidden exclusion.

UBC-LIMIT-PROFILES.md

Closed on 2026-03-21 by document DIA-UBC-LIMITS-001, which defines:

  • the canonical profiles emergency_unlimited, communication_limited, and care_limited,
  • the minimal bridge_minimum profile for PoP recognition through the FIP bridge/registry,
  • the portability profiles local_only, trans_federation_limited, and trans_federation_extended,
  • the explicit FIP bridge record model and the rule that federations may only extend limits,
  • compliance tests against nominal cross-federation PoP recognition without real access.

Priority A - Required Before Real Governance Goes Live

After closing PROCEDURAL-REPUTATION-SPEC.md, PANEL-SELECTION-PROTOCOL.md, and ABUSE-DISCLOSURE-PROTOCOL.md, there is currently no open Class A gap. The minimum governance layer now has the three implementing acts that were previously missing.

Priority B - Required Before Higher-Stakes Autonomy and Sensorium

1. EMERGENCY-ACTIVATION-CRITERIA.md

Closed on 2026-03-28 by DIA-EMRG-ACT-001, which defines:

  • trigger classes TC1-TC5,
  • credibility thresholds C0-C4,
  • the sensorium -> evaluation -> activation pipeline,
  • default TTLs, extension rules, and mandatory review,
  • and a TC2 subclass for council:did:key compromise with trapdoor freeze, emergency key rotation, and ad-hoc audit panel requirements.

2. SENSITIVE-DATA-REDUCTION.md

Why it is missing: publication, whistleblowers, exceptions, and onboarding refer to redaction of sensitive data, but there is no shared standard of redaction and disclosure.

What it must define:

  • classes of sensitive data,
  • levels of redaction,
  • rules of selective disclosure,
  • minimum audit traces without deanonymization.

Priority C - Required Before Federation-Scale Expansion

3. ROLE-REGISTRY.md

Why it is missing: the Constitution and supplements use notions such as "public-trust role," "operator," "red team," and "panel," but they do not have a shared role registry.

What it must define:

  • catalog of base roles,
  • minimum permissions and forbidden role combinations,
  • screening requirements,
  • paths of rotation and substitutability.

4. TRACE-MINIMUM.md

Why it is missing: agent autonomy, exceptions, reputation, and constitutional defense require action traces, but they do not yet have a shared minimum schema.

What it must define:

  • required trace fields,
  • relation trace -> audit -> appeal,
  • retention classes,
  • trace versioning and signatures.

Final Note

The most critical gaps of the governance layer have been closed by EXCEPTION-POLICY.md, FEDERATION-MEMBERSHIP-AND-QUORUM.md, PROCEDURAL-REPUTATION-SPEC.md, PANEL-SELECTION-PROTOCOL.md, and ABUSE-DISCLOSURE-PROTOCOL.md. The next logical step is to specify emergency activation criteria, sensitive-data redaction, and the minimum action-trace schema, so the implementing layer is equally coherent outside disputes and governance.