feat: keep what agents deliver and serve it at signed links (ADR-0004)

The Orchestration engine keeps every completed agent Execution it relays,
by tenant, Customer case and Execution, and serves its record and files at
signed, expiring links. A KAB workflow step, which takes one output per
step, is given one JSON document of links (`deliver: links`); other callers
still get each file, and what they are given is kept either way.

- store.py, links.py, delivery.py, serving.py; the relay keeps and links
- the card declares `deliver`, `sources` and an output schema
- image: STORE_DIR on a /data volume; PUBLIC_URL and LINK_SECRET settings
- option 1's tests replaced by tests of the links document

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-21 20:05:47 +01:00
parent ce5e2f20cd
commit 6d32bc696d
17 changed files with 1235 additions and 205 deletions

View File

@@ -4,7 +4,9 @@
# podman build -f Dockerfile.orchestration -t orchestration-engine .
#
# Which agents it routes to is configuration, mounted at /app/agents.yaml
# (AGENTS_FILE); deploy/agents.local.yaml is the local KAB platform's.
# (AGENTS_FILE); deploy/agents.local.yaml is the local KAB platform's. What agents
# deliver is kept in /data/store (ADR-0004); give it a volume, a PUBLIC_URL and a
# LINK_SECRET.
FROM python:3.12-slim AS builder
@@ -21,7 +23,8 @@ ENV PYTHONUNBUFFERED=1 \
PYTHONDONTWRITEBYTECODE=1 \
A2A_HOST=0.0.0.0 \
A2A_PORT=8080 \
AGENTS_FILE=/app/agents.yaml
AGENTS_FILE=/app/agents.yaml \
STORE_DIR=/data/store
WORKDIR /app
@@ -30,8 +33,10 @@ RUN groupadd -g 10001 appgroup && \
COPY --from=builder /install /usr/local
COPY deploy/agents.local.yaml /app/agents.yaml
RUN mkdir -p /data/store && chown -R appuser:appgroup /data
USER appuser
VOLUME ["/data"]
EXPOSE 8080
CMD ["python", "-m", "orchestration.main"]