{
  "schemaVersion": "1.0.0-public-snapshot",
  "id": "PRJ-ARCOR-001",
  "displayId": "ARCOR-001",
  "slug": "parallax-archive-core",
  "name": "Parallax Archive Core",
  "summary": "The unified architecture for preserving projects, artifacts, histories, relationships, claim boundaries, and future migration paths.",
  "purpose": "The unified architecture for preserving projects, artifacts, histories, relationships, claim boundaries, and future migration paths.",
  "regionId": "scriptorium",
  "projectType": "Archive architecture",
  "status": "Exploring",
  "maturity": "Growing",
  "evidenceClassification": "Operational",
  "visibility": "public-candidate",
  "canonConfidence": "Core",
  "launchTier": "Tier 1",
  "paths": [
    "understand",
    "wander"
  ],
  "tags": [
    "archive architecture",
    "archive",
    "core"
  ],
  "claimBoundaryVersion": "1.1.0",
  "claimBoundary": {
    "supported": "A unified Archive Core architecture and roadmap define six record domains and a six-terminal foundation, and the B2 portal registry demonstrates a first structured projection.",
    "notClaimed": "The current record does not claim complete ingestion of Michael's archive, legal records management, permanent preservation, universal format support, or permission to publish every discovered artifact."
  },
  "knownLimitations": [
    "The unified architecture is designed but not yet a complete migration-ready archive application.",
    "Source files and connected-service records may have incompatible permissions, formats, and retention rules.",
    "Hashes preserve byte identity, not meaning, accuracy, or permission to publish.",
    "A single core increases the importance of backups, export formats, access control, and disaster recovery."
  ],
  "currentState": {
    "summary": "Parallax Archive Core is recorded as Exploring at the Growing stage. The inventory currently marks 4 artifact lanes Ready, 2 Partial, and 2 Missing.",
    "maturityStage": "Growing",
    "maturityStageIndex": 2,
    "note": "B3 Tier 1 room draft · Core canon · Operational evidence · public candidate"
  },
  "capabilities": [
    {
      "symbol": "▤",
      "title": "Preserves six record domains",
      "description": "Projects, artifacts, relationships, trajectories, receipts, and contextual interpretation share stable identity and lineage."
    },
    {
      "symbol": "⌁",
      "title": "Supports many terminals",
      "description": "Historical, personal, playful, gallery, original, and field interfaces can reveal the same core without duplicating custody."
    },
    {
      "symbol": "↺",
      "title": "Keeps revision visible",
      "description": "Supersession, migration, disagreement, missing context, and future repair remain part of the archive record."
    }
  ],
  "architecture": {
    "summary": "The Core uses stable identifiers, typed records, virtual-file locators, relationship edges, version and custody metadata, import review, and multiple terminal adapters.",
    "layers": [
      {
        "name": "Record domains",
        "role": "Project, artifact, relationship, trajectory, receipt, and context records.",
        "status": "designed"
      },
      {
        "name": "Custody and lineage",
        "role": "Identity, source, versions, hashes, permissions, supersession, and retention.",
        "status": "designed"
      },
      {
        "name": "Terminal adapters",
        "role": "IBM 5100 Discovery, SL1200 Origin, PAT Mk.1 Creation, Breadbox 64 Play, Gallery 128, and Field Luggable.",
        "status": "designed"
      },
      {
        "name": "Portal projection",
        "role": "Read-only public rooms generated from approved archive records.",
        "status": "forming"
      }
    ]
  },
  "roadmap": [
    {
      "phase": "Now",
      "title": "Freeze the record schemas",
      "description": "Approve stable IDs, virtual-file locators, permissions, versioning, and supersession for the six domains."
    },
    {
      "phase": "Next",
      "title": "Ingest one complete project lineage",
      "description": "Bring source files, decisions, artifacts, relationships, and receipts for one project through the full process."
    },
    {
      "phase": "Later",
      "title": "Connect the six terminals",
      "description": "Build interfaces only after all can read the same records without duplicating custody."
    }
  ],
  "relatedProjectContext": [
    {
      "projectId": "PRJ-ETF-001",
      "relationship": "Connected through: Portal generated from archive source-of-truth"
    },
    {
      "projectId": "PRJ-LOOM-001",
      "relationship": "Connected through: Archive and runtime integration"
    },
    {
      "projectId": "PRJ-SL12-001",
      "relationship": "Archive model and origin interface"
    },
    {
      "projectId": "PRJ-IBM-001",
      "relationship": "Archive model and historical interface"
    },
    {
      "projectId": "PRJ-PATM1-001",
      "relationship": "Archive model and original terminal"
    },
    {
      "projectId": "PRJ-PSC-001",
      "relationship": "Connected through: Context library inside unified archive"
    }
  ],
  "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."
}