The Workshop

How one unit of work flows through the stack

Every arrow is machine-checked. The worker never grades itself, the receipt outlives every vendor, and nothing reaches production on an agent's word alone.

The run, blow by blow

"contract": {
  "definition_of_done": "GET /api/uptime returns 200 JSON {up:true, uptimeSeconds}; GET /api/version
                         returns 200 JSON {version} matching package.json. Each has a node --test case.",
  "acceptance_tests": ["uptime endpoint answers with up===true",
                       "version endpoint matches package.json version"],   // immutable
  "constraints": ["touch only app/server.mjs and test/", "no new dependencies"],
  "autonomy_ceiling": 0                                                    // propose — never commit
},
"budget": { "max_worker_runs": 8, "max_wall_seconds": 1800 }

[17:15:54] driver up — mode=propose (operator asked propose)
[17:15:54] -> job-001 (attempt 1): add GET /api/uptime + node:test case …
[17:16:46]    ok  verified.                       ← npm test, run by the driver: 52s
[17:16:48] -> job-002 (attempt 1): add GET /api/version + node:test case …
[17:18:00]    ok  verified.                       ← 72s
[17:18:02] GOAL COMPLETE — 2 tasks, 0 blocked/surfaced.

{
  "subject":   "did:web:frontierinfra.org:stack-demo-worker",   // who did the work
  "task":      { "id": "job-001", "claim": "add GET /api/uptime …" },
  "verdict":   "verified",                                      // the verifier's finding
  "ground_truth": "confirmed",                                  // checked against reality
  "checks":    [{ "query": "npm test",
                  "response_sha256": "d0d1c1…",                 // evidence, committed by hash
                  "excerpt": "ok 6 - uptime endpoint answers…" }],
  "verifier":  { "id": "did:web:frontierinfra.org:machine-driver-verify" },  // ≠ subject
  "sig":       { "alg": "Ed25519", "by": "did:web:frontierinfra.org" }       // ← your key, your domain
}

"checks": [
  { "name": "`npm test` passes (incl. workforce-built endpoints)", "passed": true },
  { "name": "job-001 AAR verifies (signature + evidence)",          "passed": true },
  { "name": "job-002 AAR verifies (signature + evidence)",          "passed": true }
],
"signed_off": true

PR INTAKE CHECK: FAIL
- PR must name the smallest regression guardrail or explain why none was added.
- PR must include human verification details.
                                    ← fixed the body; fresh run green; merged.

What broke, honestly

Two things broke, honestly. The driver's signing step failed on a relative key path — and instead of a silent skip, it alerted loudly, left the unsigned records intact for later signing, and the root cause was fixed upstream the next day with regression tests (relative paths now anchor to the goal file, and a missing key names its full resolved path). The second break was the intake gate above. Demos that never break prove nothing; this one broke twice and recovered with the audit trail to show it.

[17:16:46] ALERT: AAR sign FAILED for task job-001 (rc 1):
           error: ENOENT: no such file or directory, open 'secrets/stack-demo.jwk.json'

Every tier, with its receipt

Don't take our word for it

The point of the stack is that you never have to trust the operator — or us. Fetch a receipt from the live board and check the signature against the key published on this domain:

# fetch a receipt from the live board, verify it against this domain's published key
curl -sO https://workshop.frontierinfra.org/receipts/aar-job-001.json
git clone https://github.com/frontier-infra/agentcontrolplane
node agentcontrolplane/tools/aar.mjs verify aar-job-001.json
# → [✓] L0: Ed25519 signature valid … → conformance: L2

What happened next: the seam became a product

The day after the run, the proof→receipt bridge was productized into Proctor itself: every contract signed off on a key-configured machine now auto-emits a signed attestation — verify, judge, or operator sign-off alike. The change went through a 15-agent adversarial review workflow before it shipped, which caught two real defects the tests had missed (a Python 3.9 incompatibility that would have silently disabled emission on stock macOS, and a path-traversal through hostile contract ids) — both reproduced, fixed, and regression-tested. The spec section it conforms to (ADL contract & proof, §7) now has two independent, interoperating producers: machine-driver and Proctor. That is how a record format stops being a feature and starts being a standard.

What this is not

What this is not: the attestations are same-principal (we verified our own workers — disclosed in every record, useful for provenance, not audit-grade independence); the run was demo-scale (two small tasks, one machine); and the workforce ran in propose mode with a human landing the merge. Each of those is a dial the stack exposes, not a ceiling it hides.

← Frontier Infra home · agents: this page is readable at /workshop.agent