Skip to content
Constitution Fabric SNF v2.0

Standard 817

Constitutional Baseline for Rights‑Preserving Computation

Status: Candidate Recommendation
Maintainer: Sovereign Governance Council
Applies to: Engines, Protocols (Articles), Clauses, Tools
License: SOSL v1.0 (code) · CC BY‑SA 4.0 (spec)

1. Scope & Goals

Standard 817 defines the normative baseline for the Sovereign Constitution Fabric (SNF) so that independent implementations remain interoperable, auditable, and rights‑preserving across jurisdictions. The standard specifies terminology, rule hierarchy, conformance levels, registry structures, schemas, and test suites. It binds computation to constitutional guarantees rather than platform policies.

  • Make rights first‑class operations with verifiable evidence surfaces.
  • Resolve cross‑jurisdiction conflicts via a transparent, machine‑auditable formalism.
  • Enable public oversight through open registries and revocation channels.

2. Definitions (Normative)

Instrument

Universal unit in SNF (protocol, engine, tool, dataset, policy, proof). Has Ports, State, Controls, Lineage, Attestations, Jurisdiction Hooks.

Article

Protocol that embodies a constitutional right (e.g., InfinityWipe for erasure).

Clause

Algorithmic sub‑rule used by Articles/Engines (e.g., QSS, LogicSeal, ΔΣ, ZKChronoSeal).

PAE

Policy Arbitration Engine producing a Binding Policy Resolution (BPR) for conflicts.

Attestation

Cryptographic evidence of a state transition; published to public registries.

Nullification

Revocation of trust via attestation withdrawal and public notice (InfinityWipe semantics).

Non‑normative terms are collected in the Glossary.

3. Rule Hierarchy

When policies conflict, implementations must follow the 817 ordering to select outcomes that preserve rights and legality.

(1) Lex Originis Law of data origin (2) Lex Loci Law(s) of processing location(s) (3) Standard‑817 Meta‑Rule Tie‑break by maximal rights preservation,reversibility, and public verifiability
817 ordering for conflict resolution (normative).

Outcome Artifact. The decision must be serialized as a BPR with rationale and evidence references.

4. Conformance Levels

Standard 817 defines three levels. Vendors must publish their declared level and pass the corresponding tests.

Level A — Proof‑Aware

  • Implements SGB envelope and PQC signatures (QSS).
  • Publishes attestation hashes to a lineage registry.
  • Supports BPR import (read‑only).

Level AA — Policy‑Adherent

  • Includes Policy Guard and PAE client.
  • Produces BPR under conflicts; exposes reasoning graph.
  • Supports UCL, InfinityWipe, QOS Articles minimally.

Level AAA — Sovereign‑Grade

  • Full Article set incl. CSG‑1, Eclipse, NASI constraints.
  • Runs public proof publisher (ZKChronoSeal, ΔΣ overlays).
  • Operates revocation channel; participates in Council ballots.

5. Public Registries (IANA‑like)

To ensure predictable interop and public oversight, 817 establishes open registries:

  • Article Registry: IDs, versions, status, security notes.
  • Clause Registry: Algorithm identifiers (e.g., qss‑dilithium2, zk‑chronoseal‑v1).
  • Policy Registry: Policy code references (e.g., gdpr.17, hipaa.164.526).
  • Attestation Registry: Public hashes, anchors, revocations, tombstones.
Registries must be append‑only with cryptographic inclusion proofs; mirrorable by third parties.

6. Normative Schemas (Excerpts)

6.1 Message Envelope (snf.v2.op)

{
  "$id": "https://schema.constitutionfabric.org/snf.v2.op.json",
  "type": "object",
  "required": ["msg","op","subject","policy","jurisdiction","time","nonce"],
  "properties": {
    "msg": { "const": "snf.v2.op" },
    "op": { "enum": ["attest","nullify","publish","revoke","compose"] },
    "subject": { "type": "object", "required": ["did"], "properties": {
      "did": { "type": "string" },
      "labels": { "type": "array", "items": {"type": "string"} }
    }},
    "jurisdiction": { "type": "object", "required": ["origin"], "properties": {
      "origin": {"type": "string"},
      "loci": { "type": "array", "items": {"type":"string"} }
    }},
    "policy": { "type":"object", "required":["version"], "properties":{
      "refs": {"type":"array","items":{"type":"string"}},
      "version": {"type":"string"}
    }},
    "attachments": { "type": "object", "properties": {
      "qss": {"type":"string"},
      "logicseal": {"type":"string"}
    }},
    "payload": { "type": "object" },
    "time": { "type": "string", "format": "date-time" },
    "nonce": { "type": "string" }
  }
}

6.2 Binding Policy Resolution (BPR)

{
  "$id": "https://schema.constitutionfabric.org/snf.v2.bpr.json",
  "type": "object",
  "required": ["decision","rationale","evidence","signatures","lineage"],
  "properties": {
    "decision": { "enum": ["allow","deny","modify"] },
    "rationale": { "type":"string" },
    "evidence": { "type":"array", "items": {"type":"string"} },
    "signatures": { "type":"array", "items": {"type":"string"} },
    "lineage": { "type":"string" }
  }
}

7. Interoperability Requirements

  • Identifiers: DIDs for subjects; stable URNs for Articles/Clauses.
  • Transport: HTTP/2 or gRPC; binary and JSON encodings must be equivalent.
  • AuthN/Z: QSS for signatures; OIDC bridges allowed with rights labels.
  • Policy Input: OPA/Rego import must be supported with 817 mappings.
  • Proofs: ZKChronoSeal outputs must be reproducible and publicly verifiable.

8. Test Suites & Metrics

Conformance Tests

  • Protocol state machines (InfinityWipe, UCL, QOS) vs. golden traces.
  • PAE conflict scenarios (GDPR×CLOUD Act; HIPAA×research exception).
  • Attestation publication and revocation timing windows.

Operational Metrics

  • Proof publication latency; inclusion proof depth.
  • Policy fidelity score; reversibility index.
  • Societal indices: SBI, IEV (trendlines).

9. Security Considerations

  • Use post‑quantum signatures (Dilithium/SPHINCS+); rotate via Eclipse Protocols.
  • Publish lineage anchors with ΔΣ overlays to detect non‑monotonic histories.
  • Defend against correlation: GhostFrame/EchoSentinel epochs for unlinkability.
  • Require multi‑party approval for high‑risk operations; log intent + approvals.

10. Internationalization

All human‑readable outputs should provide language tags (BCP‑47). Policy references must use neutral codes (e.g., gdpr.17) and allow jurisdiction overlays (e.g., gdpr.17@DE).

11. Versioning & Lifecycle

  • Semantic Versioning: MAJOR for breaking changes; MINOR for additive; PATCH for fixes.
  • Stability Ladders: Draft → Candidate → Recommended → Deprecated → Retired.
  • Sunsets: Eclipse Protocols coordinate cryptographic and schema deprecations.

12. Worked Examples

12.1 Erasure with Cross‑Border Processing

// Request (snf.v2.op)
{"op":"nullify","subject":{"did":"did:cf:123"},
 "jurisdiction":{"origin":"EU","loci":["US"]},
 "policy":{"refs":["gdpr.17","cloudact.702"],"version":"817.2"},
 "attachments":{"qss":"sig:dilithium:…"},
 "payload":{"class":"PII","scope":"full"},
 "time":"2025-09-07T20:31:12Z","nonce":"…"}

// PAE → BPR (excerpt)
{"decision":"allow","rationale":"gdpr.17 precedence; US locus retained for logs",
 "evidence":["hash:…"],"signatures":["sig:…"],"lineage":"merkle:…"}

12.2 Consent Revocation

{"op":"revoke","subject":{"did":"did:cf:abc"},
 "policy":{"refs":["ucl.1"],"version":"817.2"},
 "payload":{"reason":"revoked_consent"},
 "attachments":{"logicseal":"hash:blake3:…"}}

13. Glossary (Non‑Normative)

  • ΔΣ overlay: Time‑series lens exposing anomalies in lineage.
  • BPR: Binding Policy Resolution (signed decision artifact).
  • Genesis Bus: The typed message spine of SNF.
  • NASI: Neural‑Anthropic Symbolic Interface (safe intent translation).
  • UCL: Universal Consent Layer.