← All Specifications

UCV

The constitutional model of observation — how constitutional state is made visible, understandable, and auditable to the humans it serves.

L5 — Constitutional Viewport 12 Invariants 519 Lines ❄️ Frozen

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

#AxiomStatementDerived From
VA1Constitutional 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)
VA2Observation 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)
VA3Trust 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)
VA4Provenance 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)
VA5Anomalies 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)
VA6Observation 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)
VA7Observation 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

PrimitivePresent InRole
ExistenceVA1 (state is observable)Constitutional state exists to be seen
IdentityVA3 (trust traversable)Trust chains are identity chains made visible
RelationshipVA6 (adapter-agnostic)Observation adapts to any medium while preserving meaning
ConstraintVA2 (integrity preserved)Observation must not violate constitutional constraints
TransformationVA4 (provenance reconstructible)History is transformed into visible, understandable form
VerificationVA5 (anomalies salient)Anomalies must be visually verifiable
All six primitives covered. The foundation is complete.

Section 2: The Viewport Model

2.1 Definitions

TermDefinition
ViewportA constitutional observation interface that renders state from the constitutional stack into a human-comprehensible form.
Viewport AdapterA specific rendering technology (Canvas, WebGL, SVG, Terminal, AR/VR) that implements the viewport interface for a particular display medium.
Observation TargetAny constitutional state element — keys, delegations, attestation chains, provenance records, trust anchors — that can be observed through a viewport.
Observation FrameA snapshot of constitutional state at a specific point in time, used for temporal observation.
Visual TaxonomyThe classification system for constitutional state elements in the viewport — trust, provenance, attestation, delegation, revocation.
Anomaly SignalA visual indicator that a constitutional violation has been detected — revoked key, expired delegation, tampered record, broken chain.
Observation SessionA 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

#TargetWhat It ObservesVisual Form
OT1Trust ChainTrust anchors, delegation paths, chain depth, chain validityTree/graph with anchor at root, delegations as edges
OT2Provenance ChainCreation → modification → verification historyLinear timeline with signed nodes
OT3Attestation ChainComponent attestations, operation history, verification statusEvent stream with signature badges
OT4Key LifecycleKey creation → rotation → revocation → expirationTimeline with state transitions
OT5Delegation MapAll active delegations, their confidence levels, expiryNetwork graph with confidence-weighted edges
OT6Revocation StatusRevoked keys, revocation reasons, propagationAlert overlay on affected targets
OT7Anomaly DashboardAll detected constitutional violationsProminent alert panel with severity indicators

3.2 Observation Priority

Anomalies (VA5) always render at highest priority. Within normal state:

PriorityTargetRationale
1Revocation StatusSecurity-critical; must never be hidden
2Anomaly DashboardConstitutional violations require immediate attention
3Trust ChainFoundation of all constitutional authority
4Key LifecycleKeys underpin all cryptographic operations
5Delegation MapShows authority distribution
6Provenance ChainHistorical record, important but less urgent
7Attestation ChainComponent-level verification

Section 4: Invariants

4.1 The Twelve Viewport Invariants

#InvariantStatementClassification
V1Read-Only ObservationThe viewport MUST NOT modify, create, or delete any constitutional state. Observation is strictly read-only.Critical
V2CompletenessThe viewport MUST be capable of observing all constitutional state. No state element may be excluded from observation by design.Critical
V3Temporal IntegrityWhen observing state at a specific time, the viewport MUST render that state accurately. Temporal observation MUST NOT mix states from different times.Critical
V4Anomaly SalienceConstitutional violations MUST be rendered with higher visual prominence than normal state. Anomalies MUST NOT be obscured by other visual elements.Critical
V5Chain ContinuityTrust chains, provenance chains, and attestation chains MUST be rendered as continuous, unbroken visual paths. Gaps MUST be visually flagged.Major
V6Adapter IndependenceThe viewport model MUST work identically across all adapter technologies. No observation behavior may depend on the specific rendering engine.Major
V7Signature VisibilityEvery signed element (delegation, attestation, provenance record, revocation) MUST display its cryptographic signature status — valid, invalid, or unverified.Major
V8State SynchronizationThe viewport MUST reflect current constitutional state within one observation cycle. Stale state MUST be visually indicated.Major
V9AccessibilityThe viewport MUST provide non-visual observation modes (screen reader, text-based, haptic) for accessibility compliance.Major
V10Export IntegrityExported viewport state (PNG, SVG, JSON) MUST accurately represent the observed state at the time of export.Moderate
V11Performance BoundsRendering MUST complete within constitutional time bounds. Viewports that exceed time bounds MUST degrade gracefully, not fail silently.Moderate
V12CompositionMultiple 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

ElementVisual RepresentationMeaning
Trust AnchorSolid circle, anchor colorRoot of trust; immutable authority
Active KeyGreen indicatorCurrent, valid, operational
Rotated KeyYellow indicatorSuperseded but not compromised
Revoked KeyRed indicator, strikethroughCompromised or withdrawn
Expired KeyGray indicatorPast validity period
Valid DelegationSolid edge, confidence-weightedTrusted authority path
Revoked DelegationDashed edge, redSevered authority path
Expired DelegationDotted edge, grayTime-lapsed authority
Valid SignatureGreen checkmarkCryptographically verified
Invalid SignatureRed XVerification failed
Unverified SignatureYellow question markNot yet checked
Tampered RecordRed background, pulsingData integrity violation
Chain BreakBroken line, warning iconGap in constitutional chain

5.2 Visual Severity Levels

LevelNameBehaviorExample
0InfoNormal state displayActive key, valid delegation
1WarningAttention neededExpiring delegation, rotation recommended
2AlertAction requiredExpired delegation, deprecated key
3CriticalImmediate attentionRevoked key, tampered record, broken chain
4EmergencyConstitutional faultMultiple revocations, trust anchor compromise

Section 6: Temporal Observation

6.1 The Time Model

UCV supports three temporal modes:

ModeDescriptionUse Case
LiveReal-time observation of current stateActive monitoring, dashboards
HistoricalObservation of state at a specific past timeAudit, forensics, compliance
ProjectedObservation of expected future state based on policyWhat-if analysis, expiry forecasting

6.2 Temporal Invariants

#InvariantStatement
T1Live mode MUST reflect current state within one observation cycleReal-time accuracy
T2Historical mode MUST reconstruct state accurately from provenance chainsAudit integrity
T3Projected mode MUST clearly indicate projections vs. confirmed stateHonesty in observation
T4Temporal transitions MUST be visually indicatedNo 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 TypeDetection MethodSeverity
Revoked Key UsedKey in active use appears in revocation listCritical
Expired DelegationDelegation timestamp exceeds expiryAlert
Broken ChainTrust chain has missing linkCritical
Tampered RecordSignature verification fails on stored recordEmergency
Signature MismatchSignature does not match claimed signerCritical
Stale StateObservation shows state older than freshness thresholdWarning
Chain CycleTrust chain contains circular referenceEmergency
Anchor DistrustTrust anchor has been deactivatedCritical

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:

PropertyDescription
TechnologyRendering technology (Canvas, WebGL, SVG, Terminal, AR/VR)
CapabilitiesWhat observation targets it supports
PerformanceMaximum observation count, render time bounds
AccessibilityNon-visual observation modes available
Export FormatsSupported export formats

8.2 Required Adapters

AdapterTechnologyPriorityUse Case
UCVCanvasHTML5 CanvasP0Browser-based 2D observation
UCVTerminalASCII/UnicodeP0Terminal-based observation (no browser)
UCVSVGSVGP1Vector-based, zoomable observation
UCVWebGLWebGLP23D trust chain visualization
UCVExportJSONP1Machine-readable observation export
UCVAccessibilityScreen ReaderP1Non-visual observation

8.3 Adapter Auto-Detection

UCV.autoDetect() → UCVAdapter

The viewport automatically selects the best available adapter:

  1. Check for WebGL → use UCVWebGL if available
  2. Check for Canvas → use UCVCanvas if available
  3. Check for SVG → use UCVSVG if available
  4. Default → use UCVTerminal (always available)

Section 9: Constitutional Requirements

9.1 MUST Requirements (23 total)

#RequirementAxiomInvariant
R1The viewport MUST NOT modify constitutional stateVA2V1
R2The viewport MUST observe all constitutional stateVA1V2
R3The viewport MUST render temporal state accuratelyVA7V3
R4The viewport MUST render anomalies with highest salienceVA5V4
R5The viewport MUST render chains as continuous pathsVA3V5
R6The viewport MUST work identically across adaptersVA6V6
R7The viewport MUST display signature status on all signed elementsVA5V7
R8The viewport MUST reflect current state within one cycleVA1V8
R9The viewport MUST provide non-visual observation modesVA6V9
R10The viewport MUST export state accuratelyVA1V10
R11The viewport MUST complete rendering within time boundsVA2V11
R12The viewport MUST support composed viewportsVA6V12
R13The viewport MUST detect revoked keys in active useVA5Anomaly
R14The viewport MUST detect expired delegationsVA5Anomaly
R15The viewport MUST detect broken trust chainsVA3Anomaly
R16The viewport MUST detect tampered recordsVA4Anomaly
R17The viewport MUST detect signature mismatchesVA5Anomaly
R18The viewport MUST detect stale stateVA7Anomaly
R19The viewport MUST detect chain cyclesVA3Anomaly
R20The viewport MUST detect anchor distrustVA5Anomaly
R21The viewport MUST classify anomaly severityVA5Severity
R22The viewport MUST log all detected anomaliesVA5Logging
R23The viewport MUST halt emergency-level operationsVA5Safety

9.2 SHOULD Requirements (8 total)

#RequirementRationale
S1The viewport SHOULD support live, historical, and projected temporal modesComplete observation
S2The viewport SHOULD provide zoom and pan for large graphsUsability
S3The viewport SHOULD support keyboard navigationAccessibility
S4The viewport SHOULD cache observation frames for performanceEfficiency
S5The viewport SHOULD support multiple simultaneous viewportsComposition
S6The viewport SHOULD provide observation recordingReplay/audit
S7The viewport SHOULD support collaborative observationMulti-user
S8The viewport SHOULD provide observation bookmarksNavigation

Section 10: Conformance

10.1 Conformance Levels

LevelNameRequirements MetDescription
L0BasicR1-R4, R13-R16Can observe state and detect basic anomalies
L1StandardR1-R12, R13-R20Full observation with all anomaly detection
L2CompleteAll R1-R23Full 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

SpecRelationship to UCV
UCSUCV observes state stored by UCS
USRUCV renders CoreFab state for human observation
UWAUCV may observe adapter state bridged by UWA
UCNUCV may observe network state defined by UCN
UCAUCV adapters may be implemented as UCA adapters
USDSUCV renders signature verification state from USDS
UCFUCV may observe forge state for development visibility

Appendix D: Formal Properties

D.1 Safety Properties

#PropertyStatement
SP1Observation SafetyThe viewport never modifies constitutional state
SP2Temporal SafetyHistorical observation never mixes states from different times
SP3Anomaly SafetyAnomalies are never suppressed or hidden

D.1 Liveness Properties

#PropertyStatement
LP1Observation LivenessThe viewport eventually renders all requested state
LP2Anomaly LivenessAll anomalies are eventually detected and rendered
LP3Export LivenessExport 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