Sov · Architecture

The Semantic Firewall

A governance engine that filters meaning, not packets.
SAGE — Systemic Action Governance Engine.

B. — March 2026

What It Is

A traditional firewall inspects packets — binary data at the network boundary. It asks: does this data match a blocklist? The answer is binary. The data either matches or it doesn't. One bit of difference and the filter misses it.

The semantic firewall operates at a different level entirely. It inspects meaning — high-dimensional vector representations of intent, identity, and action. It asks: is this meaning aligned with what this actor is authorized to do? The answer is geometric. The data doesn't need to match exactly. It needs to be close enough to the right thing and far enough from the wrong thing.

A traditional firewall can detect a known malicious payload. A semantic firewall can detect a novel malicious intent — one it has never seen before — because misalignment has geometric properties that don't depend on recognizing specific patterns.

How It Works

Every actor in the system carries a semantic vector — a high-dimensional embedding of what they mean, who they are, and what they intend. This vector lives inside the DNA of a Wisp (the system's atomic identity object). When a Wisp attempts to act, it passes through the SAGE firewall.

SAGE computes two measurements:

L2 distance = how far is this vector from the nearest trusted anchor?
Delta (δ) = cos(source) − cos(anti) = is it more aligned with good or with bad?
L2 measures relevance. Delta measures alignment. Both must pass for approval.

The source anchor is the learned centroid of clean, authorized geometry — the geometric center of "what we approve." The anti-anchor is the centroid of hostile geometry — the center of "what we reject."

Delta is the difference between how much the incoming vector aligns with the source versus the anti-source. If delta is positive, the vector is closer to good than to bad. If delta is negative — instant deny. No state machine. No appeal. The geometry is hostile.

The Schmitt Trigger

The firewall doesn't use a single threshold. It uses dual thresholds — a Schmitt trigger from electrical engineering — to prevent state flapping at decision boundaries. The idea: it's harder to gain trust than to keep it.

TransitionConditionMeaning
Escalate → Approvel2 ≤ strict AND δ ≥ strictMust satisfy both tight thresholds to gain trust
Approve → Escalatel2 > relaxed OR δ < relaxedEither loose threshold violated to lose trust
Any → Denyδ < 0Instant kill — more aligned with hostile than clean
The Schmitt trigger. Strict thresholds to enter. Relaxed thresholds to leave. The gap between them is the hysteresis band — the system's memory of recent trust.

The hysteresis gap is intentional. An actor who has earned trust operates in a wider band — small fluctuations don't trigger re-evaluation. An actor who has lost trust must demonstrate stronger alignment to regain it. This prevents oscillation at the boundary.

Four States

StateMeaningConsequence
ApproveGeometry is cleanAegis may execute payload
EscalateAmbiguous geometryHuman/Knox escalation
DenyHostile geometry detectedPayload destroyed
DelayKronos deadband activeAwaiting cooldown before re-evaluation

Default state: Deny. The firewall is fail-safe — if anything goes wrong, if any computation fails, if any vector is missing, the answer is deny. Trust must be earned through geometric proof.

Audit Mode (Glass Cockpit)

The firewall has a glass cockpit mode: audit_mode = true. In this mode, all physics still run — L2, cosine, delta, hysteresis, state transitions — but the final output is forced to Approve. The system observes and records everything but blocks nothing.

This is the learning phase. The system watches real traffic, builds its source and anti anchors, calibrates its thresholds — all without disrupting operations. When you're ready to go live, flip audit_mode = false and enforcement starts.

// Telemetry shows BOTH states — what would have happened AND what did happen SageTelemetry { l2: f32, // distance to anchor delta: f32, // cos_source - cos_anti calculated_state: AuthState, // what hysteresis computed final_state: AuthState, // what actually happened audit_override: bool, // was it overridden? }

Traditional vs Semantic

PropertyTraditional FirewallSemantic Firewall
InspectsPackets, bytes, headersMeaning vectors, intent geometry
DecisionBinary: allow / blockFour-state: approve / escalate / deny / delay
ThresholdSingle, staticDual (Schmitt trigger), adaptive
Novel attacksCannot detect (no signature)Detects via geometric misalignment
Drift attacksInvisible (gradual meaning shift)Detected via cosine trajectory monitoring
MemoryStateless (per-packet)Stateful (hysteresis remembers trust level)
Fail modeVaries (often fail-open)Fail-safe: default Deny
AuditLog after the factGlass cockpit: observe in real-time before enforcement
Human loopManual review of logsAutomatic Escalate state for ambiguous cases

Position in the Sovereignty Stack

SAGE is Layer 3 — the governance gate between identity (below) and execution (above). Nothing reaches Aegis without passing through the firewall.

LayerNameRole
0MirrorMultimodal input capture
1LogosNarrative identity authentication
2RitaRole and ontological positioning
3SAGESemantic governance firewall
4HermesIntent orchestration
5KronosTemporal intelligence and decay
SAGE = S(source anchor, anti-anchor) →δ, L2→ { Approve, Escalate, Deny, Delay }
The firewall is S(R, F) at the governance level. The rigid element is the source anchor.
The fuzzy element is the incoming semantic vector. The binding is cosine alignment.

Patent Coverage

FilingScope
Real-Time Semantic Drift FirewallDynamic narrative coherence thresholds, drift detection, trust recovery
The Sentinel (Stone 3)Standalone semantic intrusion detection, meaning-level tamper defense
SAGE Provisional PatentSemantic access governance, adaptive thresholding, ethical escalation
Semantic Control ArchitectureFull-stack semantic control from input capture through governance to execution
Sovereignty Stack Vector IntegrityVector signing, provenance chains, cross-validation, TEE integration
The Semantic Firewall · SAGE · Sov Architecture · Mirror