Reconcile authoritative Opsle research ledger

ARCHITECTURE.md

@@ -1,8 +1,9 @@
 # Cross-project architecture
 
 Opsle Tasks (`opsle/tasks`) owns current workload, task lifecycle and remote
-execution. Its control plane and Incus execution targets are independently
-deployed. This research repository records evidence and program state; it has no
+execution. Its current default combines the control plane and local execution
+inside one Incus instance, with optional SSH targets and an external exact-SHA
+release broker. This research repository records evidence and program state; it has no
 runtime task-management authority.
 
 Tasks calls the versioned capability contract implemented for Task 15. Trusted
@@ -24,11 +25,21 @@ its contract. Agent Trajectory Profiler and Semantic Edit Protocol retain their
 independent evidence and research boundaries. Graphify is an optional standalone
 CLI, not a Tasks capability.
 
-The final consolidation places ten source concepts under Tasks contracts and
-Routing Policy under Gearbox. Source repositories are historical and cannot be
-active dependencies. Durable Supervisor, Taslos Tasks, Paperclip and historical
-agent-run are retired. Findings, source attribution, licenses and experiment
-artifacts remain evidence; none supplies a current execution prerequisite.
+The final consolidation assigns ten source concepts to Tasks and Routing Policy
+to Gearbox. Tasks subsequently removed its copied contract archive; exact Git
+history preserves the contracts, source attribution and licenses. Current Tasks
+behavior does not establish full fidelity to those historical contracts. Source
+repositories are historical and cannot be active dependencies. Durable
+Supervisor, Taslos Tasks and historical agent-run are retired. Paperclip remains
+intentionally retained contingency infrastructure outside the research program
+and backlog. Historical artifacts supply no current execution prerequisite.
+
+Notebook implementation and production integration are complete through
+[Tasks PR #83](https://github.com/opsle/tasks/pull/83), with the exact recovery,
+deployment and test provenance in `program/registry.json`. Failed #51/#60 execution
+history remains failed; integration does not establish research completion.
+Current architecture evidence is pinned in the
+[reconciliation record](program/evidence/post-consolidation/README.md).
 
 The [generated theory map](program/THEORY_MAP.md) maps each concept and records
 its current home. The [historical architecture](program/history/pre-consolidation/ARCHITECTURE.md)

CONCEPTS.md

@@ -10,12 +10,16 @@ consolidated concepts, and one retired concept. Eighteen live concepts share eig
 current homes. Tasks is program infrastructure and the workload authority;
 Visible Value is a standalone concept and receipt-validation CLI.
 
-Ten source concepts now live in Tasks contracts: discovery, execution
+Ten source concepts have Tasks as their current home: discovery, execution
 authorization, recovery, resource claims, scheduler, state ledger, controlled
 acceptance, ephemeral workers, event wakeup and verifiable handoff. Routing Policy
 is consolidated into Gearbox. Durable Supervisor is retired, with findings
 preserved in Tasks and no current conceptual home or activation gate.
 
+Tasks later removed the copied contract archive from its current branch. The
+contracts and licenses remain available at the exact historical revisions in
+the ledger; consolidation does not prove current implementation fidelity.
+
 Graphify's final role is an optional standalone CLI, not an Opsle Tasks capability.
 Task 15's versioned capability contract integrates Gearbox, Context Firewall,
 Affected Verification and Visible Value through independent public interfaces.

README.md

@@ -54,8 +54,10 @@ dashboard and priority view with `python3 tools/render_program_status.py`.
 ## Product relationship
 
 Opsle Tasks is the authoritative current workload and task-management system and integrated reference implementation in
-`opsle/tasks`. Its control plane and project execution targets are independently
-deployed and do not depend on this research repository at runtime.
+`opsle/tasks`. Its current default combines the control plane and local execution
+in one Incus instance, with optional SSH targets and a separate release broker.
+It does not depend on this research repository at runtime. Exact architecture and
+Notebook recovery evidence are recorded in `program/registry.json`.
 
 ## Integrity
 

program/OPERATING_RULES.md

@@ -56,6 +56,13 @@ nondeterministic fields must not contaminate deterministic semantic output.
 
 ## Retirement and current ownership
 
-Durable Supervisor, Taslos Tasks, Paperclip and historical agent-run are retired. Their archived controls, migration rollback notes and experiments authorize no current work. Completed consolidation receipts supersede dated partial observations. Graphify is an optional standalone CLI, not a Tasks capability. Do not recreate retired repositories or execution systems from stale references.
+Durable Supervisor, Taslos Tasks and historical agent-run are retired. Their archived controls, migration rollback notes and experiments authorize no current work. Paperclip is intentionally retained contingency infrastructure, outside the research portfolio and backlog; removal from active Tasks orchestration did not establish contingency decommissioning. Completed consolidation receipts supersede dated partial observations. Graphify is an optional standalone CLI, not a Tasks capability. Do not recreate retired repositories or execution systems from stale references.
 
 Repository activity, Tasks project visibility and research maturity are independent. `.github` is retained for housekeeping but excluded from workload eligibility. Consolidated concepts share active homes; historical source records retain evidence without becoming active dependencies. Release and data-safety requirements remain separate from task authorization.
+
+Recovery can complete an implementation and its production integration while the
+original execution remains failed. Notebook recovery through Tasks PR #83 does
+not rewrite #51/#60, activate the overlapping pending #52, or complete a research
+lifecycle. Use the revision-linked recovery and dated history in `registry.json`
+when judging whether work is already implemented. Do not create retry or
+replacement work from a failed status alone.

program/PRIORITY.md

@@ -33,19 +33,19 @@ Park by default:
 
 | Lane | Objective | Repositories | Entry gate |
 |---|---|---|---|
-| **NOW** | Maintain the current Tasks workload and evidence-backed program state. | `tasks`, `research` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
-| **NEXT** | Address demonstrated integration or measurement deficiencies from Tasks workloads. | `gearbox`, `context-firewall`, `visible-value`, `affected-verification`, `decision-evidence-protocol`, `agent-trajectory-profiler` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
+| **NOW** | Maintain current Tasks workload and reconcile demonstrated defects with shipped recovery evidence; Notebook implementation and production integration are complete. | `tasks`, `research` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
+| **NEXT** | Address demonstrated integration or measurement deficiencies; shipped capability packages alone do not establish current-runtime compatibility or research completion. | `gearbox`, `context-firewall`, `visible-value`, `affected-verification`, `decision-evidence-protocol`, `agent-trajectory-profiler` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
 | **THEN** | Investigate semantic edits only when workload evidence establishes a need. | `semantic-edit-protocol` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
 | **LATER** | Prepare controlled research and public material when evidence and separate release authority support it. | `site` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
 | **PARKED** | Retain organization housekeeping separately from workload eligibility. | `.github` | An authorized Tasks work item and a qualifying evidence-backed reason are required. |
 
-### NOW — Maintain the current Tasks workload and evidence-backed program state.
+### NOW — Maintain current Tasks workload and reconcile demonstrated defects with shipped recovery evidence; Notebook implementation and production integration are complete.
 
 Entry: An authorized Tasks work item and a qualifying evidence-backed reason are required.
 
 Exit: The scoped defect or question is resolved with bounded evidence; release requirements remain separate.
 
-### NEXT — Address demonstrated integration or measurement deficiencies from Tasks workloads.
+### NEXT — Address demonstrated integration or measurement deficiencies; shipped capability packages alone do not establish current-runtime compatibility or research completion.
 
 Entry: An authorized Tasks work item and a qualifying evidence-backed reason are required.
 
@@ -120,4 +120,4 @@ Task/run summary: total children; model/effort distribution; total model tokens
 
 ## Exact next execution
 
-Select the next authorized task from Opsle Tasks; use its project scope and workload evidence to identify the smallest justified change. This ledger does not create a parallel queue.
+Select only authorized, evidence-backed work from Opsle Tasks. Notebook implementation and production integration are complete through PR #83; the pending #52 scope is superseded by that recovery and is not a retry candidate. Existing lane membership is unchanged; see reconciliation evidence in program/registry.json.

program/THEORY_MAP.md

@@ -15,7 +15,7 @@ Historical definitions, extraction analysis, initial SHAs, licenses, negative ev
 Coverage: 19 concepts; active 7; consolidated 11; retired 1; 8 distinct current homes.
 
 Theory registry canonical SHA-256:
-`f079b141834b738d9df6dbd2f39c2ae063e4c4186e39477130beb3dc9db7cf7b`.
+`d67661c34b1c252aa9288626a88a4c3424d1b842e9ee908ce88145caf77c2c0a`.
 
 | Concept identity | Classification | Executed / retained disposition | Confidence | Current home and maturity |
 |---|---|---|---|---|

program/evidence/post-consolidation/README.md

@@ -1,43 +1,103 @@
 # Post-consolidation evidence inventory
 
-`inventory.json` records default-branch revisions inspected through Git on
-2026-09-09. The timestamp denotes the UTC observation date, not a runtime health
-probe. `consolidation.json` is the exact parsed final committed Tasks migration
-receipt at the revision linked by the inventory. It includes dated partial
-observations for provenance; `overall: complete`, `completedAt`, and the final
-Durable Supervisor host-move receipt supersede them. Archive paths are provenance
-locators, not instructions to restore or reactivate sources.
-
-The inventory includes 11 current repositories and 12 historical sources. Eleven
-sources consolidated into Tasks (ten) or Gearbox (one); Durable Supervisor retired
-separately. `.github` is retained but its execution project is retired. Repository
-presence does not assert that a project is visible, enabled, or currently running.
-The manifest's temporary proof projects are not new research repositories.
-
-Current source inspection covered Tasks `docs/TASK_15.md`, `docs/CAPABILITIES.md`,
-remote execution proof and no-local-fallback receipt, and the current README and
-limitations of Context Firewall, Gearbox, Visible Value and Affected Verification.
-The exact revision URLs and retirement commits are in `registry.completed_work`.
-Later Taslos Tasks and Paperclip retirement commits supersede the remote proof's
-historical statements that predecessor services still existed.
-
-Tasks' historical commit `00d2bac` accepted an external Graphify capability.
-The approved Task 21 scope explicitly supplies the final superseding policy:
-Graphify is an optional standalone CLI, not a Tasks capability. The current
-bundled capability tree contains Gearbox, Context Firewall, Affected Verification
-and Visible Value only. This ledger does not claim to inspect or change an external
-operator installation, and absence from the bundled tree alone is not evidence
-about such installations.
-
-Research maturity is conservative: Context Firewall, Gearbox and Visible Value
-remain PROTOTYPED; Affected Verification remains VERIFIED with OBSERVE/SHADOW
-research limits. Tasks integration and remote proofs are operational evidence,
-not controlled comparative savings or research completion. EXP-001 remains
-unconsumed; AV-EXP-002 permanently remains FAIL.
-
-Historical ledger and conceptual analysis are preserved under
-`program/history/pre-consolidation/` at research revision
-`840c79c04199762acdd59e89e807ca9086f3e45e`. Initial Gearbox publication and all pinned
-experiment identities remain unchanged. No deployment, provider experiment,
-external task, or PR #18 operation was performed for this reconciliation.
-Final verification is delegated to the existing research pipeline.
+`program/registry.json` remains the sole machine-readable portfolio and priority
+authority. This existing inventory is subordinate evidence, not a queue or a
+second portfolio. The September 11 reconciliation is recorded under
+`registry.reconciliation`; Notebook completion is under the Tasks repository's
+`integration_completion.notebook`. No new derived view is introduced.
+
+The previous observation is preserved at
+[Research cd1ecf2](https://github.com/opsle/research/blob/cd1ecf2cf28bf057f2ed683ea647d75fd6239e5f/program/evidence/post-consolidation/inventory.json).
+`inventory.json` now records the September 11 GitHub default-branch observations.
+Its `source` and `source_revision` still identify the immutable September 7
+consolidation receipt. `consolidation.json` is unchanged: the final
+`overall: complete`, `completedAt` and host-move receipt supersede its dated
+partial observations. Archive paths are provenance, not restoration instructions.
+
+All 23 GitHub repositories were checked through repository metadata,
+default-branch SHA and exact-revision README reads. All use `main`; 11 current
+repositories remain unarchived and all 12 historical sources remain archived.
+Context Firewall, Gearbox, Affected Verification, Research and Tasks advanced
+since the previous recorded HEADs. Unchanged repositories were rechecked too.
+The historical sources' local checkouts can predate their retirement notices;
+GitHub supplies their current default-branch identities.
+
+Eleven source concepts consolidated into Tasks (ten) or Gearbox (one); Durable
+Supervisor retired separately. Tasks subsequently removed its copied contract
+archive in the simplification at
+[3baecd46b4e8](https://github.com/opsle/tasks/commit/3baecd46b4e83e4a35bad1f670ae8c5459225d3d).
+[Current architecture](https://github.com/opsle/tasks/blob/fc89649edcf80c7cb9399c025d481e79c8ce4eaa/docs/ARCHITECTURE.md)
+distinguishes historical migration material from runtime behavior. Exact Git
+history retains contracts, licenses and attribution. No concept gains maturity
+or an activation requirement from this migration or removal.
+
+Production evidence came from read-only Tasks `GET /api/state`, task details,
+durable attempts and `GET /api/health`. Only Research was enabled among current
+program projects at the observation; the other workload-eligible program
+projects were disabled. `.github` remains a current GitHub repository with a
+retired execution project, as do the historical source projects. Runtime
+admission flags do not change portfolio membership or priority lanes. Temporary
+proof projects and unrelated applications are not research repositories.
+
+Notebook implementation and production integration are complete through
+[recovery 482e392086a9e71214699b86491d14b55c8f9aba](https://github.com/opsle/tasks/commit/482e392086a9e71214699b86491d14b55c8f9aba),
+[merged PR #83](https://github.com/opsle/tasks/pull/83) and deployed SHA
+`fc89649edcf80c7cb9399c025d481e79c8ce4eaa`. The live health response and current
+release symlink agree on that SHA. PR #83 explicitly reports 498 passing tests
+in a fresh detached exact-SHA suite, zero failures and two existing skips;
+46 continuation/lifecycle tests also passed. The pinned
+[docs/releases/TASK_60_NOTEBOOK_RECOVERY_2026-09-11.md](https://github.com/opsle/tasks/blob/fc89649edcf80c7cb9399c025d481e79c8ce4eaa/docs/releases/TASK_60_NOTEBOOK_RECOVERY_2026-09-11.md)
+corroborates integrated counts, retained-file classification and PR #82
+continuation preservation. These are upstream test results, not a new Tasks test
+run performed by this ledger reconciliation. Raw private test logs and broker
+backup/activation receipts were inaccessible to the execution identity; no
+access boundary was changed.
+
+Tasks #51 and #60 remain `FAILED/TEST`: durable attempt records 532/key 2716 and
+570/key 3092, with failure events 2760 and 3137. #50 is DONE; umbrella #48 remains
+FAILED. Existing #52 is PENDING and blocked by #51, but its mode-controlled inline
+completion scope is superseded by recovery. This mismatch does not create a
+Notebook retry or replacement. Production state was not modified.
+
+Context Firewall #36 and Affected Verification #23 completed bounded external
+package implementations. Their compatibility evidence pins earlier Tasks
+revisions; installation and compatibility with current production remain
+unproven. Context Firewall's package README explicitly retains a separate
+Tasks-owned bundled-removal boundary. Gearbox PR #4 adds provider/model/effort
+routing. Visible Value #24/#40 are completed integration repairs. The ledger
+preserves failed, cancelled and superseded work independently of those outcomes.
+
+Graphify remains an optional standalone CLI, not a Tasks capability. The four
+research measurement interfaces are Gearbox, Context Firewall, Affected
+Verification and Visible Value; current Tasks additionally bundles its
+product-specific Question Recommendation adapter. Paperclip is intentionally
+retained contingency infrastructure by Task #62's approved scope, outside the
+portfolio and backlog. Its historical retirement milestone denotes removal from
+active orchestration, not decommissioning of the contingency installation. No
+contingency health or restoration-readiness check was performed.
+
+No lifecycle or priority-lane promotion is supported. EXP-001 remains PLANNED:
+current Research artifacts and inspected durable task history establish no
+authorized subject run/result. AV-EXP-002 remains the historical miss;
+AV-EXP-003 remains bounded OBSERVE/SHADOW repair evidence. Integration and everyday
+telemetry do not establish controlled benefit or independent replication. Site
+remains evidence-gated and `.github` still lists historical concept repositories.
+
+The case-insensitive tracked-file search found no accidental Visual Verify
+references; the canonical name remains Visible Value. Historical snapshots and
+frozen experiment artifacts are unchanged. Only the existing status, priority
+and theory views are regenerated; final verification remains with the pipeline.
+
+Verification passed registry validation, generated-view comparison, pinned
+offline-freeze qualification and all five existing receipt checks. The Research
+unittest suite ran 117 tests: 116 passed, one failed because
+`tests/test_validate_program.py:48` still hard-codes the previous Affected
+Verification HEAD. Updating that assertion is outside this records-only task;
+current evidence was not reverted and the test was not bypassed. This is an
+explicit unresolved pipeline blocker, recorded in `registry.reconciliation.verification`.
+
+Opsle Value accounting is in the same verification record. Offline qualification
+reproduced 36 Context Firewall invocations (EXACT), 36 Decision Evidence
+validations (OBSERVED) and 48 Trajectory Profiler profiles (EXACT). The existing
+machine receipts remain unchanged. No subject run, experiment result or causal
+savings claim was added.