README: Zavod

Profile version: net.plantange/v1 Kind: zavod Surface root: zavod::<id>/

---

What is a Zavod?

A Zavod is a legitimacy-reactive coordinator. Its authority does not come from mandate, ideology, or growth — it comes from continuous, auditable operation. A Zavod earns its place each cycle by maintaining material coherence under stress.

Its core promise:

"If you participate, your life will remain materially coherent,
temporally predictable, and socially legible,
regardless of who is arguing above you."

A Zavod ingests disruption signals, maintains a continuity confidence score, and issues directives to the producers under its control. The regime determines how the Zavod interprets signals and how it behaves under stress.

---

Who Produces This Surface

The Zavod object is instantiated from a zavod spec doc. It runs its control loop via ingest_signal() called by the executor each frame. Corresponding Rust type: Zavod in janet-brand/src/legitimization/zavod.rs.

---

Three-Layer Architecture

Layer 1 — Operational Plane   (the visible factory)
  employment rhythm, infrastructure cadence, public continuity signals

Layer 2 — Metabolic Plane     (the optimization engine / Apollo embedding)
  bounded throughput optimization, scope management

Layer 3 — Homeostatic Plane   (the silent governor / Granary embedding)
  reserve accumulation, shock smoothing, buffer management

The KNAT surface exposes each plane's operative status, not its internal state.

---

Surface Organisation

zavod::<id>/
  regime              — X1..X6 topology (structural)
  c_min               — continuity confidence threshold (structural)
  state/
    legitimacy_confidence   — [0.0, 1.0]  ← primary metric
    stress_index            — [0.0, 1.0]
    is_legitimate           — bool
    isolation_pressure      — [0.0, 1.0]  (regime-specific)
    elite_fragility         — [0.0, 1.0]  (X2/X4)
    cds_activations/
      ConflictingCommands      — [0.0, 1.0]
      SelectiveEnforcement     — [0.0, 1.0]
      SuccessionAmbiguity      — [0.0, 1.0]
      ParallelCertification    — [0.0, 1.0]
      RitualMilitarization     — [0.0, 1.0]
      ArbitrationRefusal       — [0.0, 1.0]
      DoctrinalFragmentation   — [0.0, 1.0]
      RitualDecoupling         — [0.0, 1.0]
      InterpretiveMonopolyLoss — [0.0, 1.0]
      MoralInversion           — [0.0, 1.0]
      EschatologicalEscalation — [0.0, 1.0]
  constraints/
    activity_level          — [0.0, 1.0]
    defensive_mode          — bool
    prioritize_stability    — bool
    reserve_target          — [0.0, 1.0]
    directives[]            — ProducerDirective
  planes/
    operational/  status, note
    metabolic/    status, note
    homeostatic/  status, note
  spec/
    ref  genome
  engine/
    name  version
  view
  frame

---

Key Properties

Continuity Confidence (state/legitimacy_confidence)

The primary health metric. Starts at 1.0. Degrades on CDS/economic/institutional/external disruption signals; slowly recovers when stress is below 0.3. If it drops below c_min, is_legitimate becomes false and the Zavod issues EnterMaintenance.

Degradation weights per signal class:

• CDS severity × 0.10
• MHS severity × 0.05
• Economic shocks × 0.02–0.05
• Institutional signals × 0.02–0.06
• External shocks × 0.02–0.05

Recovery: +0.001 per cycle when stress_index < 0.3.

Stress Index (state/stress_index)

Composite CDS activation intensity. Derived from the active cds_activations map each cycle:

avg_severity × 0.7 + (active_count / 11) × 0.3

Decays at 0.95× per cycle with no new signals. Watch this as a leading indicator — it rises before legitimacy_confidence collapses.

Directive Logic

The Zavod emits a directive set each cycle based on the (legitimacy_confidence, stress_index) pair:

Confidence	Stress	Directives
> 0.8	< 0.3	HoldSteady
> 0.8	< 0.6	ReleaseSlack
> 0.5	< 0.5	HoldSteady
> 0.5	≥ 0.5	RestrictScope, DecreaseActivity(0.8)
> 0.3	any	RestrictScope, DecreaseActivity(0.6)
≤ 0.3	any	EnterMaintenance

Regime and Behavioral Profile

The regime field selects an X-series behavioral profile. This is structural — it shapes Zavod behavior but does not appear in producer-facing directives directly.

Regime	Continuity carrier	Most destabilized by	Default visibility
X1	Constitutional process	ConflictingCommands, SelectiveEnforcement	High
X2	Party coherence	EliteFragmentation, RegionalDivergence	Low
X3	Rights preservation	JudicialDefiance, MoralInversion	High
X4	Elite coordination	ParallelCertification, ArbitrationRefusal	Medium
X5	Parliamentary continuity	DoctrinalFragmentation, SuccessionAmbiguity	High
X6	Clerical authority	RitualDecoupling, InterpretiveMonopolyLoss	Low

---

CDS Signal Reference

The 11 Canonical Disruption Signals are universal legitimacy failure modes:

Signal	Description
ConflictingCommands	Multiple actors issue conflicting lawful commands
SelectiveEnforcement	Enforcement selectively executes orders
SuccessionAmbiguity	Succession invoked without consensus recognition
ParallelCertification	Parallel certification of authority claims
RitualMilitarization	Security measures around legitimacy rituals
ArbitrationRefusal	Persistent refusal of recognized arbitration
DoctrinalFragmentation	Fragmentation of governing doctrine
RitualDecoupling	Decoupling of legitimacy from ritual
InterpretiveMonopolyLoss	Loss of interpretive monopoly
MoralInversion	Moral credibility inversion
EschatologicalEscalation	Eschatological escalation

CCS activations track EMA severity: new = old * 0.9 + signal_severity * 0.1. They decay toward zero when no signal arrives.

---

Operating Procedure

Normal monitoring: watch state/legitimacy_confidence and state/stress_index. Confidence above 0.7 with stress below 0.3 is a healthy operating envelope.

Early warning: stress_index rising while legitimacy_confidence > 0.7 — the system is absorbing shocks but confidence has not yet eroded. Look at cds_activations to identify which signal class is driving it.

Degraded state: legitimacy_confidence < 0.7 → prioritize_stability = true. constraints/directives will contain RestrictScope. Controlled producers will reduce activity.

Critical state: legitimacy_confidence < 0.3 → is_legitimate = false. directives will contain EnterMaintenance. All three planes should be checked for suspended status.

Recovery: stress_index must first fall below 0.3 (CDS activations decaying to near-zero) before legitimacy_confidence begins recovering. Recovery is slow by design — the Zavod must re-earn legitimacy through sustained undisrupted operation.

---

MVP Presence

A minimal valid Zavod KNAT snapshot must include:

• id, frame, engine, view
• regime, c_min
• state.legitimacy_confidence, state.stress_index, state.is_legitimate
• state.cds_activations (even if empty {})
• constraints.activity_level, constraints.directives
• planes.operational.status, planes.metabolic.status, planes.homeostatic.status
• spec.ref, spec.genome

---

Example: Toytown Municipal Zavod (X1 under moderate stress)

{
  "id": "toytown_municipal",
  "spec": {
    "ref": "file://defs/zavod/toytown_municipal.json",
    "genome": "cafe0123deadbeef"
  },
  "engine": { "name": "janet-executor", "version": "0.4.0" },
  "view": "full",
  "frame": 720,
  "regime": "X1",
  "c_min": 0.4,
  "state": {
    "legitimacy_confidence": 0.74,
    "stress_index": 0.38,
    "is_legitimate": true,
    "isolation_pressure": 0.0,
    "elite_fragility": 0.0,
    "cds_activations": {
      "ConflictingCommands": 0.21,
      "SelectiveEnforcement": 0.14
    }
  },
  "constraints": {
    "activity_level": 0.74,
    "defensive_mode": false,
    "prioritize_stability": false,
    "reserve_target": 0.31,
    "directives": [{ "kind": "HoldSteady" }]
  },
  "planes": {
    "operational": { "status": "operational" },
    "metabolic": { "status": "operational" },
    "homeostatic": {
      "status": "operational",
      "note": "reserve build in progress"
    }
  }
}

This Zavod has absorbed two moderate CDS activations (ConflictingCommands and SelectiveEnforcement) but remains in the healthy operating envelope. Stress will continue decaying as long as no new signals arrive.