{
  "abstract": "Abstract Continuity Core addresses a failure that appears above individual apps: projects, concepts, decisions, aliases, receipts, and implementation state are scattered across providers, repositories, files, and conversations. It defines an account-level continuity substrate with stable concept identity, event-sourced canon, alias and supersession edges, automatic checkpoints, source and authority labels, and a resurrection protocol that can reconstruct what a dormant project is, what is accepted, what is blocked, and what should happen next.",
  "author": "Hayden Lindley",
  "category": "Continuity & Canon",
  "claims": {
    "claims": [
      {
        "claim_id": "P25-C01",
        "evidence_refs": [
          "P25-S01",
          "P25-S02",
          "P25-S03"
        ],
        "limitations": [
          "No single integrated account-level runtime receipt is published."
        ],
        "public": true,
        "scope": "Continuity Core architecture.",
        "statement": "The corpus specifies stable concept identity, aliases, supersession, automatic checkpoints, source-authority separation, and project resurrection as an account-level continuity layer.",
        "status": "SPECIFIED"
      },
      {
        "claim_id": "P25-C02",
        "evidence_refs": [
          "P25-S01",
          "P25-S02"
        ],
        "limitations": [
          "Requires controlled recovery benchmark."
        ],
        "public": true,
        "scope": "Fragmented multi-provider projects.",
        "statement": "A reconstruction from canonical events can recover project orientation more accurately than provider transcript recall alone.",
        "status": "HYPOTHESIS"
      }
    ],
    "disclosure_note": "Claims marked non-public in the authored ledger are omitted from this public artifact.",
    "paper": "p25-continuity-core",
    "version": "0.1.0",
    "withheld_claim_count": 0
  },
  "date": "2026-07-27",
  "diagrams": {
    "diagrams": [
      {
        "brief": "Stable concept ID connected to aliases, repos, chats, artifacts, deployments, and supersession edges.",
        "format": "svg",
        "id": "P25-F01",
        "path": "/diagrams/p25-continuity-core/P25-F01.svg",
        "status": "source-generated conceptual architecture",
        "title": "Concept identity graph"
      },
      {
        "brief": "Events to checkpoint, dormancy, binding verification, resurrection surface, and next action.",
        "format": "svg",
        "id": "P25-F02",
        "path": "/diagrams/p25-continuity-core/P25-F02.svg",
        "status": "source-generated conceptual architecture",
        "title": "Checkpoint and resurrection loop"
      },
      {
        "brief": "Statements from user, agent, repository, test, and external source mapped to distinct authority states.",
        "format": "svg",
        "id": "P25-F03",
        "path": "/diagrams/p25-continuity-core/P25-F03.svg",
        "status": "source-generated conceptual architecture",
        "title": "Source versus authority"
      }
    ],
    "paper": "p25-continuity-core"
  },
  "evidence_state": "SPECIFIED",
  "id": "p25-continuity-core",
  "institution": "Glyphd Labs",
  "integrity": {
    "claim_ledger_sha256": "4a0e7878a9b471e38e24cf0372b4c4f39c583e63f0cb1ac38a50f90cc95eb66b",
    "paper_mdx_sha256": "1e349a9101a08ba418884f33bce18290ef5151323668af70768cd294231fded8"
  },
  "public_disclosure_boundary": "# Public-disclosure boundary\n\nThis paper publishes the system thesis, architecture, contracts, evidence state, limitations, and falsification criteria. It does not publish confidential claim charts, private patent strategy, secrets, credentials, customer material, unreleased datasets, or implementation details designated as trade secret. The public paper does not grant a license to implement the Covered Technology. See `LICENSE.md` and `NOTICE.md` in the Glyphd Labs repository.",
  "publication_class": "public-safe working paper",
  "publication_url": "https://www.glyphd.com/papers/p25-continuity-core",
  "revisions": {
    "paper": "p25-continuity-core",
    "versions": [
      {
        "date": "2026-07-27",
        "editor": "GPT-5.6 Pro",
        "summary": "Initial public-safe institute edition compiled from the CUTTING EDGE OR NEW corpus.",
        "version": "0.1.0"
      }
    ]
  },
  "schema_version": "1.0.0",
  "slug": "p25-continuity-core",
  "sources": {
    "notes": "Internal source paths are provenance references. Public publication must expose only approved public-safe excerpts or archived public artifacts.",
    "paper": "p25-continuity-core",
    "sources": [
      {
        "date": "2026-07-21",
        "id": "P25-S01",
        "path": "CONTINUITY-CORE-DESIGN-REVIEW2.md",
        "title": "Continuity Core Design Review 2"
      },
      {
        "date": "2026-07-18",
        "id": "P25-S02",
        "path": "ZEKE-V1-CANON-RECOVERY-AND-GAP-AUDIT-v0.1.md",
        "title": "ZEKE V1 Canon Recovery and Gap Audit"
      },
      {
        "date": "2026-07-12",
        "id": "P25-S03",
        "path": "GLYPH-DESK-MASTER-SPEC.v1.md",
        "title": "Glyph Desk Master Specification"
      }
    ],
    "version": "0.1.0"
  },
  "subtitle": "Concept identity, automatic checkpoints, project resurrection, and source-authority separation",
  "title": "Continuity Core",
  "version": "0.1.0"
}