Commit graph

110 commits

Author SHA1 Message Date
codex
5c6d8df755 docs: record central fleet projection reset (CUST-WP-0068-T09)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Image main-54b09ee. the-custodian reset-ack then fleet refuse-mode:
52 applied, 69 noop, 2 identifier-collision refusals, 0 retirements.
Fleet-ack not run — nothing was refused for retirement.
2026-08-28 21:42:05 +02:00
codex
6cd450fa55 finish CUST-WP-0068: recover, disposition, discard the cache
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Close T02–T06 from live hub evidence, disposition clay-borg product
records as not workplans, lift the task-reset restriction in state-hub,
dump and remove the retired local Postgres instance, and record ADR-010's
work-record divergence as closed.
2026-08-28 21:06:25 +02:00
codex
93b8174abd finish three custodian workplans from live hub evidence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Python Tests / pytest (push) Successful in 21s
Close CUST-WP-0064 after the 2026-08-24 unassisted fire ingested
clay-borg, close CUST-WP-0065 now that all 120 active repos project a
classification, and close ADHOC-2026-08-25. Mark CUST-WP-0067 T02/T10
done (reverse relays already gone; work-record recovery lives on 0068).
Park the later no-checkout SBOM regression as CUST-IN-0015. Teach the
classification gate to use this host's checkout path.
2026-08-28 20:27:05 +02:00
codex
d0216adb44 feat(workplan): close CUST-WP-0067-T05 and open T10 for the workplan divergence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
All 44 cache-only repository records resolved: 43 onboarded and classified,
agent-harness dropped by owner decision. Central holds 121 repositories.

Corrects an earlier claim in this workplan that the cache would hold nothing
unique once the repository records were resolved. That generalised a
repository-scoped result: the cache still holds ~400 workplans and ~1,950 tasks
that exist nowhere else, which is ADR-010's original divergence.

The cache database still must not be discarded.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 14:04:23 +02:00
codex
b5205d66b9 docs(recovery): drop agent-harness by owner decision
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 1s
Superseded by glas-harness and the rein concept, so there is nothing to
restore. Not onboarded to central; its cache-only record is left to disappear
when the cache database is discarded, rather than preserved as a hub-only
record with no backing file.

Successors verified present and classified on central before dropping.
Ten records remain outstanding.

Refs CUST-WP-0067-T05

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 13:51:05 +02:00
codex
005d198bdd feat(workplan): CUST-WP-0067-T07 files repointed on both machines
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
178 AGENTS.md files moved off the 127.0.0.1:18000 reverse tunnel to the
in-cluster address; both machines report zero stale rows. 100 pushed from the
workstation, 74 picked up by pull on the node, 4 handled individually.

binky-control committed but not pushed — it carries 6 pre-existing unpushed
commits that are not this change's to publish. activity-core was already 39
behind with an unrelated dirty file; only AGENTS.md was taken from origin.

state-hub-railiance01 is now unblocked for removal.

Still open: the block has no single source, so this recurs on the next
topology change; and 68 non-AGENTS.md references need individual judgement
rather than substitution.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 00:25:07 +02:00
codex
7f19ad465b feat(workplan): close CUST-WP-0067 T04 and T05, open T09
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
rmgr repo-onboard is the missing managed_repos write path. 33 of 44 cache-only
repositories onboarded to central (78 -> 111); the other 11 carry written
dispositions rather than guessed classifications.

T04 uncovered why onboarding only worked from a workstation: the hub resolved
its classification allowed-values file from hardcoded developer checkouts, so
every classification write 500'd in the container. T09 delivers that file.

The local cache database must not be discarded yet — 11 records live only there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 23:35:58 +02:00
codex
2755e8c91f feat(workplan): close CUST-WP-0067-T08 — central MCP deployed and verified
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
state-hub-mcp serves SSE on ClusterIP 10.43.110.80:8001, verified from the node
rather than through a tunnel, and reads central's data end-to-end (79 repos).
Remote port map and dev-hub registration repointed off the reverse tunnel.

state-hub-mcp-railiance01 is now safe to remove. state-hub-railiance01 is not:
~120 AGENTS.md files still depend on it until T07.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 23:20:11 +02:00
codex
8af5018776 docs(recovery): record proposed tunnels.yaml changes for CUST-WP-0067-T02
The bridge config lives outside any repo and could not be edited from the
session. Captures the two health-check defects and the reverse-relay
retirement, with the sequencing constraint that remote agents must be
repointed before the relay entries are removed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 22:30:36 +02:00
codex
bd8f02b785 feat(workplan): rescope CUST-WP-0067 to retire the local hub instance
Operator decision 2026-08-24: rather than making two hub instances coexist
safely, retire the second one. The local postgres+uvicorn instance is what
impersonates central and is redundant with ADR-010 decision 3 plus Repo
Manager's file-derived index.

With it gone, state-hub-primary binds 127.0.0.1:8000 unchanged and every
existing default becomes correct with no call-site edits.

Adds the cache-only recovery export (44 records) as the T05 source.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 22:24:01 +02:00
codex
ff334f1a40 feat: automate classification convergence
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Python Tests / pytest (push) Successful in 21s
2026-08-23 13:05:47 +02:00
codex
6adafd25b7 workplans: project first owner classification
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
2026-08-23 12:44:04 +02:00
codex
2462abf61d workplans: record classification projection repair
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
2026-08-23 11:34:56 +02:00
codex
b9f3238953 workplans: close stale intakes and start classification migration
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 0s
2026-08-23 01:31:29 +02:00
codex
cb62de1b7e docs: select controlled SBOM source contract
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Assistant: codex
2026-08-22 23:57:53 +02:00
codex
c72fd7cfa4 docs: archived record of the State Hub suggestion backlog
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Complete contents of the suggestion-backlog capability at retirement: 10
suggestions, 10 notes, 5 relevance bumps, raised 2026-07-06 to 2026-07-16.
All closed as declined in the 2026-07-21 intake migration; none promoted.

Kept here rather than in state-hub because state-hub is being archived and
this record must outlive it -- same reasoning as retired-legacy-interfaces.md.

Mutations already 410 since CUST-WP-0061-T06; reads were held open only to
keep this history reachable. This file is what makes removing them safe
(slice E1, STATE-WP-0079-T05).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 07:41:42 +02:00
codex
0ab3e359ce docs: journal of retired legacy interfaces
Fleet-level record of legacy interfaces retired under the State Hub
retirement program. Kept here rather than in state-hub because state-hub is
being archived -- once it is read-only its legacy-meter tables stop being
queryable in practice, and this needs to outlive that.

Records the 15 workstream->workplan aliases retired on 2026-08-20 under
STATE-WP-0079-T05 slice E2, the one retired earlier, and the 4 still held
with the reason each is held. Documents the retirement standard including
the volume-scaled quiet ladder and why it exists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-20 07:28:36 +02:00
codex
c377f0d12c Mark flex-auth drain-plan row 23 on target
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
FLEX-WP-0011-T03: runtime already lives on railiance01; coulombcore has
no flex-auth namespace. Wave 7.3 is only an identity-endpoint follow-up.
2026-08-16 09:45:46 +02:00
codex
f55baa0879 Point coulomb-social rebuild seed at owning repo
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
coulomb-social is registered under domain communication / topic
coulomb-social; CSOC-WP-0001 lives in that repo. Convert the seed doc
from "no owning repo" to a historical pointer.
2026-08-09 00:35:32 +02:00
codex
aab187937b docs(ecosystem): complete hub stack consolidation (CUST-WP-0057)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 5s
Publish ecosystem architecture, event mapping, capability bridge, and async-base
decision docs; add cross-repo regression script; update extraction boundary and
bootstrap status; archive WP-0058 touch-ups.
2026-07-11 01:26:53 +02:00
codex
3f94308e2f CUST-WP-0058: closeout — finished and archived
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
All 8 tasks done. Handoffs delivered to fin-hub, core-hub,
vergabe-teilnahme, ops-hub, railiance-apps (backup HIGH), NetKingdom.
coulomb.social rebuild seeded (docs/coulomb-social-rebuild-seed.md).
SCOPE.md Current State updated.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-10 10:34:47 +02:00
codex
51e40f1b52 CUST-WP-0058-T07: delivery-lane conformance snapshot — 4 gaps, 1 HIGH
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Lane already live (f95de14 @ vergabe-teilnahme.whywhynot.de). PASS:
standalone shape, commit-SHA image, registry, TLS ingress, smoke.
FAIL: tenant keying (§1.3), ops-hub registration (§4.1), cnpg backups
(§4.2 — missing on ALL four prod DB clusters, railiance-apps alerted),
fin-hub cost attribution (§5.1). Evidence bundle under docs/evidence/.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-10 09:28:41 +02:00
codex
e61c7ed15c CUST-WP-0058: T04 approved, T05 client-hub scoping, T06 fin-hub gap done
Some checks failed
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Has been cancelled
Service contract v0.1 accepted (Bernd 2026-07-10). Client-hub scoped as
core-hub extension (client/engagement/app_instance/support_state, CLNT-WP
skeleton). fin-hub gap assessment: 5 gaps, FIN-WP-0002 skeleton posted to
fin-hub lane (msg 9c8e8ed4); recommendation fin-hub stays reporting-only.
Remaining: T07 delivery-lane pilot, T08 closeout.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-10 01:28:57 +02:00
codex
b26ffc10ef CUST-WP-0058: DR-1/2/3 resolved — consistency refinement, plan activated
Some checks failed
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Has been cancelled
DR-1: C (instance-per-client, early cost-optimization move)
DR-2: B (coulomb.social standalone app; Binky Hedgehog as client #1)
DR-3: A (app-local accounts; demand-gated NK-WP-0011 triggers)

Refinements: consolidation-ready data model required by the service
contract; coulomb.social auto-trigger for Keycloak retired in favor of
three demand triggers. T01-T03 done (NetKingdom notified), T04/T05
unblocked, workplan active.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-10 01:11:04 +02:00
codex
22100f94cf CUST-WP-0058: business platform enablement — DR set + workplan
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 36s
Decision records DR-1 (tenancy), DR-2 (coulomb.social shape), DR-3
(external identity) framing the Binky Hedgehog commercial lane on the
coulomb/HelixForge platform; coordination workplan for service contract,
client-hub scoping, fin-hub billing gap, and delivery-lane pilot.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-10 00:29:59 +02:00
codex
cab84b8649 Record WP-0005 T12 Option A: 30-day Gitea rollback window
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 21s
Align forgejo-production-decisions with operator choice to keep coulombcore
Gitea as read-only fallback through 2026-08-07.
2026-07-09 11:32:25 +02:00
codex
2e0deee2ef feat(terminology): prose sweep tool and custodian workplan cleanup (CUST-WP-0055 T04)
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 6s
Add sweep_workstream_prose.py for agent-guidance files, sweep active workplan
prose in-repo, tighten scan allowlist exclusions, and update ADR-001 closure
protocol to workplan-first terminology.
2026-07-08 16:35:37 +02:00
codex
e1c705c0f2 docs(CUST-WP-0055-T01): add fleet workplan terminology canon v0.1
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Define workplan as the canonical fleet term, document legacy bridges and
event subjects, and commit the 2026-07-08 terminology scan baseline.
2026-07-08 14:38:45 +02:00
codex
d0bcba96c9 docs(CORE-WP-0007): retire inter-hub-haskell in inventory and cutover record
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 4s
2026-07-08 12:48:04 +02:00
codex
af49c053f1 finish(CUST-WP-0054): workstation independence engineering closeout
Complete T04–T08: bulk Forgejo remote_url migration for all registered
repos, phase 5 stabilization tooling, dev-hub beachhead artifacts, and
phoenix drill runbook. Archive workplan with T09/T10 as operator gates.
2026-07-08 11:42:49 +02:00
codex
a272f5fcda Advance CUST-WP-0025: close T16/T17, add canon and fin-hub bootstrap
- Mark T16/T17 done with cutover evidence and decision coupling doc
- Add business-model-canvas and bootstrap-protocol canon (T20/T21)
- Record Core Hub readiness-summary evidence stubs
- Refresh fos-hub-bootstrap-sequence-status and core-hub-replacement-evidence
2026-07-08 00:52:17 +02:00
codex
3ea0291f54 Record T02 cutover Option A and close design decision set
Staged per-repo promotion as primary plan; freeze-all emergency fallback only.
All WP-0005 T02 production choices are now decided.
2026-07-07 17:00:05 +02:00
codex
89300bd5fc Record T02 backup decision: Option A (Nextcloud + age)
Daily forgejo dump and pg_dump, age-encrypted upload to Nextcloud WebDAV,
balanced retention (14 daily + 4 weekly), RPO 24h / RTO 4h.
2026-07-07 16:55:13 +02:00
codex
56943efbf7 Record T02 package scope: Option C (OCI, npm, generic)
Operator decided multi-ecosystem registry with npm as a launch requirement;
additional types follow inventory evidence. Update SMTP row to T06-done state.
2026-07-07 16:47:15 +02:00
codex
5aacf8770f Record IONOS SMTP decision and Forgejo mailer deployment
Document forgejo@coulomb.social on IONOS smtp.ionos.com:587; mailer live on
railiance01 via railiance-apps Helm. T06 password-reset test remains open.
2026-07-07 11:08:14 +02:00
codex
b8412994b7 docs: record state-hub Forgejo CI promotion main-0ca9c27 (Helm rev 8)
Update Phase 5 cutover evidence and CUST-WP-0054 T05 notes after
image.yaml #31 build and railiance01 deploy with working-memory sweep.
2026-07-07 01:14:11 +02:00
codex
8baa2d10ff feat: schedule Phase 5 checks; start T06 path decoupling
Add phase5 daily/closeout ActivityDefinitions, document schedules in Phase 5
evidence, and migrate daily triage sinks to custodian:// runtime URIs.
2026-07-07 00:48:36 +02:00
codex
03dc2070a3 docs: Phase 5 day-1 stabilization check — all gates green
Records phase5-stabilization-check.sh snapshot after CI image promotion;
T05 remains in progress until 72h window closes 2026-07-09.
2026-07-07 00:37:02 +02:00
codex
872266cb57 docs: record state-hub CI image promotion to main-375961c
Forgejo image.yaml #26 built and Helm rev 7 deployed on railiance01;
post-upgrade consistency sweep exit_code=0.
2026-07-06 20:22:23 +02:00
codex
40670dcc55 docs(CUST-WP-0054-T05): record post-cutover daily triage success
Manual activity-core trigger completed with daily_triage progress event
a99e644e and working-memory report daily-triage-2026-07-06-67685f1c.md.
2026-07-06 19:51:04 +02:00
codex
104c66763e docs(CUST-WP-0054-T05): open Phase 5 stabilization window
Record kickoff baseline checks, 72h monitoring gates, and a reusable
phase5-stabilization-check.sh script for daily health snapshots.
2026-07-06 19:41:42 +02:00
codex
c9764ba73c docs(CUST-WP-0054-T05): Phase 4 sweep checkout migration evidence
Record railiance01 clone tree, host_paths registration, and tooling for
bulk clone and path registration. Update T05 workplan with Phase 4 completion.
2026-07-06 19:24:28 +02:00
codex
0bebad0bae docs(CUST-WP-0054): update Phase 1 evidence with Forgejo image fix notes
Record main-d1a4fcf CI fix and DinD root cause after image rebuild.
2026-07-06 18:59:04 +02:00
codex
5d3b0120f1 docs(CUST-WP-0054): record Phase 3 access rewire to railiance01
state-hub-primary tunnel, activity-core in-cluster URL, fleet-state-hub
coulombcore retired. Production :8000 now serves railiance01 hub.
2026-07-06 18:57:43 +02:00
codex
5961e74bfc docs(CUST-WP-0054): record Phase 2 data migration evidence
coulombcore frozen; pg_restore to railiance01 with exact-count gate pass.
Phase 3 access rewire still pending.
2026-07-06 18:51:59 +02:00
codex
149afb104d docs(CUST-WP-0054): record Phase 1 empty stack evidence on railiance01
Phase 1 deploy complete: CNPG state-hub-db, Alembic at head, empty hub
healthy on ClusterIP 10.43.68.154. Documents gitea image workaround and
Forgejo rebuild prerequisite before Phase 2.
2026-07-06 18:38:35 +02:00
codex
284d11c735 docs(CUST-WP-0054): record Phase 1 empty stack evidence on railiance01
Phase 1 deploy complete: CNPG state-hub-db, Alembic at head, empty hub
healthy on ClusterIP 10.43.68.154. Documents gitea image workaround and
Forgejo rebuild prerequisite before Phase 2.
2026-07-06 18:28:27 +02:00
codex
5b51f90a9f CUST-WP-0054-T05 Phase 0 preflight evidence (baseline counts, dry-runs, image pull) 2026-07-06 18:08:02 +02:00
codex
fa715c29d5 CUST-WP-0054-T05: State Hub railiance01 cutover plan and task progress 2026-07-06 17:25:09 +02:00
codex
0d890a7155 Document activity-core tier-3 promotion; production set complete (CUST-WP-0054-T04) 2026-07-06 17:14:13 +02:00