Tutorial

Why PGS Exists Traditional systems: embed behavior in code are difficult to audit and reproduce require changes across multiple layers PGS: declares behavior in protocol artifacts compiles it into an execution graph executes deterministically with a full trace This onboarding shows how to work within that model. 1. What You Already Did If you followed the pgs_workspace README, you ran this: ./scripts/bootstrap_pgs.sh source .venv/bin/activate ./scripts/demo_sample_workflow.sh You saw a workflow execute twice. The first run registered an actor. The second run produced ALREADY_EXISTS on one node — and still wrote to the event stream. You examined a trace. ...

Author: Bhash Ganti (Bachi) Goal: Teach PGS by building something real, not by describing an abstraction. Before You Start This document assumes you have run the bootstrap and seen at least one workflow execute. You do not need to understand everything yet — that is the point of an example. We will build a complete domain from scratch, following the same steps used to build the actual collatz_conjecture domain in pgs_ai_governance. By the end, you will understand how a real spec becomes a running, traceable, transport-accessible PGS domain. ...