{
  "schemaVersion": "1.0.0-public-snapshot",
  "id": "PRJ-SOSA-001",
  "displayId": "SOSA-001",
  "slug": "parallax-sosa",
  "name": "Parallax SOSA",
  "summary": "A sovereign operating architecture for explicit authority, signed envelopes, bridge execution, freeze drift, and repairable governance.",
  "purpose": "A sovereign operating architecture for explicit authority, signed envelopes, bridge execution, freeze drift, and repairable governance.",
  "regionId": "ledger-vault",
  "projectType": "Sovereign architecture",
  "status": "Active",
  "maturity": "Growing",
  "evidenceClassification": "Operational",
  "visibility": "public-candidate",
  "canonConfidence": "Core",
  "launchTier": "Tier 1",
  "paths": [
    "build",
    "understand",
    "collaborate"
  ],
  "tags": [
    "sovereign architecture",
    "governance",
    "operating system"
  ],
  "claimBoundaryVersion": "1.1.0",
  "claimBoundary": {
    "supported": "SOSA v1.2 is frozen as a final baseline and v1.3 alpha includes Bridge Runner, Operator Authority, Signed Envelopes, and Freeze Drift work.",
    "notClaimed": "SOSA is not certified security software, a legal sovereignty mechanism, a guarantee against unauthorized action, or proof of fault tolerance beyond tested implementations."
  },
  "knownLimitations": [
    "The architecture is active but not represented as a formally verified secure operating system.",
    "Cryptographic signatures are only as trustworthy as identity proofing and key custody.",
    "Operator authority can still be abused if governance and review are weak.",
    "Distributed failure, clock drift, replay, partition, and recovery behavior require deeper implementation testing."
  ],
  "currentState": {
    "summary": "Parallax SOSA is recorded as Active at the Growing stage. The inventory currently marks 4 artifact lanes Ready, 3 Partial, and 1 Missing.",
    "maturityStage": "Growing",
    "maturityStageIndex": 2,
    "note": "B3 Tier 1 room draft · Core canon · Operational evidence · public candidate"
  },
  "capabilities": [
    {
      "symbol": "✉",
      "title": "Moves signed envelopes",
      "description": "Carries identity, mandate, payload, evidence, constraints, expiry, and signatures through the runtime."
    },
    {
      "symbol": "⚖",
      "title": "Executes bounded authority",
      "description": "Operator Authority and Bridge Runner rules determine which actions may cross a boundary."
    },
    {
      "symbol": "❄",
      "title": "Freezes drift",
      "description": "Detects stale mandates, conflicting state, missing receipts, or unauthorized expansion and moves toward a safe frozen state."
    }
  ],
  "architecture": {
    "summary": "SOSA combines sovereign nodes, Authority Capsules, signed envelopes, Bridge Runner, Operator Authority, Freeze Drift, verification, and repair receipts.",
    "layers": [
      {
        "name": "Sovereign node",
        "role": "Local identity, custody, policy, state, and exit behavior.",
        "status": "demonstrated"
      },
      {
        "name": "Signed envelope",
        "role": "Versioned message with mandate, evidence, restrictions, expiry, and signatures.",
        "status": "forming"
      },
      {
        "name": "Bridge Runner",
        "role": "Governed boundary executor that validates and records cross-node action.",
        "status": "forming"
      },
      {
        "name": "Freeze and repair",
        "role": "Stops uncertain operation, preserves state, and requires explicit recovery authority.",
        "status": "designed"
      }
    ]
  },
  "roadmap": [
    {
      "phase": "Now",
      "title": "Publish one signed-envelope walkthrough",
      "description": "Show mandate, validation, execution, rejection, freeze, and repair in a compact example."
    },
    {
      "phase": "Next",
      "title": "Implement adversarial tests",
      "description": "Exercise replay, stale authority, partial failure, conflicting commands, and recovery."
    },
    {
      "phase": "Later",
      "title": "Formalize critical invariants",
      "description": "Apply stronger verification only to the bounded safety properties the runtime can actually enforce."
    }
  ],
  "relatedProjectContext": [
    {
      "projectId": "PRJ-CB-001",
      "relationship": "Connected through: Authority and protected dissent"
    },
    {
      "projectId": "PRJ-GC-001",
      "relationship": "Connected through: Agent-office governance"
    },
    {
      "projectId": "PRJ-V369-001",
      "relationship": "Connected through: Sovereignty-engine themes"
    },
    {
      "projectId": "PRJ-SAR-001",
      "relationship": "Connected through: Autonomy constrained by explicit authority"
    },
    {
      "projectId": "PRJ-ALO-001",
      "relationship": "Connected through: Ledger and sovereign runtime"
    },
    {
      "projectId": "PRJ-LOOM-001",
      "relationship": "Connected through: Workflow weaving over governance substrate"
    }
  ],
  "contentStatus": "draft",
  "recordUpdatedAt": "2026-07-25",
  "sourceNote": "Public-safe static snapshot generated from the v0.4 B4 review registry. Source files and private working notes are not embedded."
}