Files
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

1.3 KiB

Plans

One directory per iteration. Each holds the plan for that iteration and, for finished steps, the record of what was built.

Iterations

# Directory Status What it is
1 iter-01-execution-engine/ steps 1 to 6 built on 2026-10-13; 7 planned The Execution engine: brought from the Reference, given a Workflow, and proved on a toy Workflow and on the Reference's own.
2 iter-02-orchestration-engine/ F1 proposed; F2 and F4 built on 2026-10-20; K1, K2 and K3's object storage (ADR-0004) built on 2026-10-21 The Orchestration engine: routes each request to the agent for its work and relays everything back.

The plan across both repositories is ../tom_analysis/IMPLEMENTATION_PLAN.md.

Files in an iteration

  • MAP.md: the intent, each step's status, and the sources of truth to read.
  • steps/step-N.md: written when step N is finished. What was built, what differed from the plan, and how it was verified. A step with no file is not done.

Working in an iteration

  1. Read MAP.md and the sources of truth it names.
  2. Build the step until its "done when" holds and pytest, ruff check, ruff format --check and mypy all pass.
  3. Write steps/step-N.md and set the step's status in MAP.md.