Engines
Adjudicators & Execution Cores of the Fabric
Overview
In SNF, an Engine is a long‑running, verifiable service that evaluates Clauses and enforces Articles. Engines subscribe to the Sovereign Genesis Bus (SGB), apply Policy Guard checks, emit Binding Policy Resolutions (BPR), and publish cryptographic attestations (QSS + ChronoFlux/ZKChronoSeal). This page defines the normative engine set for SNF v2.0 and their execution semantics.
Engine Catalogue
Policy Arbitration Engine (PAE)
Maps cross‑jurisdictional conflicts to computable resolutions. Inputs: policy refs, facts, evidence bundles. Outputs: signed BPR with lineage and ΔΣ score.
RecommendedNASI Engine
Neural–Anthropic Symbolic Interface for human‑in‑the‑loop deliberation. Converts natural‑language positions into formal policy facts under 817 constraints.
CandidateChronoFlux Engine
Schedules multi‑anchor time‑seals for lineage roots; coordinates ZKChronoSeal publication for sensitive deployments.
RecommendedCodex Symbolica Engine
Applies symbolic reasoning over constitutional invariants; validates LogicSeal bindings and meta‑policy consistency (MetaSentinel).
CandidateCodex Wall Resonance Engine
Detects resonance breaches across mirrored policy walls; integrates EchoClash to prevent adversarial replays.
ResearchHelvetica Constitutionalis Engine
Swiss‑grade comparative law engine; harmonizes multilingual statutes into Standard‑817 ontologies.
CandidateMarket Dreamscope Engine
Applies Articles to financial data flows; ensures rights‑preserving analytics for market telemetry.
ResearchBond Sentiment Decoder Engine
Evaluates sovereign risk disclosures; exposes SBI/IEV priors to PAE.
ResearchExecution Architecture
APIs & Schemas
Engine Capability Descriptor
{ "$id": "https://schema.constitutionfabric.org/snf.v2.engine-cap.json", "type": "object", "required": ["id","version","family","articles","clauses","endpoints"], "properties": { "id": {"type":"string"}, "version": {"type":"string"}, "family": {"enum":["pae","nasi","chronoflux","symbolica","resonance","helvetica","dreamscope","bonddecoder"]}, "articles": {"type":"array","items":{"type":"string"}}, "clauses": {"type":"array","items":{"type":"string"}}, "endpoints": {"type":"array","items":{"type":"string","format":"uri"}}, "attestations": {"type":"boolean"}, "ballot": {"type":"string","format":"uri"} } }
Binding Policy Resolution (BPR)
{ "$id": "https://schema.constitutionfabric.org/snf.v2.bpr.json", "type": "object", "required": ["id","engine","input","decision","attestation","time"], "properties": { "id": {"type":"string"}, "engine": {"type":"string"}, "input": {"type":"object"}, "decision": {"type":"object"}, "attestation": {"type":"string"}, "lineage": {"type":"string"}, "time": {"type":"string","format":"date-time"} } }
Execution Semantics
- Determinism Envelope: Engines MUST provide deterministic outputs for identical inputs within a fixed epoch and capability profile.
- Policy First: Policy Guard MUST run pre‑ and post‑conditions; failures are signed with explanatory BPR‑errors.
- Proof Duty: All decisions MUST be signed (QSS) and time‑sealed (ChronoFlux/ZKChronoSeal).
- Privacy Budget: GhostFrame/EchoSentinel MUST be available; activation is driven by IEV/SBI priors.
Deployment Tiers
Tier | Profile | Requirements | Typical Use |
---|---|---|---|
Edge | Light | Read‑only registries; verify proofs; emit local ΔΣ | Clients, gateways |
Core‑A | Standard | PAE + ChronoFlux; publish attestations | Institutions |
Core‑AA | Hardened | + ZKChronoSeal, GhostFrame/EchoSentinel | Research clouds |
Core‑AAA | Sovereign | Public audit API; Council ballots; EchoClash | National/critical infra |
Observability
Metrics
BPR latency, ΔΣ anomaly rate, revocation lag, attest publish SLA, IEV exposure, privacy‑epoch activation.
Audit API
Public read‑only endpoints for lineage roots, inclusion proofs, BPR catalogs, and revocation streams.
Interop & Standards
- All engines MUST register capabilities and publish signed snapshots per Standard‑817.
- License: SOSL v1.0 applies to code and reference deployments; invariants MUST remain enabled.
- Wire format: SGB messages use canonical JSON with LogicSeal commitments.
Worked Examples
1) Cross‑border Erasure (PAE + ChronoFlux)
{ "op":"nullify", "subject":{"did":"did:cf:EU:abc"}, "policy":{"refs":["gdpr.17","ccpa.1798.105"],"version":"817.2"}, "facts":{"storage":"US‑cloud‑X","age":">30d"}, "attachments":{"qss":"sig:dilithium:…","logicseal":"hash:…"} } // PAE decision → BPR {"decision":{"action":"erase","deadline":"P7D"},"ΔΣ":0.02,"att":"sig:…","seal":"seal:chronoflux:ledgerY:tx42"}
2) Human–AI Concord (NASI)
{ "op":"deliberate", "topic":"public‑interest‑research", "positions":["ethics‑board:allow with safeguards","citizen‑panel:allow"], "constraints":["ucl.1","csg.1"], "attachments":{"ghostframe":"epoch:ghostframe:g2:2026‑01‑01T00:00:00Z"} } // NASI emits structured facts with provenance ready for PAE.
Security Considerations
- PQC Agility: Dual‑stack signature support during eclipse rollovers.
- Revocation Safety: Hard fail closed on key revocation; publish compensating events.
- Privilege Minimization: Separate attestation signing from engine runtime via HSM.
- Side‑Channel Hygiene: Normalize timing; redact sensitive traces in public proofs.
Appendix — Status Matrix
Engine | Status | Articles | Clauses | Conformance |
---|---|---|---|---|
Policy Arbitration Engine | Recommended | I, III, V, IX, X | QSS, LogicSeal, ΔΣ, ZKChronoSeal | Core‑A → AAA |
NASI Engine | Candidate | IV, IX | GhostFrame, EchoSentinel, IEV | Core‑AA → AAA |
ChronoFlux Engine | Recommended | X | ChronoFlux, ZKChronoSeal | Edge → AAA |
Codex Symbolica | Candidate | X | LogicSeal Review, MetaSentinel | Core‑A → AA |
Resonance Engine | Research | II, X | EchoClash | AA → AAA |
Helvetica Constitutionalis | Candidate | X | ΔΣ | Core‑A → AA |
Market Dreamscope | Research | X | ΔΣ, FameVector | AA |
Bond Sentiment Decoder | Research | X | IEV, SBI | AA |