Jonathan Boniface 83df77005a feat: keep delivered work in S3-compatible object storage (ADR-0004 phase 3)
The store's rules now sit on a Blobs layer: a folder, as before, or a
prefix in an S3-compatible bucket (MinIO locally), chosen by STORE_BACKEND.
The layout is the same in both; the record is written last.

- S3_BUCKET, S3_PREFIX, S3_ENDPOINT_URL, S3_REGION; AWS credentials
- an s3 extra (boto3), installed in the image; moto for tests
- every store test runs on both kinds of storage

Retention, the platform's sign-in and each kept file as a platform
artifact are left: the last needs the platform's S3 backend, which it does
not yet have.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 21:08:39 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00
2026-10-21 19:50:24 +01:00

Orchestration engine

Two things live here.

  • Execution engine (execution_engine/): the package an agent runs on. It holds one Execution of a Workflow: Deliverables, Phases, Approvals, and the agents that produce them. It knows no subject.
  • Orchestration engine: the service every request comes through, which decides which agent the work belongs to. Not built yet.

Vocabulary is in CONTEXT.md, decisions in docs/adr/, the design in .scratch/engine/spec.md, and what has been built in .agents/plans/.

python3 -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/python -m pytest -q
Description
No description provided
Readme 467 KiB
Languages
Python 100%