Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 153021@bnt-lap001 Assistant-Session: 46917be4-6400-4106-b8b7-61953a0caf24
1.5 KiB
1.5 KiB
Decision records
WEBFETCH-DEC-2026-001 — Approve pushing web-fetcher federation commits to reuse-surface main
id: WEBFETCH-DEC-2026-001
kind: decision
title: Approve pushing web-fetcher federation commits to reuse-surface main
status: prepared
origin: residual
origin_ref: WEBFETCH-WP-0003-T05
owner: web-fetcher
affects:
- web-fetcher
- reuse-surface
requested_dispositions:
- approved
- rejected
created: '2026-10-19T12:40:00Z'
updated: '2026-10-19T12:40:00Z'
state_hub_decision_id: "0cc16212-f983-4da6-972e-a353dbd93164"
Context
capability.infotech.provenance-fetch is already registered with the hosted
reuse-surface service (reuse.coulomb.social, visible in /v1/federated).
The local reuse-surface checkout has two unpushed commits:
be5c006— adds web-fetcher toregistry/federation/sources.yaml.307fcaf— refreshes web-fetcher's row inregistry/indexes/federated.yamlto v0.2.0 (D2 / A3 / C2 / R2). The diff touches only that entry.
Both are fast-forward on origin/main. Pushing to another repo's shared
main is blocked for agents by the permission guard.
Disposition requested
- approved — the founder runs
cd ~/reuse-surface && git push origin main(or allows the agent to), thenWEBFETCH-WP-0003-T05is set todone. - rejected — drop the two commits; the hosted registration stays the only federation path.
Note: the same checkout has someone else's uncommitted changes
(.custodian-brief.md, WORK-RECORDS.md); a push does not include them.