Implementations

PAA in practice

Implementations and case studies are added as they meet the citation bar: a citable artifact mapping the system's interfaces to PAA primitives. The entry below is the first.

Reference implementation

jig

Reference implementation

Minimal agent framework. Six interfaces, two execution models, everything swappable. jig independently converged on the same structural choices PAA names — bounded substrates, typed result envelopes, a separate evidence log, a pluggable verdict producer — without being designed to PAA. That independent convergence is the point: the primitives are real, not invented for the spec.

jig is a reference implementation, not the implementation. It demonstrates that PAA's primitives have a natural home in a minimal framework. Other systems may converge differently and appear here as they publish their own mapping artifacts.

AgentResult, PipelineResult Boundary result envelopes (Stage 1)

run_agent, run_pipeline Bounded execution substrates (Stage 1)

Step Subtask boundary (Stage 1)

TracingLogger Evidence log substrate (Stage 2)

Grader Evaluator technique interface (Stage 3)

FeedbackLoop Accumulated verdict storage and eval export (Stage 5, 8)

eval/calibration.py, judge_variants.py Evaluator maturation, distillation ladder (Stage 8)

(no Boundary object) PAA Boundary: implicit in AgentConfig shape and result envelopes

(no Gate object) PAA Gate: not in scope; jig does not manage gate position

(no PromotionRule / DemotionRule) PAA promotion and demotion: not in scope; jig accumulates evidence but implements no transition logic

jig on GitHub PAA mapping doc

Citation bar

An entry appears here when it meets two conditions: a public codebase or artifact, and a mapping document that traces the system's interfaces to PAA primitives — including honest non-matches.

Independent convergence is stronger than retrofit. The mapping document does not need to show perfect alignment; it needs to show that the author looked and reported what they found. Loose rows and honest non-matches are evidence of integrity, not weakness.

Case studies and domain implementations follow the same bar: a citable writeup showing where PAA primitives appear in a production system, with the evidence log and gate decisions as the proof artifacts. Empty cells in the lifecycle coverage matrix are the content calendar.