tegwick
cdd5cef373
The first implementation took local filesystem paths. Central has no workstation checkout and must not depend on one: ADR-012 decision 1 makes the forge the projection source, and a backfill reading someone's laptop would reintroduce the exact coupling that ADR removes. Surfaced concretely — central's postgres is not reachable from the workstation (only the API tunnel, which is HTTP), so the local-path variant cannot reach the database it needs to update, while the pod can clone the forge and already holds the connection. A repository that cannot be cloned contributes nothing rather than reducing what the rest can identify. Refs STATE-WP-0083-T06 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006 |
||
|---|---|---|
| .. | ||
| edge | ||
| events | ||
| models | ||
| routers | ||
| schemas | ||
| services | ||
| classification.py | ||
| config.py | ||
| database.py | ||
| doi_engine.py | ||
| flow_defs.py | ||
| main.py | ||
| task_status.py | ||
| workplan_status.py | ||