UCV Formal Specification v0.1.0
The constitutional model for how sovereign entities observe, understand, and reason about constitutional state — making the invisible architecture of governance visible to the humans it serves.
Preamble
This document is the formal specification of the Universal Constitutional Viewport (UCV) — a constitutional layer providing the model of observation across all of ICore. UCV answers the question: "How is constitutional computing made visible, understandable, and auditable?"
UCV does not implement any specific visualization engine, rendering library, or analytics framework. UCV is the constitutional model of observation — it defines what a viewport means, what it means to observe constitutional state, what it means to reason about constitutional processes, and what it means to detect anomalies. Any conforming visualization implementation must satisfy UCV's axioms and invariants, but UCV itself specifies no rendering engine, no chart type, no display technology.
Without UCV, constitutional computing is invisible — correct, sovereign, but opaque. With UCV, constitutional computing becomes transparent: every trust chain, every provenance record, every attestation, every delegation, every revocation can be seen, understood, and verified by the humans it governs.
This specification answers the constitutional question: How is meaning observed? It defines the invariants that observation must satisfy — the properties that hold true regardless of rendering engine, display technology, or visualization method. UCV specifies no renderer; it specifies what any conforming renderer must guarantee.
Classification: Constitutional — defines the observation model for all of ICore.
Derivation:
Reference Systems (L5) → UCV (constitutional observation model)
Depends on: Reference Systems (observation requires a foundation of data systems to observe). Transitively, UCV depends on everything below L5 — observation must consume state produced by the entire constitutional stack.
Depended on by: USR/CoreFab (runtimes need to be observable), UCA (adapters may bridge to rendering engines that UCV governs), P3: Life (constitutional agents must be visually auditable).
Section 1: Foundational Axioms
1.1 The Seven Observation Axioms
| # | Axiom | Statement | Derived From |
|---|
| VA1 | Constitutional state is inherently observable. | Every piece of constitutional state — every key, every delegation, every attestation, every provenance record — is observable. No constitutional state may be hidden by the viewport. Opacity is unconstitutional. | Existence (USCP) |
| VA2 | Observation preserves constitutional integrity. | Observing state must not alter, corrupt, or destroy it. A viewport is read-only with respect to the state it observes. Observation that mutates constitutional state without explicit authorization is unconstitutional. | Constraint (USCP) |
| VA3 | Trust chains are visually traversable. | Every delegation path, every trust anchor connection, every chain of authority must be visually traceable from any subject to its constitutional origin. Gaps in visual trust chains indicate constitutional faults. | Identity (USCP) |
| VA4 | Provenance is visually reconstructible. | The complete history of any constitutional artifact — its creation, modification, delegation, and verification — must be visually reconstructible from its provenance chain. Invisible history is unconstitutional. | Transformation (USCP) |
| VA5 | Anomalies are visually salient. | Constitutional violations — revoked keys, expired delegations, tampered records, broken trust chains — must be visually prominent. A viewport that obscures anomalies is unconstitutional. | Verification (USCP) |
| VA6 | Observation is adapter-agnostic. | The viewport model must work regardless of rendering technology — Canvas, WebGL, SVG, terminal ASCII, AR/VR, or any future medium. Constitutional observation is not bound to any display technology. | Relationship (USCP) |
| VA7 | Observation is time-aware. | The viewport must be able to represent constitutional state at any point in time — past, present, or projected future based on policy. Temporal observation is a constitutional right. | Constraint (USCP) |
1.2 Axiom Sufficiency
| Primitive | Present In | Role |
|---|
| Existence | VA1 (state is observable) | Constitutional state exists to be seen |
| Identity | VA3 (trust traversable) | Trust chains are identity chains made visible |
| Relationship | VA6 (adapter-agnostic) | Observation adapts to any medium while preserving meaning |
| Constraint | VA2 (integrity preserved) | Observation must not violate constitutional constraints |
| Transformation | VA4 (provenance reconstructible) | History is transformed into visible, understandable form |
| Verification | VA5 (anomalies salient) | Anomalies must be visually verifiable |
All six primitives covered. The foundation is complete.
Section 2: The Viewport Model
2.1 Definitions
| Term | Definition |
|---|
| Viewport | A constitutional observation interface that renders state from the constitutional stack into a human-comprehensible form. |
| Viewport Adapter | A specific rendering technology (Canvas, WebGL, SVG, Terminal, AR/VR) that implements the viewport interface for a particular display medium. |
| Observation Target | Any constitutional state element — keys, delegations, attestation chains, provenance records, trust anchors — that can be observed through a viewport. |
| Observation Frame | A snapshot of constitutional state at a specific point in time, used for temporal observation. |
| Visual Taxonomy | The classification system for constitutional state elements in the viewport — trust, provenance, attestation, delegation, revocation. |
| Anomaly Signal | A visual indicator that a constitutional violation has been detected — revoked key, expired delegation, tampered record, broken chain. |
| Observation Session | A bounded period of active observation, with its own temporal frame and observation targets. |
2.2 The Constitutional Viewport Stack
┌═══════════════════════════════════════════════════════════════════┐
║ CONSTITUTIONAL VIEWPORT STACK ║
║ ║
║ ┌─────────────────────────────────────────────────────────────┐ ║
║ │ OBSERVATION LAYER │ ║
║ │ Trust Chain View │ Provenance View │ Attestation View │ ║
║ │ Delegation View │ Key Lifecycle │ Anomaly View │ ║
║ └──────────────────────────┬──────────────────────────────────┘ ║
║ │ ║
║ ┌──────────────────────────┴──────────────────────────────────┐ ║
║ │ CONSTITUTIONAL VIEWPORT │ ║
║ │ Rendering → Observation → Temporal → Anomaly Detection │ ║
║ └──────────────────────────┬──────────────────────────────────┘ ║
║ │ ║
║ ┌──────────────────────────┴──────────────────────────────────┐ ║
║ │ VIEWPORT ADAPTERS │ ║
║ │ Canvas │ WebGL │ SVG │ Terminal │ AR/VR │ [Future] │ ║
║ └──────────────────────────┬──────────────────────────────────┘ ║
║ │ ║
║ ┌──────────────────────────┴──────────────────────────────────┐ ║
║ │ CONSTITUTIONAL STATE (UCS) │ ║
║ │ Trust │ Provenance │ Attestation │ Delegation │ Keys │ ║
║ └─────────────────────────────────────────────────────────────┘ ║
║ ║
└═══════════════════════════════════════════════════════════════════┘
2.3 The Viewport Interface
Every conforming viewport adapter MUST implement:
interface UCVViewport {
// Core lifecycle
init(state: UCSInterface) → Promise<void>
render(frame: ObservationFrame) → Promise<RenderResult>
destroy() → void
// Observation targets
observe(target: ObservationTarget) → ObservationHandle
unobserve(handle: ObservationHandle) → void
listObservations() → ObservationTarget[]
// Temporal
setFrame(frame: ObservationFrame) → void
getCurrentFrame() → ObservationFrame
getAvailableFrames() → ObservationFrame[]
// Anomaly detection
onAnomaly(callback: (signal: AnomalySignal) → void) → void
clearAnomalies() → void
getAnomalies() → AnomalySignal[]
// Rendering
resize(width: number, height: number) → void
export(format: 'png' | 'svg' | 'json') → Promise<ExportResult>
}
Section 3: Observation Targets
3.1 The Seven Observation Targets
| # | Target | What It Observes | Visual Form |
|---|
| OT1 | Trust Chain | Trust anchors, delegation paths, chain depth, chain validity | Tree/graph with anchor at root, delegations as edges |
| OT2 | Provenance Chain | Creation → modification → verification history | Linear timeline with signed nodes |
| OT3 | Attestation Chain | Component attestations, operation history, verification status | Event stream with signature badges |
| OT4 | Key Lifecycle | Key creation → rotation → revocation → expiration | Timeline with state transitions |
| OT5 | Delegation Map | All active delegations, their confidence levels, expiry | Network graph with confidence-weighted edges |
| OT6 | Revocation Status | Revoked keys, revocation reasons, propagation | Alert overlay on affected targets |
| OT7 | Anomaly Dashboard | All detected constitutional violations | Prominent alert panel with severity indicators |
3.2 Observation Priority
Anomalies (VA5) always render at highest priority. Within normal state:
| Priority | Target | Rationale |
|---|
| 1 | Revocation Status | Security-critical; must never be hidden |
| 2 | Anomaly Dashboard | Constitutional violations require immediate attention |
| 3 | Trust Chain | Foundation of all constitutional authority |
| 4 | Key Lifecycle | Keys underpin all cryptographic operations |
| 5 | Delegation Map | Shows authority distribution |
| 6 | Provenance Chain | Historical record, important but less urgent |
| 7 | Attestation Chain | Component-level verification |
Section 4: Invariants
4.1 The Twelve Viewport Invariants
| # | Invariant | Statement | Classification |
|---|
| V1 | Read-Only Observation | The viewport MUST NOT modify, create, or delete any constitutional state. Observation is strictly read-only. | Critical |
| V2 | Completeness | The viewport MUST be capable of observing all constitutional state. No state element may be excluded from observation by design. | Critical |
| V3 | Temporal Integrity | When observing state at a specific time, the viewport MUST render that state accurately. Temporal observation MUST NOT mix states from different times. | Critical |
| V4 | Anomaly Salience | Constitutional violations MUST be rendered with higher visual prominence than normal state. Anomalies MUST NOT be obscured by other visual elements. | Critical |
| V5 | Chain Continuity | Trust chains, provenance chains, and attestation chains MUST be rendered as continuous, unbroken visual paths. Gaps MUST be visually flagged. | Major |
| V6 | Adapter Independence | The viewport model MUST work identically across all adapter technologies. No observation behavior may depend on the specific rendering engine. | Major |
| V7 | Signature Visibility | Every signed element (delegation, attestation, provenance record, revocation) MUST display its cryptographic signature status — valid, invalid, or unverified. | Major |
| V8 | State Synchronization | The viewport MUST reflect current constitutional state within one observation cycle. Stale state MUST be visually indicated. | Major |
| V9 | Accessibility | The viewport MUST provide non-visual observation modes (screen reader, text-based, haptic) for accessibility compliance. | Major |
| V10 | Export Integrity | Exported viewport state (PNG, SVG, JSON) MUST accurately represent the observed state at the time of export. | Moderate |
| V11 | Performance Bounds | Rendering MUST complete within constitutional time bounds. Viewports that exceed time bounds MUST degrade gracefully, not fail silently. | Moderate |
| V12 | Composition | Multiple viewports MAY be composed in a single observation session. Composed viewports MUST maintain independent temporal frames. | Moderate |
Section 5: Visual Taxonomy
5.1 The Constitutional Color Schema
| Element | Visual Representation | Meaning |
|---|
| Trust Anchor | Solid circle, anchor color | Root of trust; immutable authority |
| Active Key | Green indicator | Current, valid, operational |
| Rotated Key | Yellow indicator | Superseded but not compromised |
| Revoked Key | Red indicator, strikethrough | Compromised or withdrawn |
| Expired Key | Gray indicator | Past validity period |
| Valid Delegation | Solid edge, confidence-weighted | Trusted authority path |
| Revoked Delegation | Dashed edge, red | Severed authority path |
| Expired Delegation | Dotted edge, gray | Time-lapsed authority |
| Valid Signature | Green checkmark | Cryptographically verified |
| Invalid Signature | Red X | Verification failed |
| Unverified Signature | Yellow question mark | Not yet checked |
| Tampered Record | Red background, pulsing | Data integrity violation |
| Chain Break | Broken line, warning icon | Gap in constitutional chain |
5.2 Visual Severity Levels
| Level | Name | Behavior | Example |
|---|
| 0 | Info | Normal state display | Active key, valid delegation |
| 1 | Warning | Attention needed | Expiring delegation, rotation recommended |
| 2 | Alert | Action required | Expired delegation, deprecated key |
| 3 | Critical | Immediate attention | Revoked key, tampered record, broken chain |
| 4 | Emergency | Constitutional fault | Multiple revocations, trust anchor compromise |
Section 6: Temporal Observation
6.1 The Time Model
UCV supports three temporal modes:
| Mode | Description | Use Case |
|---|
| Live | Real-time observation of current state | Active monitoring, dashboards |
| Historical | Observation of state at a specific past time | Audit, forensics, compliance |
| Projected | Observation of expected future state based on policy | What-if analysis, expiry forecasting |
6.2 Temporal Invariants
| # | Invariant | Statement |
|---|
| T1 | Live mode MUST reflect current state within one observation cycle | Real-time accuracy |
| T2 | Historical mode MUST reconstruct state accurately from provenance chains | Audit integrity |
| T3 | Projected mode MUST clearly indicate projections vs. confirmed state | Honesty in observation |
| T4 | Temporal transitions MUST be visually indicated | No silent time jumps |
Section 7: Anomaly Detection
7.1 The Anomaly Framework
UCV defines anomaly detection as a constitutional requirement, not an optional feature:
| Anomaly Type | Detection Method | Severity |
|---|
| Revoked Key Used | Key in active use appears in revocation list | Critical |
| Expired Delegation | Delegation timestamp exceeds expiry | Alert |
| Broken Chain | Trust chain has missing link | Critical |
| Tampered Record | Signature verification fails on stored record | Emergency |
| Signature Mismatch | Signature does not match claimed signer | Critical |
| Stale State | Observation shows state older than freshness threshold | Warning |
| Chain Cycle | Trust chain contains circular reference | Emergency |
| Anchor Distrust | Trust anchor has been deactivated | Critical |
7.2 Anomaly Response Protocol
Anomaly Detected → Classify Severity → Render Salient Signal →
→ Log Anomaly → Notify Observer → If Emergency: Halt Affected Operations
Section 8: Adapter Specification
8.1 Adapter Contract
Each adapter MUST declare:
| Property | Description |
|---|
| Technology | Rendering technology (Canvas, WebGL, SVG, Terminal, AR/VR) |
| Capabilities | What observation targets it supports |
| Performance | Maximum observation count, render time bounds |
| Accessibility | Non-visual observation modes available |
| Export Formats | Supported export formats |
8.2 Required Adapters
| Adapter | Technology | Priority | Use Case |
|---|
UCVCanvas | HTML5 Canvas | P0 | Browser-based 2D observation |
UCVTerminal | ASCII/Unicode | P0 | Terminal-based observation (no browser) |
UCVSVG | SVG | P1 | Vector-based, zoomable observation |
UCVWebGL | WebGL | P2 | 3D trust chain visualization |
UCVExport | JSON | P1 | Machine-readable observation export |
UCVAccessibility | Screen Reader | P1 | Non-visual observation |
8.3 Adapter Auto-Detection
UCV.autoDetect() → UCVAdapter
The viewport automatically selects the best available adapter:
- Check for WebGL → use UCVWebGL if available
- Check for Canvas → use UCVCanvas if available
- Check for SVG → use UCVSVG if available
- Default → use UCVTerminal (always available)
Section 9: Constitutional Requirements
9.1 MUST Requirements (23 total)
| # | Requirement | Axiom | Invariant |
|---|
| R1 | The viewport MUST NOT modify constitutional state | VA2 | V1 |
| R2 | The viewport MUST observe all constitutional state | VA1 | V2 |
| R3 | The viewport MUST render temporal state accurately | VA7 | V3 |
| R4 | The viewport MUST render anomalies with highest salience | VA5 | V4 |
| R5 | The viewport MUST render chains as continuous paths | VA3 | V5 |
| R6 | The viewport MUST work identically across adapters | VA6 | V6 |
| R7 | The viewport MUST display signature status on all signed elements | VA5 | V7 |
| R8 | The viewport MUST reflect current state within one cycle | VA1 | V8 |
| R9 | The viewport MUST provide non-visual observation modes | VA6 | V9 |
| R10 | The viewport MUST export state accurately | VA1 | V10 |
| R11 | The viewport MUST complete rendering within time bounds | VA2 | V11 |
| R12 | The viewport MUST support composed viewports | VA6 | V12 |
| R13 | The viewport MUST detect revoked keys in active use | VA5 | Anomaly |
| R14 | The viewport MUST detect expired delegations | VA5 | Anomaly |
| R15 | The viewport MUST detect broken trust chains | VA3 | Anomaly |
| R16 | The viewport MUST detect tampered records | VA4 | Anomaly |
| R17 | The viewport MUST detect signature mismatches | VA5 | Anomaly |
| R18 | The viewport MUST detect stale state | VA7 | Anomaly |
| R19 | The viewport MUST detect chain cycles | VA3 | Anomaly |
| R20 | The viewport MUST detect anchor distrust | VA5 | Anomaly |
| R21 | The viewport MUST classify anomaly severity | VA5 | Severity |
| R22 | The viewport MUST log all detected anomalies | VA5 | Logging |
| R23 | The viewport MUST halt emergency-level operations | VA5 | Safety |
9.2 SHOULD Requirements (8 total)
| # | Requirement | Rationale |
|---|
| S1 | The viewport SHOULD support live, historical, and projected temporal modes | Complete observation |
| S2 | The viewport SHOULD provide zoom and pan for large graphs | Usability |
| S3 | The viewport SHOULD support keyboard navigation | Accessibility |
| S4 | The viewport SHOULD cache observation frames for performance | Efficiency |
| S5 | The viewport SHOULD support multiple simultaneous viewports | Composition |
| S6 | The viewport SHOULD provide observation recording | Replay/audit |
| S7 | The viewport SHOULD support collaborative observation | Multi-user |
| S8 | The viewport SHOULD provide observation bookmarks | Navigation |
10.1 Conformance Levels
| Level | Name | Requirements Met | Description |
|---|
| L0 | Basic | R1-R4, R13-R16 | Can observe state and detect basic anomalies |
| L1 | Standard | R1-R12, R13-R20 | Full observation with all anomaly detection |
| L2 | Complete | All R1-R23 | Full conformance with all requirements |
10.2 Conformance Test
UCV.validateConformance(adapter) → {
conforms: boolean,
score: number, // 0-100%
level: 'L0'|'L1'|'L2',
missing: string[], // Unmet requirement IDs
warnings: string[] // SHOULD requirements not met
}
Appendix A: Implementation Notes
A.1 Browser Implementation
For browser-based viewports:
// UCV Canvas Adapter
class UCVCanvas {
constructor(canvasElement) {
this.canvas = canvasElement;
this.ctx = canvasElement.getContext('2d');
}
async render(frame) {
// Clear canvas
this.ctx.clearRect(0, 0, this.canvas.width, this.canvas.height);
// Render trust chains
for (const chain of frame.trustChains) {
this.renderTrustChain(chain);
}
// Render anomalies (highest priority - always on top)
for (const anomaly of frame.anomalies) {
this.renderAnomaly(anomaly);
}
}
renderTrustChain(chain) {
// Draw nodes and edges
// Apply visual taxonomy colors
// Flag chain breaks
}
renderAnomaly(anomaly) {
// Render with severity-based styling
// Ensure salience (VA5)
}
}
A.2 Terminal Implementation
For terminal-based viewports:
// UCV Terminal Adapter
class UCVTerminal {
async render(frame) {
// ASCII art trust chain visualization
// Color-coded anomaly indicators
// Text-based observation output
}
renderTrustChain(chain) {
// Tree structure using box-drawing characters
// Color codes for anomaly detection
}
}
A.3 JSON Export
// UCV Export Adapter
class UCVExport {
async exportJSON(frame) {
return {
timestamp: frame.timestamp,
trustChains: frame.trustChains,
anomalies: frame.anomalies,
provenance: frame.provenance,
attestations: frame.attestations,
metadata: {
exportedAt: new Date().toISOString(),
version: UCV.VERSION,
conforms: 'L2'
}
};
}
}
Appendix B: Dependency Graph
UCV (Universal Constitutional Viewport)
├── UCS (Universal Constitutional Storage)
│ ├── Trust state
│ ├── Provenance state
│ ├── Attestation state
│ └── Delegation state
├── Reference Systems (L5)
│ ├── Data systems
│ └── Communication systems
└── Downstream dependents
├── USR/CoreFab (runtimes need observation)
├── UCA (adapters bridge to renderers)
└── P3: Life (agents must be auditable)
Appendix C: Relationship to Existing Specs
| Spec | Relationship to UCV |
|---|
| UCS | UCV observes state stored by UCS |
| USR | UCV renders CoreFab state for human observation |
| UWA | UCV may observe adapter state bridged by UWA |
| UCN | UCV may observe network state defined by UCN |
| UCA | UCV adapters may be implemented as UCA adapters |
| USDS | UCV renders signature verification state from USDS |
| UCF | UCV may observe forge state for development visibility |
D.1 Safety Properties
| # | Property | Statement |
|---|
| SP1 | Observation Safety | The viewport never modifies constitutional state |
| SP2 | Temporal Safety | Historical observation never mixes states from different times |
| SP3 | Anomaly Safety | Anomalies are never suppressed or hidden |
D.1 Liveness Properties
| # | Property | Statement |
|---|
| LP1 | Observation Liveness | The viewport eventually renders all requested state |
| LP2 | Anomaly Liveness | All anomalies are eventually detected and rendered |
| LP3 | Export Liveness | Export requests eventually complete with accurate state |
UCV v0.1.0 — Constitutional Viewport Specification
Originated by Sir Collins (access1@tutamail.com)
Classification: Constitutional — defines the observation model for all of ICore