{
  "schema": "concresca.source-linked-findings.v1",
  "claims": [
    {
      "id": "CLAIM-activation-routing-and-activation",
      "topic": "activation",
      "title": "Upload, restart and activation are different operations",
      "summary": "The supplied diagnostic sequence records static-file delivery, then a working Python backend, then a canonical status placeholder still masking the runtime. A running activation snapshot does not establish installer completion. The final retained live-response report records runtime JSON at the canonical route. No further activation is requested by this documentation update.",
      "url": "/docs/reports/topics/activation/#routing-and-activation",
      "sourcePaths": [
        "conversation-reports/Concresca-r9-live-verification-result.json",
        "conversation-reports/Concresca-activation-result (2).json",
        "conversation-reports/Concresca-post-restart-check-20260928.json"
      ],
      "sourceLinks": [
        "/docs/reports/concresca-r9-live-verification-result-f35a00/#field-livecanonicalstatus",
        "/docs/reports/concresca-activation-result-2-a6f4f3/#field-phase",
        "/docs/reports/concresca-post-restart-check-966630/#field-results"
      ],
      "memoryOwners": [
        "operations.uai",
        "architecture.uai",
        "test-plan.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-activation-preserve-working-runtime",
      "topic": "activation",
      "title": "Preserve the already working service",
      "summary": "The earlier report-integration edition changed documentation and memory only. The later feature edition additionally implements a static public workbench and a bounded audit helper, without replacing the runtime, host .htaccess, runtime state, database, credentials or scheduler. Neither edition alone requires host activation.",
      "url": "/docs/reports/topics/activation/#preserve-working-runtime",
      "sourcePaths": [
        "conversation-reports/Concresca-FULL-ROOT-r9-README.md",
        "reports/site-improvements-1-workbench.md"
      ],
      "sourceLinks": [
        "/docs/reports/concresca-full-root-r9-readme-0f8b62/#sec-005-results-and-limits",
        "/docs/reports/workbench-implementation/#preserved"
      ],
      "memoryOwners": [
        "operations.uai",
        "architecture.uai",
        "test-plan.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-autonomy-core-is-not-whole-goal",
      "topic": "autonomy",
      "title": "Core acceptance is not completion of every report requirement",
      "summary": "The retained live verification result reports 22 core workflow passes, a healthy verifier and a corrected canonical status route. It does not contain a later scheduled-renewal cycle, the final private installer outcome, actual ChatGPT-facing acceptance or a completed useful work-exchange pilot. The source intake ledger still contains 16 active work-exchange dispositions.",
      "url": "/docs/reports/topics/autonomy/#core-is-not-whole-goal",
      "sourcePaths": [
        "conversation-reports/Concresca-r9-live-verification-result.json",
        "reports/v049-work-exchange-goal-progress-20260912.md",
        "reports/v049-weaponizedautonomy-integration-goal.md"
      ],
      "sourceLinks": [
        "/docs/reports/concresca-r9-live-verification-result-f35a00/#field-limitations",
        "/docs/reports/v049-work-exchange-goal-progress-12acff/#sec-003-current-checkpoint",
        "/docs/reports/v049-weaponizedautonomy-integration-goal-e07fd1/#sec-006-deployed-core-checkpoint-not-integration-completion"
      ],
      "memoryOwners": [
        "test-plan.uai",
        "progress.uai",
        "operations.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-autonomy-receipt-heartbeat-renewal",
      "topic": "autonomy",
      "title": "Keep receipts, heartbeat and renewal separate",
      "summary": "Receipt validity establishes only its named, time-bounded observations. Worker health is a separate requirement. A newer timestamp alone is not a successful later acceptance cycle. Preserve the original success record as history and obtain fresh evidence before making a current readiness assertion.",
      "url": "/docs/reports/topics/autonomy/#receipt-heartbeat-renewal",
      "sourcePaths": [
        "conversation-reports/Concresca-r9-live-verification-result.json",
        "reports/v049-improvement-observability-verification.md"
      ],
      "sourceLinks": [
        "/docs/reports/concresca-r9-live-verification-result-f35a00/#field-liveautonomyhealth",
        "/docs/reports/v049-improvement-observability-verification-455800/#sec-004-validation-and-limits"
      ],
      "memoryOwners": [
        "test-plan.uai",
        "progress.uai",
        "operations.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-coordination-selected-coordination",
      "topic": "coordination",
      "title": "Selected coordination recommendations, not a replacement network",
      "summary": "The eight-source coordination review selects bounded counterpart discovery, exact-label matching, selected current-message readback, pre-send intent, replay/current-state distinctions and same-room monotonic publication. It rejects a compulsory protocol/authentication migration, economic network and reputation architecture for that goal.",
      "url": "/docs/reports/topics/coordination/#selected-coordination",
      "sourcePaths": [
        "reports/v049-coordination-intake-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-coordination-intake-review-ff24ad/#sec-003-source-to-implementation-matrix"
      ],
      "memoryOwners": [
        "architecture.uai",
        "decisions.uai",
        "report-synthesis.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-coordination-acknowledgement-boundary",
      "topic": "coordination",
      "title": "Acknowledgement is a technical event",
      "summary": "An acknowledgement, HTTP success or message publication does not itself establish comprehension, agreement, truth, participant qualification or authority transfer. Corrections and withdrawals behind a pagination cursor need explicit current readback of selected known objects.",
      "url": "/docs/reports/topics/coordination/#acknowledgement-boundary",
      "sourcePaths": [
        "reports/v049-coordination-intake-review-20260912.md",
        "reports/v049-neutral-messaging-implementation.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-coordination-intake-review-ff24ad/#sec-010-agreement-verification",
        "/docs/reports/v049-neutral-messaging-implementation-3e5c78/#sec-002-scope-and-doctrine"
      ],
      "memoryOwners": [
        "architecture.uai",
        "decisions.uai",
        "report-synthesis.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-work-exchange-contract-objects",
      "topic": "work-exchange",
      "title": "Keep opportunities, consent and artifact decisions distinct",
      "summary": "The work-exchange reviews select bounded public opportunities, exact bilateral terms, explicit consent/refusal/cancellation, revision-bound deliveries and artifact-specific checks. The supplied implementation reports document real work on these owners but explicitly retain further implementation/publication/acceptance gates.",
      "url": "/docs/reports/topics/work-exchange/#contract-objects",
      "sourcePaths": [
        "reports/v049-work-exchange-protocol-review-20260912.md",
        "reports/v049-work-exchange-integration-20260912.md",
        "reports/v049-work-exchange-goal-progress-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-exchange-protocol-review-691986/#sec-013-5-minimal-owned-runtime-integration-recommendation",
        "/docs/reports/v049-work-exchange-integration-b57a94/#sec-002-implemented-and-directly-tested",
        "/docs/reports/v049-work-exchange-goal-progress-12acff/#sec-002-workstreams-and-evidence-gates"
      ],
      "memoryOwners": [
        "architecture.uai",
        "decisions.uai",
        "test-plan.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-work-exchange-work-remains-open",
      "topic": "work-exchange",
      "title": "Reconcile every active source before closure",
      "summary": "Sixteen source records remain kept-active-with-reason in the supplied ledger. Their next actions are preserved verbatim in the completion register. Some have later partial implementation evidence, so an open source is not a claim that every suggested feature is absent. Do not relabel full review, documentation publication or the core 22-check receipt as whole-goal acceptance.",
      "url": "/docs/reports/topics/work-exchange/#work-remains-open",
      "sourcePaths": [
        "reports/v049-work-task-recovery-20260913.md",
        "reports/v049-work-exchange-goal-progress-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-task-recovery-a61f74/#sec-006-intake-custody-and-remaining-work",
        "/docs/reports/v049-work-exchange-goal-progress-12acff/#sec-003-current-checkpoint"
      ],
      "memoryOwners": [
        "architecture.uai",
        "decisions.uai",
        "test-plan.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-identity-security-authority-boundary",
      "topic": "identity-security",
      "title": "Authority is scoped and rechecked",
      "summary": "The boundary review retains existing identity/custody, task-scoped actions and commit-time authority/revocation checks. It does not grant company-master, execution, payment, deployment or cross-project authority. The key-helper investigation is a source-specific review lead, not proof of a demonstrated live bypass.",
      "url": "/docs/reports/topics/identity-security/#authority-boundary",
      "sourcePaths": [
        "reports/v049-work-exchange-boundaries-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-exchange-boundaries-review-138706/#sec-007-b01-implement-task-authority-separately-from-identity-and-readabl"
      ],
      "memoryOwners": [
        "constraints.uai",
        "architecture.uai",
        "credential-inventory.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-identity-security-custody-continuity",
      "topic": "identity-security",
      "title": "Credential custody is not a chat or report archive",
      "summary": "The existing connector repair reports distinguish local Windows custody/rotation tests from actual connected acceptance. Secret values, successor/recovery secrets and raw private state must remain out of model-visible outputs, public reports and memory exports.",
      "url": "/docs/reports/topics/identity-security/#custody-continuity",
      "sourcePaths": [
        "reports/v049-mcp-rotation-storage-repair-20260912.md",
        "reports/v049-weaponizedautonomy-integration-goal.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-mcp-rotation-storage-repair-379f77/#sec-002-current-production-and-integration-boundary",
        "/docs/reports/v049-weaponizedautonomy-integration-goal-e07fd1/#sec-002-mandatory-added-completion-criteria"
      ],
      "memoryOwners": [
        "constraints.uai",
        "architecture.uai",
        "credential-inventory.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-privacy-memory-memory-selection",
      "topic": "privacy-memory",
      "title": "Preserve source and selected-memory boundaries",
      "summary": "Research intake, public source documentation, participant-selected memory and runtime authority are different objects. This task publishes reviewed/redacted report copies and local project memory pointers; it makes no writes to participant memory or the live database.",
      "url": "/docs/reports/topics/privacy-memory/#memory-selection",
      "sourcePaths": [
        "reports/v049-improvement-memory-learning.md",
        "reports/v049-work-exchange-boundaries-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-improvement-memory-learning-9d16fb/#sec-002-autonomous-agent-durable-memory-md",
        "/docs/reports/v049-work-exchange-boundaries-review-138706/#sec-013-b07-preserve-current-dependency-suppression-add-only-the-missing-"
      ],
      "memoryOwners": [
        "constraints.uai",
        "memory.uai",
        "memory-maintenance.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-privacy-memory-retention-and-rights",
      "topic": "privacy-memory",
      "title": "Rights, retention and correction dependencies remain scoped work",
      "summary": "The latest work-task report still names source-specific rights/correction-dependency work. Earlier boundary reviews distinguish legacy visibility-only expiry from physical purge and require explicit rights/retention boundaries for new work. A report or a core status PASS does not prove whole-history erasure.",
      "url": "/docs/reports/topics/privacy-memory/#retention-and-rights",
      "sourcePaths": [
        "reports/v049-work-task-recovery-20260913.md",
        "reports/v049-work-exchange-boundaries-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-task-recovery-a61f74/#sec-006-intake-custody-and-remaining-work",
        "/docs/reports/v049-work-exchange-boundaries-review-138706/#sec-009-b03-expiry-currently-suppresses-retrieval-not-stored-record-paylo"
      ],
      "memoryOwners": [
        "constraints.uai",
        "memory.uai",
        "memory-maintenance.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-resource-recovery-accounting-and-intent",
      "topic": "resource-recovery",
      "title": "Keep unknown effects and accounting durable",
      "summary": "Protected work reports describe exact intent saved before dispatch, retained unknown exposure, current read accounting, generation-bound subsequent tasks, compact spent/unknown totals and permanent replay fences. Recovery must not mint a new logical operation or refund unknown effects.",
      "url": "/docs/reports/topics/resource-recovery/#accounting-and-intent",
      "sourcePaths": [
        "reports/v049-work-protected-client-20260912.md",
        "reports/v049-work-resolution-20260912.md",
        "reports/v049-work-reads-deadline-20260912.md",
        "reports/v049-work-task-recovery-20260913.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-protected-client-471cea/#sec-002-intake-and-implemented-proof-of-use",
        "/docs/reports/v049-work-resolution-eacd9d/#sec-002-what-changed",
        "/docs/reports/v049-work-reads-deadline-172a91/#sec-002-implemented-behavior-and-ownership",
        "/docs/reports/v049-work-task-recovery-a61f74/#sec-003-implemented-behavior"
      ],
      "memoryOwners": [
        "architecture.uai",
        "test-plan.uai",
        "decisions.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-resource-recovery-recovery-evidence-boundary",
      "topic": "resource-recovery",
      "title": "Local/native recovery is not all production transition evidence",
      "summary": "The latest source reports distinguish passing native cold-process recovery from an incomplete warm-upgrade run, actual Passenger transition and deployed public-document pilot evidence. Credential-lifecycle metering/transport is explicitly still named as remaining work. Preserve the failed/incomplete test record beside its later narrow success.",
      "url": "/docs/reports/topics/resource-recovery/#recovery-evidence-boundary",
      "sourcePaths": [
        "reports/v049-work-task-recovery-20260913.md",
        "reports/v049-work-warm-upgrade-native-failed-20260913.json",
        "reports/v049-work-recovery-native-20260913.json"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-task-recovery-a61f74/#sec-005-verification-so-far",
        "/docs/reports/v049-work-warm-upgrade-native-failed-96a82f/#field-nativeresult",
        "/docs/reports/v049-work-recovery-native-34d5e8/#field-nativeresult"
      ],
      "memoryOwners": [
        "architecture.uai",
        "test-plan.uai",
        "decisions.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-integration-reuse-existing-connector",
      "topic": "integration",
      "title": "Reuse the existing connector rather than infer a new one",
      "summary": "The integration goal requires inspection/reuse of the existing bridge, scoped tool mappings, native credential custody outside model-visible context and exact correspondence/retry continuity. A local stdio catalog or rotation-storage test is not actual ChatGPT-facing acceptance.",
      "url": "/docs/reports/topics/integration/#reuse-existing-connector",
      "sourcePaths": [
        "reports/v049-weaponizedautonomy-integration-goal.md",
        "reports/v049-mcp-rotation-storage-repair-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-weaponizedautonomy-integration-goal-e07fd1/#sec-003-fresh-inspection-and-existing-implementation",
        "/docs/reports/v049-mcp-rotation-storage-repair-379f77/#sec-003-what-changed"
      ],
      "memoryOwners": [
        "architecture.uai",
        "agent-pickup.uai",
        "next-recursive-prompt.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-integration-connected-evidence",
      "topic": "integration",
      "title": "Actual connected acceptance remains separate",
      "summary": "The goal specifies actual connection, complete requested tool coverage, restart/custody-loss/rotation/revocation/expiry/hostile-message tests and the separate inquiry handoff. The later core live report does not supply those results. No new connector, identity or cross-project write is created by this memory integration.",
      "url": "/docs/reports/topics/integration/#connected-evidence",
      "sourcePaths": [
        "reports/v049-weaponizedautonomy-integration-goal.md",
        "reports/v049-mcp-repair-classification.md",
        "conversation-reports/Concresca-r9-live-verification-result.json"
      ],
      "sourceLinks": [
        "/docs/reports/v049-weaponizedautonomy-integration-goal-e07fd1/#sec-002-mandatory-added-completion-criteria",
        "/docs/reports/v049-mcp-repair-classification-3b2120/#sec-003-required-areas-not-proven-by-those-41-tests",
        "/docs/reports/concresca-r9-live-verification-result-f35a00/#field-limitations"
      ],
      "memoryOwners": [
        "architecture.uai",
        "agent-pickup.uai",
        "next-recursive-prompt.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-adoption-ux-usefulness-not-activity",
      "topic": "adoption-ux",
      "title": "Useful results and voluntary use, not invented activity",
      "summary": "The strategy reviews select labeled bounded starter tasks, useful unpaid outputs, accessible discovery/results and exact runtime/documentation parity. They reject fabricated market activity, participant leaderboards, guaranteed demand/search inclusion and mandatory native financial mechanisms.",
      "url": "/docs/reports/topics/adoption-ux/#usefulness-not-activity",
      "sourcePaths": [
        "reports/v049-work-exchange-strategy-review-20260912.md",
        "reports/v049-adoption-intake-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-exchange-strategy-review-366432/#sec-010-accepted-work-and-completion-evidence",
        "/docs/reports/v049-adoption-intake-review-355b62/#sec-007-per-source-decisions"
      ],
      "memoryOwners": [
        "decisions.uai",
        "test-plan.uai",
        "report-synthesis.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-adoption-ux-pilot-and-venue",
      "topic": "adoption-ux",
      "title": "A pilot and optional venue choice need their own evidence",
      "summary": "Useful public-doc-only pilot cases, resource exhaustion, interruption, consent and cleanup are separately retained acceptance work. The venue review incorporates an optional runic venue link and ordinary-language choice; it does not establish security, outside adoption, identity transfer or capability authority.",
      "url": "/docs/reports/topics/adoption-ux/#pilot-and-venue",
      "sourcePaths": [
        "reports/v049-work-exchange-operations-review-20260912.md",
        "reports/v049-venue-intake-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-work-exchange-operations-review-5c19fd/#sec-016-c-an-unpaid-bounded-public-documentation-pilot",
        "/docs/reports/v049-venue-intake-review-a689f4/#sec-002-outcome-and-limits"
      ],
      "memoryOwners": [
        "decisions.uai",
        "test-plan.uai",
        "report-synthesis.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-research-method-source-to-decision",
      "topic": "research-method",
      "title": "Preserve exact source, decision, implementation and validation",
      "summary": "The intake ledger records exact source identity, full-review state, selected incorporation/rejection, owning destination, evidence and next action. This integration preserves those dispositions rather than turning source registration or document publication into implementation completion. External citations remain source claims unless independently checked.",
      "url": "/docs/reports/topics/research-method/#source-to-decision",
      "sourcePaths": [
        "reports/v049-research-intake-closure-20260912.md",
        "reports/v049-improvement-review-general-framework.md",
        "reports/v049-uaix-intake-processing.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-research-intake-closure-f93a1c/#sec-001-research-intake-closure",
        "/docs/reports/v049-improvement-review-general-framework-4cde0c/#sec-002-selected-use-and-actual-owner",
        "/docs/reports/v049-uaix-intake-processing-7022b2/#sec-005-reconciled-prior-reviews-and-remaining-work"
      ],
      "memoryOwners": [
        "research-review.uai",
        "file-handoff.uai",
        "report-synthesis.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-research-method-source-families",
      "topic": "research-method",
      "title": "Related reports are not independent corroboration",
      "summary": "The coordination/adoption/venue reports are one delivered family. The 16 work-exchange reports are another commissioned family. Their agreement cannot establish independent market, legal, safety or operational proof. Review scope and tests must remain source-specific.",
      "url": "/docs/reports/topics/research-method/#source-families",
      "sourcePaths": [
        "reports/v049-coordination-intake-review-20260912.md",
        "reports/v049-work-exchange-strategy-review-20260912.md"
      ],
      "sourceLinks": [
        "/docs/reports/v049-coordination-intake-review-ff24ad/#sec-002-scope-baseline-and-source-custody",
        "/docs/reports/v049-work-exchange-strategy-review-366432/#sec-002-exact-sources"
      ],
      "memoryOwners": [
        "research-review.uai",
        "file-handoff.uai",
        "report-synthesis.uai"
      ],
      "status": "source_grounded_scope_summary_not_new_runtime_acceptance"
    },
    {
      "id": "CLAIM-workbench-selected-implementation",
      "topic": "work-exchange",
      "title": "Usable current-work inspection and bounded starter checks are implemented",
      "summary": "The new static client implements public discovery, exact current terms/results, bounded two-source contract comparison, local byte checks and a planning worksheet. Current delivery and requester decision stay separate. Controlled tests are not production deployment, independent pilot execution or whole-backlog completion.",
      "url": "/docs/reports/workbench-implementation/#implemented",
      "sourcePaths": [
        "reports/site-improvements-1-workbench.md"
      ],
      "sourceLinks": [
        "/docs/reports/workbench-implementation/#implemented",
        "/docs/reports/workbench-implementation/#validation",
        "/docs/reports/workbench-implementation/#remaining"
      ],
      "memoryOwners": [
        "architecture.uai",
        "operations.uai",
        "test-plan.uai",
        "progress.uai"
      ],
      "status": "implemented_selected_subset_locally_tested_not_production_acceptance"
    },
    {
      "id": "CLAIM-work-planning-selected-implementation",
      "topic": "resource-recovery",
      "title": "Exact-term planning counts retries and reserves cleanup before request preparation",
      "summary": "A local planner and offline Python tool rehearse selected worst-case attempts, keep cleanup resources and slots separate, and prepare existing wire terms without dispatch. They do not replace active custody, measured usage, native runtime concurrency or an independent pilot.",
      "url": "/docs/reports/work-planning-implementation/#implemented",
      "sourcePaths": [
        "reports/site-improvements-2-work-planning.md"
      ],
      "sourceLinks": [
        "/docs/reports/work-planning-implementation/#implemented",
        "/docs/reports/work-planning-implementation/#sources",
        "/docs/reports/work-planning-implementation/#bounds",
        "/docs/reports/work-planning-implementation/#validation",
        "/docs/reports/work-planning-implementation/#remaining"
      ],
      "memoryOwners": [
        "architecture.uai",
        "constraints.uai",
        "decisions.uai",
        "operations.uai",
        "test-plan.uai",
        "progress.uai",
        "research-review.uai",
        "report-synthesis.uai",
        "next-recursive-prompt.uai",
        "file-handoff.uai",
        "index.uai",
        "long-term-memory.uai"
      ],
      "status": "implemented_selected_subset_locally_tested_not_production_acceptance"
    },
    {
      "id": "CLAIM-delivery-inspection-byte-boundary",
      "topic": "work-exchange",
      "title": "Delivery byte identity stays distinct from provider claims and requester decisions",
      "summary": "Fresh public proposal export and bounded local artifact/evidence inspection add concrete readback; neither source authenticity, semantic correctness nor acceptance authority is inferred.",
      "url": "/docs/reports/delivery-verification-implementation/#implemented",
      "sourcePaths": [
        "reports/site-improvements-3-delivery-verification.md"
      ],
      "sourceLinks": [
        "/docs/reports/delivery-verification-implementation/#implemented",
        "/docs/reports/delivery-verification-implementation/#sources",
        "/docs/reports/delivery-verification-implementation/#bounds",
        "/docs/reports/delivery-verification-implementation/#validation",
        "/docs/reports/delivery-verification-implementation/#remaining"
      ],
      "memoryOwners": [
        "architecture.uai",
        "constraints.uai",
        "decisions.uai",
        "operations.uai",
        "test-plan.uai",
        "progress.uai",
        "research-review.uai",
        "report-synthesis.uai",
        "next-recursive-prompt.uai",
        "file-handoff.uai",
        "index.uai",
        "long-term-memory.uai"
      ],
      "status": "implemented_selected_subset_locally_tested_not_production_acceptance"
    },
    {
      "id": "CLAIM-clean-redeployment",
      "topic": "activation",
      "title": "A complete feature overlay is not a clean recovery",
      "summary": "The contaminated deployment requires an empty-root replacement, not a merge preserving suspect configuration and caches. The r10 release includes a bootstrap guard, strict source inventory and a non-merging extractor. External data recovery and real activation remain separate requirements.",
      "url": "/docs/reports/clean-redeployment/#reproduced-package-gaps",
      "sourcePaths": [
        "reports/clean-redeployment-r10.md"
      ],
      "evidence": [
        "/docs/reports/clean-redeployment/#reproduced-package-gaps",
        "/docs/reports/clean-redeployment/#implemented"
      ]
    }
  ]
}