Expose goal milestones and remaining acceptance as tracked tasks
Some checks failed
Use-case regression gate / usecase-regressions (push) Failing after 6m49s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a18e2d-f513-7742-b8e7-12af0b744ff3
This commit is contained in:
tegwick 2026-10-31 11:19:19 +01:00
parent 7298b7f616
commit e56654933c
7 changed files with 618 additions and 15 deletions

View file

@ -86,20 +86,36 @@
| task | CSOC-WP-0011-T01 | todo | — | workplans/CSOC-WP-0011-ui-framework-architecture.md |
| task | CSOC-WP-0011-T02 | todo | — | workplans/CSOC-WP-0011-ui-framework-architecture.md |
| task | CSOC-WP-0011-T03 | todo | — | workplans/CSOC-WP-0011-ui-framework-architecture.md |
| task | CSOC-WP-0012-T01 | progress | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T01 | done | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T02 | done | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T03 | progress | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T04 | progress | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T05 | done | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T06 | done | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T07 | progress | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T08 | progress | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T09 | todo | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T10 | todo | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T11 | todo | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0012-T12 | todo | — | workplans/CSOC-WP-0012-durable-recovery-service-readiness.md |
| task | CSOC-WP-0013-T01 | done | — | workplans/CSOC-WP-0013-sharing-content-hardening.md |
| task | CSOC-WP-0013-T02 | progress | — | workplans/CSOC-WP-0013-sharing-content-hardening.md |
| task | CSOC-WP-0013-T03 | todo | — | workplans/CSOC-WP-0013-sharing-content-hardening.md |
| task | CSOC-WP-0013-T04 | done | — | workplans/CSOC-WP-0013-sharing-content-hardening.md |
| task | CSOC-WP-0013-T05 | todo | — | workplans/CSOC-WP-0013-sharing-content-hardening.md |
| task | CSOC-WP-0014-T01 | progress | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T02 | todo | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T03 | wait | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T04 | progress | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T04 | done | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T05 | done | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T06 | progress | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0014-T07 | todo | — | workplans/CSOC-WP-0014-cohort-transfer-bubble-offramp.md |
| task | CSOC-WP-0015-T01 | done | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0015-T02 | todo | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0015-T03 | done | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0015-T04 | progress | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0015-T04 | done | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0015-T05 | todo | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0015-T06 | todo | — | workplans/CSOC-WP-0015-communication-runtime-acceptance.md |
| task | CSOC-WP-0016-T01 | done | — | workplans/CSOC-WP-0016-mfa-setup-link.md |
| task | CSOC-WP-0017-T01 | done | — | workplans/CSOC-WP-0017-wave2-resource-right-sizing.md |
| intake | CSOC-IN-0001 | closed | blue | docs/intakes/csoc-residuals.md |

View file

@ -0,0 +1,106 @@
# Progress assessment for CSOC-WP-0012–0015
Assessment date: 2026-10-31. This is an effort estimate against the full four-workplan
objective, not a task-count percentage or a new acceptance decision.
**Working estimate: roughly 60% complete, with about 40% still ahead. A reasonable
remaining-work range is 35–50%.** Productive review may expose further work; elapsed
hours, test counts and the number of prepared release packets do not predict that
rework. This is not a calendar completion promise.
## Basis and uncertainty
| Workplan | Planning weight | Estimated work remaining | What drives the remainder |
| --- | ---: | ---: | --- |
| WP-0012 recovery/service | 35% | 35–45% | Recurring route and inactive installation, native failure/retry/watchdog proof, schedule observation, retention/capacity, complete service registration/cost/offboarding evidence |
| WP-0013 sharing/content | 20% | 25–40% | Actual corpus/assets fidelity and revision lifecycle acceptance, four productive sharing/portability journeys and any resulting fixes |
| WP-0014 migration/off-ramp | 30% | 50–65% | Source exceptions and identity/grant/assets mapping, remaining productive cohort transfers and date verification, retained use-case verdicts, separate cutover/retirement decision |
| WP-0015 communication | 15% | 25–40% | General sender/reply/inbox/DNS/bounce ownership, native reset-authority return, productive registration/invitation acceptance |
Weights are an explicit engineering judgment about relative scope, not measured
historical effort. Weighted bounds are approximately 36–50%; the public estimate
is deliberately rounded. Do not count final acceptance gates and their detailed
execution tasks twice. Substantial implementation is complete, but pending native
operations and productive acceptance are real work. The range assumes existing
implementations largely survive review and that the remaining source exceptions
can be resolved without a new platform feature set. More reconstruction or major
rejected workflows would raise it. Waiting for an owner or observation window can
extend calendar time without proportionate engineering effort.
## Verified progress that the old task counts concealed
- Independent encrypted paired recovery, provider-only protected-kit recovery and
immutable readback have been exercised. Latest corrected-date recovery compares
13 tables, 114 rows and 86 files, with owner/outsider view checks. See
`provider-kit-recovery-post-date-2026-10-31.json` and the identity release return.
- Storage enforcement was deployed and verified at revision 18. The later identity/
export image release is verified at revision 19 with unchanged business data,
content and migration history. See `storage-release-review-2026-10-31.md` and
`identity-export-release-return-2026-10-31.md`.
- The accepted-cohort date correction is complete, with all 36 imported source
dates verified and three local pages preserved. See
`accepted-cohort-date-manifest-proof-2026-10-31.json`.
- State Hub backup notification readback and the SMTP proof are verified; the user
confirmed actual Gmail inbox receipt. Recurring delivery source and isolated
native checks are complete. This does not establish automatic monitoring.
- All 71 known spaces are retained in inventory, with 67 draft trees and explicit
unresolved exceptions. Native identity/browser and owner-source communication
rehearsals pass. Neither preparation nor automated success supplies a productive
transfer verdict.
The latest source gate is `make check`: 475 passed, zero failures/errors/skips,
including required browser journeys. Fifteen cases cover the source installer
library. No source code changed during this tracking audit; its source hashes and
result envelope are in `backup-source-installer-validation-2026-10-31.json`.
## Tracking correction and scope conservation
Before this audit, 4 of 14 very broad tasks were marked done. Hundreds of lines of
implementation and deployment receipts accumulated inside the others. State Hub
received description updates, but its unchanged completion counts hid meaningful
progress. That was a planning/tracking weakness, not evidence that no work happened.
The audit retains every original task ID and evidence trail, adds 16 concrete
execution/milestone tasks, and splits three broad tasks at verified boundaries:
| Original task | Now complete | Remaining original scope remains live in |
| --- | --- | --- |
| WP-0012-T01 | Independent custody and protected retrieval | WP-0012-T04 retention, capacity and historical-copy disposition; ongoing service remains T03/T07–T12 |
| WP-0014-T04 | Accepted live cohort date correction and postflight | WP-0014-T06 remaining trees/dates/productive verification; T07 transfer |
| WP-0015-T04 | Browser implementation/native rehearsal and verified app release | WP-0015-T05 productive flow verdicts; T06 native reset-authority return |
No workplan is finished. New source/rehearsal milestone tasks say explicitly what
is and is not proved. WP-0012-T03 remains a final service acceptance gate, not a
second estimate for its detailed implementation tasks. WP-0013-T02 similarly
consumes T04 preparation and T05 lifecycle acceptance. New task totals are **11
of 30 done**, useful as a checklist but still unsuitable as effort arithmetic.
Central REST readback at 10:18:38Z verifies all 30 task titles, statuses and
human-action flags against the source files, and all four workplans remain active.
Receipt: `goal-progress-statehub-2026-10-31.json`. `statehub fix-consistency`
synchronized the task records and regenerated the work-record index; the three
renamed titles were explicitly reconciled from the files because that command
does not synchronize existing task titles.
Next task state changes must occur at the named milestone: execution receipt,
independent postflight, native recurring run, or explicit productive verdict.
Any failed review becomes a concrete live task. Progress updates should name
which task advanced and its next closure condition, rather than only append a
long session narrative.
## Immediate sequence
1. WP-0012-T07: receive and verify the existing attended telemetry route execution.
Its receipt was absent at the latest native observation (10:04:37Z). The reviewed
packet and digest4d848106 are unchanged; this audit performs no privileged action.
2. WP-0012-T08/T04: finish the supervised inactive installer and resolve operating
retention/capacity requirements. Source primitives are complete; installation
and timer activation have not occurred.
3. WP-0012-T09/T10: prove native capture and failure reception, then activate and
observe the already approved schedule after its prerequisites are met.
4. Resume WP-0013 fidelity/journey review and WP-0014 source-exception/cohort work;
prepare WP-0015 productive flow and general sender ownership returns. These
lanes are not completed by backup work and must remain visible.
There is no need to rerun completed storage, date, image or one-off email commands,
or to approve the already settled alert destinations and schedule again.

View file

@ -0,0 +1,243 @@
{
"schema": "coulomb.goal-task-tracking-audit.v1",
"verified_at": "2026-10-31T10:18:38.646453+00:00",
"source": "central State Hub REST readback compared with authoritative workplan files",
"workplans": [
{
"record_id": "CSOC-WP-0012",
"id": "0cd1f513-f26e-5707-b646-8b4bbe6369fc",
"status": "active"
},
{
"record_id": "CSOC-WP-0013",
"id": "70370f4e-7cba-5b0a-853b-fedcd2bd49a5",
"status": "active"
},
{
"record_id": "CSOC-WP-0014",
"id": "db6b85dc-f2f0-5283-ac52-3a6af28eb5b5",
"status": "active"
},
{
"record_id": "CSOC-WP-0015",
"id": "38208f72-c285-56fa-be44-de9b59a4e031",
"status": "active"
}
],
"tasks": [
{
"record_id": "CSOC-WP-0012-T01",
"id": "dc470337-585f-517d-b2a5-92e89a7dbec8",
"title": "T01 \u2014 Admit and verify independent offsite custody",
"status": "done",
"needs_human": false
},
{
"record_id": "CSOC-WP-0012-T02",
"id": "25ae6330-d26f-54ee-a599-2eca3a2e274d",
"title": "T02 \u2014 Activate and prove the first encrypted paired recovery point",
"status": "done",
"needs_human": false
},
{
"record_id": "CSOC-WP-0012-T03",
"id": "ded6fc1d-0819-57c5-9213-e64db76bc6ed",
"title": "T03 \u2014 Establish scheduled backup, monitoring and service evidence",
"status": "progress",
"needs_human": false
},
{
"record_id": null,
"id": "a36722a5-5f13-5728-9d58-24f030c2bb00",
"title": "T04 \u2014 Admit retention, capacity and historical-copy disposition",
"status": "progress",
"needs_human": true
},
{
"record_id": null,
"id": "380ecf13-cd24-5930-88c3-fb5dabc70dec",
"title": "T05 \u2014 Verify both approved backup alert destinations",
"status": "done",
"needs_human": false
},
{
"record_id": null,
"id": "5adde49c-e9a3-51bd-bdce-cba60d6f3ec1",
"title": "T06 \u2014 Implement and rehearse recurring alert delivery sources",
"status": "done",
"needs_human": false
},
{
"record_id": null,
"id": "8c8e4810-d967-54b2-ae49-25d367eac459",
"title": "T07 \u2014 Deploy and independently verify the recurring email route",
"status": "progress",
"needs_human": true
},
{
"record_id": null,
"id": "ca41b874-5e09-538e-9692-d31d990d679b",
"title": "T08 \u2014 Finish the supervised source installer and install inactive units",
"status": "progress",
"needs_human": false
},
{
"record_id": null,
"id": "c30bc200-6e0c-5651-b53a-be7a6f3dd207",
"title": "T09 \u2014 Prove native paired service and recurring failure reception",
"status": "todo",
"needs_human": false
},
{
"record_id": null,
"id": "009c9b51-32d4-5a35-a771-7cff0059c042",
"title": "T10 \u2014 Activate and observe the approved recurring schedule",
"status": "todo",
"needs_human": false
},
{
"record_id": null,
"id": "61f5f196-40e4-5901-a10e-318304809a00",
"title": "T11 \u2014 Close service registration, provenance, cost and smoke evidence",
"status": "todo",
"needs_human": false
},
{
"record_id": null,
"id": "54af74b0-3212-537e-a02c-d2d8a091caf9",
"title": "T12 \u2014 Agree and prove complete client offboarding and expiry",
"status": "todo",
"needs_human": false
},
{
"record_id": "CSOC-WP-0013-T01",
"id": "4d18a390-c82a-5d6b-8509-1b1704975150",
"title": "T01 \u2014 Finish unambiguous storage enforcement",
"status": "done",
"needs_human": false
},
{
"record_id": "CSOC-WP-0013-T02",
"id": "8d06cdee-e0ce-5c3e-bf98-705deed0ee62",
"title": "T02 \u2014 Complete content fidelity and revision lifecycle",
"status": "progress",
"needs_human": false
},
{
"record_id": "CSOC-WP-0013-T03",
"id": "8edd7661-17b0-5aa0-b177-6170aa159623",
"title": "T03 \u2014 Review productive sharing and personal portability",
"status": "todo",
"needs_human": false
},
{
"record_id": null,
"id": "17a2e781-5e44-5e89-8b76-e357d32de7ab",
"title": "T04 \u2014 Prepare private corpus fidelity review evidence",
"status": "done",
"needs_human": false
},
{
"record_id": null,
"id": "c2986a84-4da2-5fb3-b021-7bbe5104fe47",
"title": "T05 \u2014 Accept revision retention and interrupted copy or move recovery",
"status": "todo",
"needs_human": false
},
{
"record_id": "CSOC-WP-0014-T01",
"id": "0002882d-f156-5a5d-b524-d04793f4684d",
"title": "T01 \u2014 Reconcile retained inventory and nominate the next cohort",
"status": "progress",
"needs_human": true
},
{
"record_id": "CSOC-WP-0014-T02",
"id": "9257e4df-4b34-5127-9485-0118b9c203b8",
"title": "T02 \u2014 Review remaining journeys and record transfer decisions",
"status": "todo",
"needs_human": false
},
{
"record_id": "CSOC-WP-0014-T03",
"id": "599b4b6a-829d-5fe5-b52d-ff419e548fa8",
"title": "T03 \u2014 Decide service and host cutover for accepted cohorts",
"status": "wait",
"needs_human": true
},
{
"record_id": "CSOC-WP-0014-T04",
"id": "3018caa3-0f7b-5cc4-85e9-4dc4f41be9f7",
"title": "T04 \u2014 Preserve original dates in the accepted live cohort",
"status": "done",
"needs_human": false
},
{
"record_id": null,
"id": "f1c11eb8-20c4-576f-88b8-6b650b11e987",
"title": "T05 \u2014 Capture retained inventory and prepare deterministic draft trees",
"status": "done",
"needs_human": false
},
{
"record_id": null,
"id": "56e17aac-da6a-5f29-9781-5a5ebdd7e022",
"title": "T06 \u2014 Reconcile and verify dates for every remaining source tree",
"status": "progress",
"needs_human": false
},
{
"record_id": null,
"id": "26e9bbab-34cf-5616-94d4-61464027895c",
"title": "T07 \u2014 Transfer reconciled remaining cohorts and verify each return",
"status": "todo",
"needs_human": false
},
{
"record_id": "CSOC-WP-0015-T01",
"id": "e87ea643-7bee-5427-b4f5-b32f20dc2f29",
"title": "T01 \u2014 Admit and activate explicit transactional caller policies",
"status": "done",
"needs_human": false
},
{
"record_id": "CSOC-WP-0015-T02",
"id": "0604cb15-72c7-5d15-bb42-0335d4ec80df",
"title": "T02 \u2014 Establish platform sender and monitored reply/bounce ownership",
"status": "todo",
"needs_human": false
},
{
"record_id": "CSOC-WP-0015-T03",
"id": "286e60bf-76a1-5a18-bd2c-edd9d1400c41",
"title": "T03 \u2014 Complete independent ledger recovery and copy custody",
"status": "done",
"needs_human": false
},
{
"record_id": "CSOC-WP-0015-T04",
"id": "7c718d86-8f0d-5cb2-a765-b0c07116005c",
"title": "T04 \u2014 Implement, rehearse and release owner-spanning browser journeys",
"status": "done",
"needs_human": false
},
{
"record_id": null,
"id": "120ec9a8-6340-576f-8a3c-b8139c0dc25a",
"title": "T05 \u2014 Obtain productive registration and invitation flow verdicts",
"status": "todo",
"needs_human": false
},
{
"record_id": null,
"id": "e17a6d09-1fdd-5fa1-a36d-763802e37f7f",
"title": "T06 \u2014 Verify the native reset-authority owner return",
"status": "todo",
"needs_human": false
}
],
"task_count": 30,
"done_count": 11,
"all_status_title_and_human_flags_match": true,
"effort_estimate_is_not_task_count": true
}

View file

@ -16,17 +16,29 @@ state_hub_workstream_id: "0cd1f513-f26e-5707-b646-8b4bbe6369fc"
Residual acceptance from CSOC-WP-0008, split at the user's request. Existing implementation/release/acceptance evidence remains in the originating workplan; these tasks own the remaining concrete outputs. Source checks never grant runtime or productive acceptance.
## T01 — Admit independent offsite custody and retention
## Current execution map — 2026-10-31
Completed: T01 independent custody, T02 recovery, T05 dual-destination proof and T06 recurring source/rehearsal. T04 owns retention/capacity; T07 the pending attended route; T08 inactive installation; T09 native operational proof; T10 schedule activation/observation. T11/T12 expose the previously buried service-contract work. T03 remains the final service acceptance gate and is not an additional implementation estimate on top of T07–T12.
The [four-workplan assessment](../docs/release/goal-progress-audit-2026-10-31.md)
records the scope split and effort estimate. Task counts are not effort percentages.
Historical notes retain the evidence trail; this map and the task blocks govern
current status. No original acceptance requirement has been dropped.
## T01 — Admit and verify independent offsite custody
```task
id: CSOC-WP-0012-T01
status: progress
status: done
priority: high
needs_human: true
intervention_note: "Scoped API custody, protected kit and first application recovery are native-verified; no repeat scope/schedule approval or routine personal login is needed. Historical local production-pair copies still need explicit owner disposition. Retention/capacity and monitored scheduling remain open."
state_hub_task_id: "dc470337-585f-517d-b2a5-92e89a7dbec8"
needs_human: false
```
**Current scope after the October 31 tracking audit:** Independent publisher/reader/key custody and protected-kit retrieval are complete. The original retention, capacity and historical-copy disposition scope continues in live task T04. First application recovery remains completed T02; ongoing monitoring belongs to T03 and T07–T10.
Earlier dated notes below are retained as history, not the current task state.
Use existing RPF-WP-0053-T02/T03/T06 credential-pair/prefix/escrow admission. Own the coulomb-social consumer acceptance, not another credential provisioning lane. Record capacity, retained independent retrieval receipts, RPO/RTO and expiry of temporary production-pair copies; no secrets in records.
2026-10-27: User approved the scoped node executor/delivery (decision
@ -525,6 +537,122 @@ founder return, independently verify the receipt and actual route, then complete
consumer installation and native received-signal/replay/producer-death proof.
Existing capacity/retention/copy-disposition and WP13/14/15 obligations persist.
2026-10-31 inactive installation primitive: strict sealed-bundle reader and
transactional source installer now validate the22-member/19-target archive,
preserve unchanged/shared pinned helpers, journal preimages and staged identities
before replacement, verify inactive units and all file readbacks, and support
explicit interruption-safe rollback. Scope excludes credentials, capture and
timer starts. Native target observation finds only3 existing files,16 missing,
all5 units absent/inactive and both locks free at observation time. Route receipt
4d848106 remains absent and native receiver is still pending-only; the founder
command is unchanged. Review: docs/release/backup-source-installer-review-2026-10-31.md.
The terminal caller/lock/route/profile gate and exact final installation review
remain to prepare; no production target was modified. Original native execution,
signal/replay/dead-producer and capacity/retention/disposition/service gates remain.
## T04 — Admit retention, capacity and historical-copy disposition
```task
id: CSOC-WP-0012-T04
status: progress
priority: high
state_hub_task_id: "a36722a5-5f13-5728-9d58-24f030c2bb00"
needs_human: true
intervention_note: "Historical private production-pair copies still need explicit owner disposition; retention/capacity admission remains open. Existing custody and schedule approval are settled."
```
Remaining scope from T01. Close with owner-admitted capacity/headroom limits, a current generation/expiry plan, and explicit retention or deletion disposition for historical private production-pair copies. Execute only admitted expiry and retain native receipts. Proposed limits and a deletion candidate list are not admission. Evidence: `docs/release/backup-capacity-review-2026-10-30.md` and `generation-retention-post-date-2026-10-31.json`. No deletion has occurred. Existing RPF-WP-0053 custody/expiry ownership remains canonical.
## T05 — Verify both approved backup alert destinations
```task
id: CSOC-WP-0012-T05
status: done
priority: high
state_hub_task_id: "380ecf13-cd24-5930-88c3-fb5dabc70dec"
```
State Hub central readback verifies event816e6775 and inbox message8d70c5a7 to platform-root. The one-off SMTP proof was independently verified and the user explicitly confirmed receipt at bernd.worsch@gmail.com. Destination decisionf4df16b5 is settled. Evidence: `docs/release/backup-alert-destinations-2026-10-31.json` and `backup-alert-email-2026-10-31/verification.json`. The original provider receipt remains unchanged; human receipt confirmation is separate. This closes destination/delivery proof only; recurring monitoring is T07–T10. Do not resend the proof.
## T06 — Implement and rehearse recurring alert delivery sources
```task
id: CSOC-WP-0012-T06
status: done
priority: high
state_hub_task_id: "5adde49c-e9a3-51bd-bdce-cba60d6f3ec1"
```
Durable independent channel attempts, retry/replay, failed/pending/stale episodes and unit integration are implemented. Native isolated Alertmanager-to-local-SMTP, route and systemd validation pass. The sealed operating archive has 22 members and 19 targets. Evidence: `docs/release/backup-alert-recurring-integration-2026-10-31.md`, `backup-alert-isolated-smtp-2026-10-31.json` and `backup-operating-delivery-alerts-2026-10-31.json`. This is source/rehearsal completion; installation and production event delivery remain T07–T09.
## T07 — Deploy and independently verify the recurring email route
```task
id: CSOC-WP-0012-T07
status: progress
priority: high
state_hub_task_id: "8c8e4810-d967-54b2-ae49-25d367eac459"
needs_human: true
intervention_note: "Existing attended route packet4d848106 awaits founder execution and independent verification. Destination/test-send approval is settled; do not resend the one-off proof."
```
The exact owner execution packet is ready; durable receipt was absent at the 10:04:37Z observation. Founder execution and independent complete-resource/runtime-config postflight remain. Use the existing reviewed owner packet in `/home/worsch/rapp-telemetry/docs/coulomb-backup-route-execution-2026-10-31.md`, digest4d848106; inspect any existing attempt before further action. No renewed recipient approval is needed. Close only on durable verified native success, preserving the existing PVC and unrelated routes.
## T08 — Finish the supervised source installer and install inactive units
```task
id: CSOC-WP-0012-T08
status: progress
priority: high
state_hub_task_id: "ca41b874-5e09-538e-9692-d31d990d679b"
```
The installation/rollback library and 15 disposable-filesystem cases pass; the full gate has 475 passes with zero skips. The final supervised wrapper must bind sources, bundle, preimages, locks, route/profile and inactive-unit guards. Then obtain the attended execution return and verify installed hashes and disabled units. Evidence: `docs/release/backup-source-installer-review-2026-10-31.md` and its validation JSON. Three target files exist; other 16 targets and all five units were absent in the observation. No installation has occurred.
## T09 — Prove native paired service and recurring failure reception
```task
id: CSOC-WP-0012-T09
status: todo
priority: high
state_hub_task_id: "c30bc200-6e0c-5651-b53a-be7a6f3dd207"
```
After T07/T08 and applicable T04 operating admission, prove a native paired service capture, exact primary/mirror receipt, independent retrieval, received failed/pending/stale events in both channels, retry and restart continuity, and outside-producer failure detection. Retain correlated receipts without claiming an Alertmanager handoff is recipient delivery. Simulated source tests and the one-off email cannot close this task.
## T10 — Activate and observe the approved recurring schedule
```task
id: CSOC-WP-0012-T10
status: todo
priority: high
state_hub_task_id: "009c9b51-32d4-5a35-a771-7cff0059c042"
```
After T04 and T07–T09, activate the already approved 03:15 UTC schedule with five-minute jitter, RPO24h/stale26h and attended RTO60min target. Verify native timer/service state and subsequent scheduled capture/freshness evidence. Record measured recovery limits; cached-image rehearsal is not cold-start recovery. Do not ask the user to approve the schedule again. Close on observed operation, not merely enabling a timer.
## T11 — Close service registration, provenance, cost and smoke evidence
```task
id: CSOC-WP-0012-T11
status: todo
priority: high
state_hub_task_id: "61f5f196-40e4-5901-a10e-318304809a00"
```
Remaining T03 service-contract §§1–5 evidence: authenticated ops registration, canonical client × app × instance finance mapping and current ingestion/report, Forgejo successor provenance and governing identity-specialization decision, current SLO evidence, and CSOC-IN-0004 stage-1 smoke reconciliation. Consume existing identity/cohort returns from WP-0014/0015 without duplicating owner implementations. Use `docs/release/service-contract-conformance-2026-10-27.md` and `service-provenance-reconciliation-2026-10-30.md`. Resource requests and planning labor are not booked costs.
## T12 — Agree and prove complete client offboarding and expiry
```task
id: CSOC-WP-0012-T12
status: todo
priority: high
state_hub_task_id: "54af74b0-3212-537e-a02c-d2d8a091caf9"
```
Remaining T03 service-contract §6: resolve external/unattributed data, obtain private delivery/acceptance of complete client export, and agree instance teardown, sessions, logs and primary/mirror/protected-kit expiry. Current packaged export proof covers 85 selected files and four record sets; it is not offboarding acceptance. Coordinate retention with T04 and personal portability with WP-0013-T03. Record non-destructive review first; do not infer authorization to delete data.
## Completion
Finish when every task above has its stated evidence and acceptance, or hand off any newly discovered residual to a live work record first. Cross-owner dependencies remain their existing canonical records.

View file

@ -16,6 +16,15 @@ state_hub_workstream_id: "70370f4e-7cba-5b0a-853b-fedcd2bd49a5"
Residual acceptance from CSOC-WP-0008, split at the user's request. Existing implementation/release/acceptance evidence remains in the originating workplan; these tasks own the remaining concrete outputs. Source checks never grant runtime or productive acceptance.
## Current execution map — 2026-10-31
T01 storage enforcement is complete. T04 now exposes completed fidelity-review preparation. T02 still owns actual corpus/assets fidelity verdicts and final content acceptance; its revision lifecycle detail is T05. T03 owns four separate UC-003/004/005/006 productive verdicts. No review verdict has been inferred from tests or weekly-call acceptance.
The [four-workplan assessment](../docs/release/goal-progress-audit-2026-10-31.md)
records the scope split and effort estimate. Task counts are not effort percentages.
Historical notes retain the evidence trail; this map and the task blocks govern
current status. No original acceptance requirement has been dropped.
## T01 — Finish unambiguous storage enforcement
```task
@ -172,6 +181,28 @@ Review owner Share space/revocation, reader/outsider denial, account-local expor
Prepared exact UC-003–006 steps in docs/usecases/sharing-portability-review.md;
no acceptance inferred.
## T04 — Prepare private corpus fidelity review evidence
```task
id: CSOC-WP-0013-T04
status: done
priority: high
state_hub_task_id: "17a2e781-5e44-5e89-8b76-e357d32de7ab"
```
Captured-source audit and private source/product cards cover 245 records/242 bodies, explicitly retaining three missing bodies and six markup-change cases. Review steps identify source/product comparison and separate resource review. Evidence: `docs/release/corpus-rendering-audit-2026-10-28.json`, `bubble-source-continuation-2026-10-31.json` and `docs/usecases/sharing-portability-review.md`. This closes preparation only; the actual verdict belongs to T02.
## T05 — Accept revision retention and interrupted copy or move recovery
```task
id: CSOC-WP-0013-T05
status: todo
priority: high
state_hub_task_id: "c2986a84-4da2-5fb3-b021-7bbe5104fe47"
```
Explicit lifecycle portion of T02: review the existing revision purge/retention policy and failed multi-file copy/move recovery, preserve source/incoming-address authorization, and obtain the required operational/product acceptance. Reuse existing source and crash-recovery tests; investigate concrete gaps before adding implementation. No live purge is authorized by task creation. Close with the agreed policy and evidence for the intended lifecycle.
## Completion
Finish when every task above has its stated evidence and acceptance, or hand off any newly discovered residual to a live work record first. Cross-owner dependencies remain their existing canonical records.

View file

@ -16,6 +16,15 @@ state_hub_workstream_id: "db6b85dc-f2f0-5283-ac52-3a6af28eb5b5"
Residual acceptance from CSOC-WP-0008, split at the user's request. Existing implementation/release/acceptance evidence remains in the originating workplan; these tasks own the remaining concrete outputs. Source checks never grant runtime or productive acceptance.
## Current execution map — 2026-10-31
T05 records completed capture/tooling preparation; T04 now closes the independently verified accepted-cohort date correction. T01 still owns source exceptions, currentness and identity/grant/assets reconciliation. Remaining date verification is T06 and actual further-cohort migration is T07. T02 productive journey/transfer verdicts and T03 the separate cutover decision remain open. Bubble login renewal is currently cleared; four source graph exceptions and one unassigned record remain.
The [four-workplan assessment](../docs/release/goal-progress-audit-2026-10-31.md)
records the scope split and effort estimate. Task counts are not effort percentages.
Historical notes retain the evidence trail; this map and the task blocks govern
current status. No original acceptance requirement has been dropped.
## T01 — Reconcile retained inventory and nominate the next cohort
```task
@ -134,17 +143,20 @@ Depends on WP-0012 service/recovery and WP-0013 privacy/content returns. Link se
for the cutover return, not resolved by closing WP-0008. Retain parallel hosts
until an explicit cohort/apex decision; Bubble retirement requires all retained use cases transferred or explicitly discontinued.
## T04 — Preserve original creation dates and reconcile the accepted cohort
## T04 — Preserve original dates in the accepted live cohort
```task
id: CSOC-WP-0014-T04
status: progress
status: done
priority: high
needs_human: false
intervention_note: "Founder date correction47829c7a and accepted-cohort per-source-ID manifest are independently verified. Do not rerun the date command. Task remains open for remaining tree/source-date exceptions and productive verification, dependent on source continuation under T01."
state_hub_task_id: "3018caa3-0f7b-5cc4-85e9-4dc4f41be9f7"
needs_human: false
```
**Current scope after the October 31 tracking audit:** The accepted-cohort correction and independent per-source-ID postflight are complete. The original requirement covering every remaining tree/page/chunk and its productive verification continues in live task T06. All-space transfer remains T07. Do not replay the completed date command.
Earlier dated notes below are retained as history, not the current task state.
User requirement from 2026-10-27 (decision
4aab0481-8597-5e47-bc8c-46e8d3b524ed): preserve creation dates of spaces,
pages and every chunk. Import now restores SQL Space.created_at and preserves
@ -286,6 +298,39 @@ exceptions and their productive verification keep T04 progress. T01 needs renewe
Bubble access; no broad import, source exception resolution or transfer acceptance
is inferred. The old date command must not be replayed.
## T05 — Capture retained inventory and prepare deterministic draft trees
```task
id: CSOC-WP-0014-T05
status: done
priority: high
state_hub_task_id: "f1c11eb8-20c4-576f-88b8-6b650b11e987"
```
Bounded all-space and reference continuation retain all 71 known spaces, 245 article records/242 bodies and 67 draft trees, with source hashes/date manifests and isolated import rehearsal. Four source graph groups plus the unassigned record remain explicit exceptions, not invented content. Evidence: `docs/release/bubble-offline-preparation-2026-10-28.json` and `bubble-source-continuation-2026-10-31.json`. This completes inventory/tooling preparation only. Source completeness and mappings remain T01; productive transfer is T07.
## T06 — Reconcile and verify dates for every remaining source tree
```task
id: CSOC-WP-0014-T06
status: progress
priority: high
state_hub_task_id: "56e17aac-da6a-5f29-9781-5a5ebdd7e022"
```
Remaining all-space scope split from T04. Preserve original space/page/chunk creation dates in every remaining tree and verify per-source-ID manifests after transfer. Resolve missing/conflicting dates through source evidence or explicit disposition under T01. Existing 67-tree isolated rehearsal and the completed accepted-cohort correction are evidence, not acceptance of all remaining cohorts. Preserve post-transfer local edits, copies, aliases and grants.
## T07 — Transfer reconciled remaining cohorts and verify each return
```task
id: CSOC-WP-0014-T07
status: todo
priority: high
state_hub_task_id: "26e9bbab-34cf-5616-94d4-61464027895c"
```
After each source/identity/grant/assets mapping is ready under T01 and content rules under WP-0013, prepare and execute the authorized stepwise all-space migration in the requested LIFO order with restartable per-space receipts. Verify content, original dates (T06), ownership, explicit grants, assets and links without overwriting later local edits. User productive transfer verdicts remain T02. All spaces are eventual scope; a draft tree is not a productive import. Cutover/retirement remains T03.
## Completion
Finish when every task above has its stated evidence and acceptance, or hand off any newly discovered residual to a live work record first. Cross-owner dependencies remain their existing canonical records.

View file

@ -16,6 +16,15 @@ state_hub_workstream_id: "38208f72-c285-56fa-be44-de9b59a4e031"
Residual acceptance from CSOC-WP-0010, split at the user's request. Existing implementation/release/acceptance evidence remains in the originating workplan; these tasks own the remaining concrete outputs. Source checks never grant runtime or productive acceptance.
## Current execution map — 2026-10-31
T01 caller policy, T03 independent ledger recovery and the narrowed T04 implementation/native rehearsal/application release are complete. T02 still owns the general platform sender, reply/inbox/support, DNS and bounce operation; backup-specific Gmail receipt does not close it. T05 exposes productive flow verdicts and T06 the remaining native reset-authority owner return.
The [four-workplan assessment](../docs/release/goal-progress-audit-2026-10-31.md)
records the scope split and effort estimate. Task counts are not effort percentages.
Historical notes retain the evidence trail; this map and the task blocks govern
current status. No original acceptance requirement has been dropped.
## T01 — Admit and activate explicit transactional caller policies
```task
@ -64,18 +73,21 @@ The app gate now binds real encryption/recovery and scoped quota continuity test
pending explicit owner disposition, with no inferred expiry/deletion. Production
restore still requires fencing and post-capture reconciliation. See the audit.
## T04 — Establish owner-spanning browser journeys and productive flow verdicts
## T04 — Implement, rehearse and release owner-spanning browser journeys
```task
id: CSOC-WP-0015-T04
status: progress
status: done
priority: high
needs_human: false
decision_id: "75b94bb6-4709-495f-91fe-43e53e2867ed"
intervention_note: "Founder release9f1daf6c is complete and independently verified at revision19; do not rerun. Release execution gate cleared. Productive flow verdicts and owner acceptance remain open."
state_hub_task_id: "7c718d86-8f0d-5cb2-a765-b0c07116005c"
needs_human: false
```
**Current scope after the October 31 tracking audit:** The owner-source and native isolated browser gates plus the exact revision 19 application release are complete. Productive UC-010/011 verdicts, current Case B and any remaining reset review continue in T05; the native reset-authority owner return continues in T06. Existing personal reset acceptance remains preserved. This split does not promote unaccepted journeys to established.
Earlier dated notes below are retained as history, not the current task state.
Use isolated issuer/directory/local mail sink/app for UC-009/010/011. Bind exact mandatory browser nodes without production URLs/accounts or SMTP provider sends; test expired/replayed handles and tenant/client/caller denials. Future UC-012 needs a user-selected product template/caller. Preserve UC-008 manual mail distribution and UC-009 existing personal reset acceptance.
2026-10-11: the checkout has a loopback issuer, directory and mailbox double. The browser node is bound on UC-009/010/011 and still `established: false`. It covers reset-to-local-mailbox, sign-in, callback replay, expired and reused handles, tenant and client refusal, registration verify/cancel, and caller/suppression invitation counts. No SMTP, production account, or live issuer is contacted. Real user-engine/email-connect admission, DNS and productive per-flow verdicts remain open. UC-012 stays deferred. Gate for this slice: `make check` 200 passed.
@ -176,6 +188,28 @@ packaged client export verifies85files without source mutation. Full make check
execution; RAPPS-WP-0015-T05 is complete. Productive flow and service/offboarding
acceptance remain open. Return: docs/release/identity-export-release-return-2026-10-31.md.
## T05 — Obtain productive registration and invitation flow verdicts
```task
id: CSOC-WP-0015-T05
status: todo
priority: high
state_hub_task_id: "120ec9a8-6340-576f-8a3c-b8139c0dc25a"
```
Acceptance scope split from T04: current Case B, UC-010 registration and UC-011 invitation/resend/cancel/expiry behavior need private owner-spanning productive review and explicit verdicts. Preserve existing UC-009 personal-reset acceptance and UC-008 manual distribution; review only remaining reset differences. Keep each gap as live work and do not promote candidate journeys from isolated tests alone. UC-012 remains deferred pending an explicitly selected template/caller, not an implied requirement to add arbitrary notifications. Review sources: `docs/usecases/platform-communication.md` and `docs/identity/smoke.md`.
## T06 — Verify the native reset-authority owner return
```task
id: CSOC-WP-0015-T06
status: todo
priority: high
state_hub_task_id: "e17a6d09-1fdd-5fa1-a36d-763802e37f7f"
```
Remaining owner admission from T04 is canonical NK-WP-0054-T05. Isolated native Authelia/LLDAP reset and full browser integration are proven, including read-only-bind refusal and successful scoped password replacement. Obtain and assess the owner native authority/runtime return; preserve MFA/TLS/directory boundaries and link acceptance here. Do not create a duplicate provisioning lane or infer a live grant from the synthetic proof. Evidence: `docs/release/native-recovery-browser-review-2026-10-31.md` and `native-password-reset-review-2026-10-30.md`.
## Completion
Finish when every task above has its stated evidence and acceptance, or hand off any newly discovered residual to a live work record first. Cross-owner dependencies remain their existing canonical records.