Track G: Operations

Track G focuses on running ArcFlow in production-like local conditions: schema migrations, readiness probes, trace export, and idempotent re-migration. No application workflow authoring required.

Goal

Apply migrations, verify /ready, export trace via CLI, and confirm idempotent re-migration. Operator-focused tasks rather than SDK development.

Prerequisites

Item	Required
Docker Compose	Server stack
Rust toolchain	For `arcflow-cli` from repo root
Prior reading	Track B for server basics
Guides	execution traces, Trace data policy rules

Step 1: Start stack with migrate job

bash

docker compose -f docker/docker-compose.server.yml up -d --build

Compose runs arcflow-migrate before arcflow-server starts. Confirm migrate container exited successfully:

bash

docker compose -f docker/docker-compose.server.yml logs arcflow-migrate

Step 2: Verify readiness

bash

curl -sf http://localhost:8080/health
curl -s -o /dev/null -w "%{http_code}\n" http://localhost:8080/ready

Expect /ready 200 when Postgres is reachable and schema is at head. 503 indicates degraded state; do not route production traffic.

Document result:

ready_http_code=200

Step 3: Create a run for trace export

Use Track B payload or quick curl create. Copy run_id after Completed.

bash

curl -s -X POST http://localhost:8080/v1/runs \
 -H "Content-Type: application/json" \
 -H "Authorization: Bearer dev-secret" \
 -d @run-payload.json

Step 4: Export trace via CLI

bash

cargo run -p arcflow-cli -- trace YOUR_RUN_ID --format json --verbose

Compare CLI output to HTTP trace:

bash

curl -s "http://localhost:8080/v1/runs/YOUR_RUN_ID/trace" \
 -H "Authorization: Bearer dev-secret"

Pass criteria: both exports list lifecycle events; no prompt text or secrets in JSON (trace data policy).

Step 5: Idempotent re-migration

Run migrate again explicitly:

bash

cargo run -p arcflow-cli -- migrate up

Or restart migrate service:

bash

docker compose -f docker/docker-compose.server.yml run --rm arcflow-migrate

Second run should exit zero with no pending migrations. Schema version remains at head; no duplicate object errors.

Verify /ready still 200 after re-migration.

Verification checklist

Check	Expected
First migrate	Success, server starts
`/ready`	200 at head
CLI trace	JSON with event kinds
HTTP trace	Consistent with CLI for server runs
Second migrate	Idempotent, no failures
Trace policy	No raw prompts in export

Expected output

Migrate logs show applied revisions once. CLI trace prints indented JSON event array. Re-migrate prints already at head or equivalent no-op message.

Troubleshooting

Symptom	Likely cause	Fix
`/ready` 503	Postgres down or migrate failed	Inspect logs; restart postgres service
CLI trace not found	Wrong id or local-only SDK run	Use server-persisted run id from POST
Migrate conflict	Manual schema edit	Restore from backup; never patch prod schema by hand
Secrets in trace	Misconfiguration	Escalate; traces must stay metadata-only

What you learned

Track G covers operational contracts operators rely on daily: migration idempotency, readiness gating, and auditable trace export without leaking user content.

Next tracks

Track	Focus
H	IDE graph view and local CLI runs
Level 3 cert	Production deployment and token rotation

Stop stack when done:

bash

docker compose -f docker/docker-compose.server.yml down