feat: keep what agents deliver, build on it by reference, in object storage (ADR-0004) #1
Reference in New Issue
Block a user
Delete Branch "docs/handoff-run"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The Orchestration engine keeps what agents deliver and serves it at signed links (ADR-0004), lets a request build on kept work by reference, and keeps it in S3-compatible object storage. Four stacked commits: the delivery store,
sources_from, object storage, and the record of the first run with real models.execution_engine/is unchanged: no agent's behaviour changes.Evidence
mainhas the tests of option 1 (tests/orchestration/test_document.py), 7 failing: the one-document delivery was never implemented.After: they are replaced by
test_links.py,test_store.py(every store test on both a folder and S3 via moto) andtest_sources_from.py; 606 tests pass,ruffandmypyclean.architecture_and_operating_modelrequest: the solution architecture agent's Execution completed in about 50 minutes, its 15 files were kept in MinIO and given to the operating model agent assources, which completed; 74.9 minutes end to end; both Executions fetched back through their links.Merge Danger
Door: two-way
Revert restores relaying without keeping. What has been kept in a store stays there, unread, until removed.
Blast Radius: Orchestration-engine
A deployment needs a volume or a bucket (
STORE_BACKEND,STORE_DIRorS3_*), aPUBLIC_URLa browser reaches, and aLINK_SECRET; without the secret, links stop working on restart. Kept files name what a Customer case's agents delivered, so the store's access matters (signed links only today). ADR-0003 is stillproposed.🤖 Generated with Claude Code