Watch code move without authority moving with it.

This toy workflow shows one way to evaluate generated PTC-Lisp across environments with different code, data, tools, and permissions. It is an example of the runtime primitives, not a required architecture.

Runtime choreography

One workflow, three bounded missions

Step 1 of 7
Generated code may fail · authority stays bounded

Workflow environment

Host-authored sequencerChooses which mission evaluates next. It carries no mission-only tools or namespaces.

Browser mission

Evaluate parser programsHas web tools, but no model or filesystem authority.

Evidence missionevidence.clj

Turn failure into contextSees bounded HTML, old selectors, and the empty result.

Artifact missionartifact.clj

Store parser sourceCan read and write two root-level .clj files, but cannot browse.

MCP serverptc-web

ModelSelector recipe

MCP serverptc-fs-mcp

Look for an accepted parserThe workflow asks the artifact mission to read accepted.clj. On the first run, it is not there.

PTC-Lisp evaluatedquery.clj → browser mission

Evaluation resultreturned to workflow