diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md new file mode 100644 index 0000000..124eae1 --- /dev/null +++ b/WORK-RECORDS.md @@ -0,0 +1,80 @@ +# Work Records — reuse-surface + +> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record +> stage 3). Do not edit by hand — edit the source file/block listed for +> each record and re-run fix-consistency to refresh this index. Archived +> workplans are omitted; closed decisions/intakes/engagements stay listed +> so recently-resolved work is still visible. [auto] + +| Kind | ID | Status | Lane | Source | +| --- | --- | --- | --- | --- | +| workplan | REUSE-WP-0001 | finished | — | workplans/REUSE-WP-0001-statehub-bootstrap.md | +| workplan | REUSE-WP-0002 | finished | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| workplan | REUSE-WP-0003 | finished | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| workplan | REUSE-WP-0004 | finished | — | workplans/REUSE-WP-0004-registry-hardening.md | +| workplan | REUSE-WP-0005 | finished | — | workplans/REUSE-WP-0005-registry-federation.md | +| workplan | REUSE-WP-0006 | finished | — | workplans/REUSE-WP-0006-registry-hygiene-and-coverage.md | +| workplan | REUSE-WP-0007 | finished | — | workplans/REUSE-WP-0007-interactive-catalog.md | +| workplan | REUSE-WP-0008 | finished | — | workplans/REUSE-WP-0008-graph-explorer.md | +| workplan | REUSE-WP-0009 | finished | — | workplans/REUSE-WP-0009-cli-hardening.md | +| workplan | REUSE-WP-0010 | finished | — | workplans/REUSE-WP-0010-network-federation.md | +| workplan | REUSE-WP-0016 | finished | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| workplan | REUSE-WP-0020 | active | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0001-T01 | done | — | workplans/REUSE-WP-0001-statehub-bootstrap.md | +| task | REUSE-WP-0001-T02 | done | — | workplans/REUSE-WP-0001-statehub-bootstrap.md | +| task | REUSE-WP-0001-T03 | done | — | workplans/REUSE-WP-0001-statehub-bootstrap.md | +| task | REUSE-WP-0002-T01 | done | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| task | REUSE-WP-0002-T02 | done | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| task | REUSE-WP-0002-T03 | done | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| task | REUSE-WP-0002-T04 | done | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| task | REUSE-WP-0002-T05 | done | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| task | REUSE-WP-0002-T06 | done | — | workplans/REUSE-WP-0002-mvp-registry-foundation.md | +| task | REUSE-WP-0003-T01 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T02 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T03 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T04 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T05 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T06 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T07 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0003-T08 | done | — | workplans/REUSE-WP-0003-intent-scope-gap-closure.md | +| task | REUSE-WP-0004-T01 | done | — | workplans/REUSE-WP-0004-registry-hardening.md | +| task | REUSE-WP-0004-T02 | done | — | workplans/REUSE-WP-0004-registry-hardening.md | +| task | REUSE-WP-0004-T03 | done | — | workplans/REUSE-WP-0004-registry-hardening.md | +| task | REUSE-WP-0004-T04 | done | — | workplans/REUSE-WP-0004-registry-hardening.md | +| task | REUSE-WP-0005-T01 | done | — | workplans/REUSE-WP-0005-registry-federation.md | +| task | REUSE-WP-0005-T02 | done | — | workplans/REUSE-WP-0005-registry-federation.md | +| task | REUSE-WP-0005-T03 | done | — | workplans/REUSE-WP-0005-registry-federation.md | +| task | REUSE-WP-0005-T04 | done | — | workplans/REUSE-WP-0005-registry-federation.md | +| task | REUSE-WP-0005-T05 | done | — | workplans/REUSE-WP-0005-registry-federation.md | +| task | REUSE-WP-0006-T01 | done | — | workplans/REUSE-WP-0006-registry-hygiene-and-coverage.md | +| task | REUSE-WP-0006-T02 | done | — | workplans/REUSE-WP-0006-registry-hygiene-and-coverage.md | +| task | REUSE-WP-0006-T03 | done | — | workplans/REUSE-WP-0006-registry-hygiene-and-coverage.md | +| task | REUSE-WP-0006-T04 | done | — | workplans/REUSE-WP-0006-registry-hygiene-and-coverage.md | +| task | REUSE-WP-0007-T01 | done | — | workplans/REUSE-WP-0007-interactive-catalog.md | +| task | REUSE-WP-0007-T02 | done | — | workplans/REUSE-WP-0007-interactive-catalog.md | +| task | REUSE-WP-0007-T03 | done | — | workplans/REUSE-WP-0007-interactive-catalog.md | +| task | REUSE-WP-0008-T01 | done | — | workplans/REUSE-WP-0008-graph-explorer.md | +| task | REUSE-WP-0008-T02 | done | — | workplans/REUSE-WP-0008-graph-explorer.md | +| task | REUSE-WP-0009-T01 | done | — | workplans/REUSE-WP-0009-cli-hardening.md | +| task | REUSE-WP-0009-T02 | done | — | workplans/REUSE-WP-0009-cli-hardening.md | +| task | REUSE-WP-0009-T03 | done | — | workplans/REUSE-WP-0009-cli-hardening.md | +| task | REUSE-WP-0010-T01 | done | — | workplans/REUSE-WP-0010-network-federation.md | +| task | REUSE-WP-0010-T02 | done | — | workplans/REUSE-WP-0010-network-federation.md | +| task | REUSE-WP-0010-T03 | done | — | workplans/REUSE-WP-0010-network-federation.md | +| task | REUSE-WP-0016-T01 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T02 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T03 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T04 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T05 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T06 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T07 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T08 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0016-T09 | done | — | workplans/REUSE-WP-0016-interactive-registry-maintain.md | +| task | REUSE-WP-0020-T01 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T02 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T03 | todo | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T04 | wait | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T05 | todo | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T06 | todo | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T07 | todo | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | +| task | REUSE-WP-0020-T08 | done | — | workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md | diff --git a/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md b/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md index 5175872..c5d7e8d 100644 --- a/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md +++ b/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md @@ -119,18 +119,31 @@ raising. ```task id: REUSE-WP-0020-T03 -status: todo +status: wait priority: medium ``` -Cross-repo, in `~/evidence-binder`. Both entries in -`registry/indexes/capabilities.yaml` ("Evidence-to-target binding", -"Visual-guide rect registry") lack the required `id`. Add ids consistent with -the registry naming convention, confirm against `schemas/capability.schema.yaml`, -and check whether `registry/capabilities/*.md` entries exist behind them or -whether the index rows are orphans. +Cross-repo, in `~/evidence-binder`. **Routed 2026-08-20**, not edited directly — +that repo is active (last commit 2026-07-30) and has its own identity and topic. -Route rather than edit directly if that repo has an owning agent. +The defect is larger than the missing `id`. Both rows use an entirely +non-conforming shape — `type` / `title` / `description` / `keywords` instead of +`id` / `name` / `summary` / `vector` / `domain` / `status` / `owner` / `path` / +`tags` / `consumption_modes`. History shows `597b489` added the +REUSE-WP-0014-T04 scaffold and then `a10f080` ("Extract binder package from +citation-evidence") hand-wrote these two rows around it. `registry/capabilities/` +is empty, so both index rows are orphans with no backing entry Markdown. + +Left to that repo's owner because the remaining judgment is theirs: reshaping +the rows is mechanical, but assigning D/A/C/R maturity vectors is an assessment +of their own delivery state, and invented values would be wrong in a way that is +hard to notice later. The message offers `capabilities: []` as an honest +alternative — ten other federation members sit at count 0 — and offers to do the +work here if they supply vectors or accept a conservative `D1/A0/C0/R0` +placeholder marked for review. + +Suggested ids: `capability.evidence.binding`, +`capability.evidence.rect-registry`. ## Re-Enable The evidence-binder Source @@ -148,7 +161,7 @@ hardened, re-enable and confirm `/v1/federated` returns 61 sources. ```task id: REUSE-WP-0020-T05 -status: todo +status: progress priority: high ``` @@ -170,21 +183,33 @@ Deadline-bound: must land before **2026-08-31**. 2. Bump `image.tag` in `railiance-apps/helm/reuse-surface-values.yaml` from `e3ae22e` to a verified Forgejo tag. - **Prefer a build of current HEAD over `main-f9d957a`.** T02's compose - hardening is not in `main-f9d957a`, and without it re-enabling - `evidence-binder` (T04) would take production to HTTP 500 again. Pushing - HEAD touches `reuse_surface/**`, so CI will produce `main-`; - deploy that tag. Not pushed yet — pushing to the shared remote needs an - explicit go-ahead. + **Done 2026-08-20** — `railiance-apps@029460d` pins `main-b035664`, verified + to resolve (manifest `200`). CI built it after `fix-consistency` pushed the + T02/T08 commits. It carries the compose hardening, which `main-f9d957a` does + not: without it, re-enabling `evidence-binder` (T04) would take production + back to HTTP 500. - Left deliberately unmodified for now: writing a tag that has not been built - is worse than leaving the current wrong one, since it converts a latent - failure into an immediate one on the next reconcile. -3. Correct `docs/deploy/reuse-kubernetes.md`, which still describes Gitea as - the live registry and its manual `docker build`/`push` commands still - target `gitea.coulomb.social`. -4. Apply from a host with cluster access; verify rollout, `/v1/federated`, - and that the PVC at `/data` survived. + Committed but **not applied**. `railiance-apps` has no ArgoCD or Flux + controller, so a commit there deploys nothing — `make reuse-deploy` is a + manual `helm upgrade` requiring `REUSE_KUBECONFIG` for Railiance01. +3. ~~Correct `docs/deploy/reuse-kubernetes.md`.~~ **Done 2026-08-20** (`b035664`). +4. **Remaining.** Apply from a host with cluster access — the workstation + kubeconfig points at `127.0.0.1:16443` and needs an ops-bridge tunnel: + + ```bash + make reuse-dry-run # helm template, no apply + make reuse-deploy # helm upgrade --install --wait + make reuse-status # pods, svc, ingress, pvc, certificate + curl -s https://reuse.coulomb.social/v1/federated | head -c 300 + curl -s https://reuse.coulomb.social/v1/reuse-events # 404 today; 200 proves T04/T05 shipped + ``` + + Confirm the PVC at `/data` survived, since `reuse.db` and the remote index + cache live there. + + **`make reuse-smoke` will fail** — it runs `curl -fsS $(REUSE_URL)/health`, + and `/health` returns nginx `404` through the ingress (see T06). Fix that + first or expect a false negative on an otherwise good deploy. Ships REUSE-WP-0019 **T04/T05/T06** as a side effect — telemetry store, R-axis aggregation, and hub freshness monitoring were closed as finished but