coulomb/commerce-canon
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
commerce-canon/workplans/IDENTITY-WP-0004-commerce-rename.md
tegwick 40d5792faf
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Plan commerce canon rename and record cutover readiness 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a070b5-4994-7271-bd8b-7c3dbcedec4b
2026-09-05 18:30:51 +02:00

6.8 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated state_hub_workstream_id
IDENTITY-WP-0004 workplan Rename identity-canon to commerce-canon with continuous history infotech identity-canon active codex canon 2026-09-05 2026-09-05 598275a1-8fbd-5607-8292-d992ead1487d

Repository rename to commerce-canon

Implements CFED-WP-0001-T03 under CUST-ADR-006 accepted-1. Project coordination and the concept ledger live in prj-canon-federation; this plan owns the donor repository's rename preparation and verification.

The user authorized proceeding with the rename on 2026-09-05. The remaining execution gate is technical, not a request to repeat that authorization. No operation may bypass a failing State Hub preflight.

Capture the immutable repository baseline

id: IDENTITY-WP-0004-T01
status: done
priority: high
state_hub_task_id: "c090a28b-bf82-5d2f-b1f6-670f1eaf1147"

Captured before adding this preparatory plan:

  • State Hub repository UUID: 8c82baea-bb40-435d-ac42-ec7a7c20dbb8.
  • Forgejo: https://forgejo.coulomb.social/coulomb/identity-canon, numeric ID 46.
  • Branch main; local and verified Forge head both 43c5c21a7a7e273241d9c7622db4e926ac9aadfa; checkout clean.
  • State Hub Forge identity verified through the supported API on 2026-09-05.
  • Three finished IDENTITY-WP plans and 14 tasks retained on the same UUID.
  • Registered paths: bnt-lap001:/home/worsch/identity-canon and 239.62.205.92.host.secureserver.net:/home/tegwick/identity-canon.

Refresh the baseline after committing preparation and immediately before cutover. The snapshot is evidence, not permission to rename a subsequently changed head.

Prepare metadata and coordinate external dependencies

id: IDENTITY-WP-0004-T02
status: progress
priority: high
state_hub_task_id: "8606bbbb-716d-5011-950e-29dc9ea3c2d8"

Apply the reviewed metadata patch from prj-canon-federation/docs/evidence/2026-09-05-commerce-metadata.patch only after rebind. It updates README/INTENT/SCOPE, classification, and records the migration. Regenerate AGENTS.md and CLAUDE.md after registering the canonical local path.

Classification: financials primary, government and infotech secondary; retain research category during migration. New post-rename plans use COMMERCE-WP-; this existing rename plan and all finished IDENTITY-WP plans keep their IDs. The generator infers the majority historical prefix, so append an explicit COMMERCE-WP override under the preserved agent-extension marker after generation.

The repository has no runtime app or package build. The existing CI smoke, capability registry, and documentation links still require verification. Identity capability identifiers are stable references; destination ownership is resolved during model migration, not by blindly renaming capability IDs.

Project tasks CFED-WP-0001-T08/T09 own cross-canon and fleet reference acceptance. Inventory each affected owner before cutover, including the second registered host, fabric/reuse-surface discovery and SBOM projection. Record owner evidence before claiming these consumers verified; do not assert changes on the remote host merely because its registered path is known.

Resolve signing and refresh the preflight

id: IDENTITY-WP-0004-T03
status: done
priority: high
state_hub_task_id: "1cd684ba-046b-5ff3-bb25-5424f82ee4b5"

Current blocker: State Hub returns preflight_signing_unavailable. REPOSITORY_RENAME_PREFLIGHT_SECRET must be supplied to the deployed API by its platform credential/deployment owner. Existing platform handoff: cd52ba10-de41-46ce-aa8b-9b44050da8f7, recorded by STATE-WP-0085-T09 and shared with FLEX-WP-0020. Do not put secret material into this plan or State Hub.

Use a fresh private mode-0600 preflight file. Require zero blockers, matching Forge ID/head, an available target, coordinated active work, and resolved external dependencies. The new plan itself is active work and must be explicitly coordinated. No operation journal has been started.

Execute the rename and prove continuity

id: IDENTITY-WP-0004-T04
status: progress
priority: high
state_hub_task_id: "2082388e-2096-5138-a7a6-40c9f71e1fb5"

Use statehub repo rename start/apply phases in order: forge-renamed, statehub-rebound, source-synced, consumers-verified, completed. Follow state-hub/docs/repository-rename-operations.md; use confirmation rename:8c82baea-bb40-435d-ac42-ec7a7c20dbb8:identity-canon:commerce-canon.

Preserve Forge ID 46 and the State Hub UUID. Obtain a fresh verification clone at the new coordinate and prove its exact baseline commit before source-synced. Rename the existing clean local checkout in place and update its remotes; register the new local path. Keep the other host's mapping until its checkout has actually moved. Verify the protected old-slug alias and historical work links. Apply metadata, regenerate instructions, preserve finished workplans byte-for-byte, and record actual cutover evidence. Run consistency and link checks.

Rollback uses the journal's rollback-preflight and rollback phases only when identity/head and old-name availability still permit it. Do not delete or steal an occupied slug. Local path/remotes and metadata must be restored consistently; retain verification evidence and do not delete repository history.

Close with evidence and live handoffs

id: IDENTITY-WP-0004-T05
status: wait
priority: medium
state_hub_task_id: "c78ce770-3e0c-505d-8eff-538fd305da52"

Attach operation verification and immutable identity evidence to CFED-WP-0001-T03. Confirm both registered-host dispositions, remotes, instructions, classification, finished-plan hashes, and owner-backed consumer verification. Hand off actionable residuals as live records before finishing. Canon layout/model/corpus migration remains with CFED-WP-0001-T04 through T13, not this rename plan.

Cutover coordination — 2026-09-05

RPF-WP-0035-T04 is done: signing version 2 delivered, State Hub Helm revision 59. Fresh read-only preflight passes with no blockers. The only active-work warning is this plan's own four pending tasks; codex coordinates them in this session and no concurrent donor-content migration is authorized during cutover.

Known external source: reuse-surface registry/federation/sources.yaml and local-repo-roster.yaml, plus generated federated index/cache. CFED-WP-0001-T09 owns the fleet sweep and will collect that repository's source/refresh evidence. Scans of ops-warden, railiance-fabric and sbom-nexus checked-in Markdown/YAML/JSON found no literal old-slug references. Live projections still require verification. The CI smoke uses dynamic GITHUB_REPOSITORY and has no hardcoded slug.

The registered railiance01 checkout is inspected separately; its path will not be rewritten in State Hub without proving its actual filesystem disposition. The user renewed instruction to continue once signing was provisioned.