coulomb-social/docs/release/source-date-release-review-2026-10-31.md

Accepted-cohort original-date correction — exact attended proposal

Founder-executed and independently verified on2026-10-31. Storage release5fd7ccd8 remains at Helm revision18. This separate correction is accepted under resolved decision 5eec458c-0f43-483d-a13c-a9d739ea6b08.

Verified execution return — do not replay

The durable root receipt completed at02:10:42Z with phase: completed, correction_status: completed and application_resumed: true. Its fresh pre-correction paired point is primary version1793412500034233, captured02:07:21Z on the current image with immutable provider readback. The controller's completed path establishes the native writer fence, exact helper admission/UID, whole-store postflight, helper deletion and application resume. The helper's component-level backup_provider_readback_performed_here:false and external_writer_fence_verified_here:false correctly reserve those external checks to the supervisor; they are not failed checks.

Independent read-only native postflight checks the frozen root capsule/journal, current revision18/image51281946, sole Ready PVC writer and absent helper UID. All13tables/114rows/86files match the exact derived final fingerprint. The selected SQL date and index date match the original source; removing exactly the inserted metadata line reproduces every original index byte.40owner-page renders, 40unsaved-outsider denials and public health/landing checks pass. Installation pins are unchanged and backup timers remain inactive.

A separate productive per-source-ID manifest verifies36original article dates and their exact page bytes, all3local pages, plus SQL/index dates, against the same hash-bound retained source. The14,485byte private manifest is retained under protected local recovery custody; its public proof contains only hashes/counts. This closes the selected accepted-cohort correction and date-manifest return. Remaining tree/source exceptions and transfer/user verdicts keep WP-0014-T04 open.

Evidence: source-date-receipt-2026-10-31.json, source-date-independent-postflight-2026-10-31.json and accepted-cohort-date-manifest-proof-2026-10-31.json. Preparation artifacts below remain historical and are not rewritten to imply prior admission. The founder command below has completed and must not be replayed.

Exact date proposal: sha256:47829c7ac2e6fd2c81fde1c914aec7c6e433098fa66985db6cfb9b34069942dc. The root-private seven-member capsule is on railiance01 at /tmp/csoc-date-capsule-20261031-v2.

Intended result and preserved data

Correct the previously selected accepted cohort's SQL space creation date to its original Bubble date, and insert that same original date as source_created_at in its existing index frontmatter. The exact selection, before/after dates, source hashes and index hash are in the private plan.json. The destination/source identities, original date, index hash and two proposed operations are identical to the previously reviewed plan. No date is derived from an ID, file timestamp or deployment time.

All36imported article dates still match the exact retained244-article source snapshot used by the prior plan. Its spaces/articles hashes match that plan. Three local pages, including the newly added page, are preserved; the existing article/copy/local page bytes are not rewritten. The index receives only the new metadata line, preserving its existing metadata, comments and body bytes. No content reimport, title/body replacement, grant/identity change, purge, email, timer activation, apex cutover or production-data restore is included.

This does not complete remaining source exceptions or grant corpus/transfer acceptance. The expired Bubble session and further cohort work remain separate.

Native preparation and current-pair rehearsal

The read-only native observer verifies current revision18/image51281946, cluster/deployment/PVC/node UIDs, actual running image, the local machine, installed backup helper hashes and public recipient. It verifies the sole Ready application writer, no autoscaler/GitOps adoption, inactive backup timers, migration0003/global constraint and actual helper server admission/dry-run. The complete baseline covers13SQL tables/114rows and86files, including migration bookkeeping. It was rechecked and the exact expected complete-store result was derived without changing SQL or files. The native observer reads production metadata; it does not capture, fence writers, create a live helper or apply dates. The observer's inherited offline production_access:false reporting was corrected to true before this final capsule/observation was produced.

The current plan and actual helper/controller also pass isolated rehearsals on disposable clones of the latest independently recovered pair. Normal completion and a lost reply after the real SQL/file commit both settle with one simulated capture and one actual apply, preserving/comparing all13tables/86files. Explicit recovery performs no second apply or capture; clones are removed and the retained source stays unchanged. Kubernetes/root fencing and provider capture are simulated in these rehearsals; actual native execution must establish those boundaries. The rehearsal now supports an explicit protected work root so private copies and diagnostics remain outside the temporary Git checkout.

Public metadata: source-date-native-proposal-2026-10-31.json. Current-pair rehearsal: source-date-supervisor-rehearsal-2026-10-31.json. The native capsule and rehearsal bind the same private plan/module/controller hashes. Full source gate: make check396passed, zero skips/failures/errors.

Execution, failure and recovery

The founder's exact terminal confirmation is required by the deployment-owner supervision rule: “The agent cannot approve itself.” Existing source-date requirements and backup/custody admissions remain valid; preparation does not approve this privileged operation.

The command repeats current-state checks, takes a fresh admitted paired backup with immutable primary readback, and compares the entire store across capture. It then holds backup locks, fences application/PVC writers, admits and verifies one exact helper, takes SQL/content locks and applies the two-field correction through a durable journal. Only the selected SQL date and index insertion may change; every table/file must match the derived result before the helper is removed and the application resumes. The backup pause has taken about56seconds; the subsequent sole-writer correction adds a separate maintenance pause.

An uncertain attempt keeps its helper/fence/journal for inspection. Do not replay --execute. Return its output for journal inspection; explicit founder-attended --recover reconciles the original capsule/journal/backup and never takes a new capture or replays the correction. Original index bytes and the private plan remain in the root journal, requiring the already tracked operator offboarding handoff and explicit expiry. No automatic deletion/expiry is performed.

Durable state: /var/lib/coulomb-social-backup/date-operations/47829c7ac2e6fd2c81fde1c914aec7c6e433098fa66985db6cfb9b34069942dc/. Successful completion needs phase: completed, correction_status: completed, the resumed application and independent native postflight. A settled absent or rolled-back correction does not satisfy the original-date task.

Founder terminal command (completed; do not replay)

From the workstation terminal where the storage release finished, run:

ssh -t railiance01 \
  'sudo -n python3 /tmp/csoc-date-capsule-20261031-v2/supervisor.py --capsule /tmp/csoc-date-capsule-20261031-v2 --expect-digest sha256:47829c7ac2e6fd2c81fde1c914aec7c6e433098fa66985db6cfb9b34069942dc --execute'

At the confirmation prompt enter:

APPLY-DATE sha256:47829c7ac2e6fd2c81fde1c914aec7c6e433098fa66985db6cfb9b34069942dc

Keep the terminal open, then return the final JSON result. The agent verifies the durable root receipt and actual target before recording correction acceptance.