The Zero-Paste Workflow: Letting Your Harness Pull Only the Contract Card It Needs

A complete blueprint for running a zero-paste engineering session where discovery, selection, materialization, and verification run through typed edges without touching the system clipboard.

In a zero-paste engineering workflow, the developer states the assignment, constraints, and acceptance criteria once in a structured task file or prompt, and never copies documentation or stack traces by hand again. The harness executes four separated stages:

• Effect-free card discovery: Queries the capability index (getagentfoundry.si / foundry.baltor.ai) and retrieves < 2 KB contract cards matching the task's input and output types.
• Graph composition and engine slot binding: Orders the selected capability cards into a Solution graph and binds each functional edge to its highest-ranked qualified engine in engine_slots.yaml.
• Lazy source materialization: Pulls pinned source bytes only for the vertices that need execution or adaptation, keeping unchanged components locked.
• Automated counterexample verification: Runs verifier.py directly against the candidate output and feeds any counterexample receipt straight back to the Loop until the exit condition is met or the call budget is reached.

# Zero-Paste Task Specification (WORKFLOW.yaml)
schema_version: baltor.workflow.v1
task_id: fluted_ceramic_relief_vessel
model_binding: gemma4:31b
call_budget_ceiling: 6
required_contract_cards:
  - creative.mesh.lathe_harmonic_relief.v1
  - creative.mesh.manifold_repair.v1
  - studio.lighting.four_pass_pbr.v1
verification_gate:
  script: verifier.py
  require_independent_verifier: true
  invariants:
    - watertight_2_manifold == true
    - boundary_edges == 0
    - luminance_contrast_ratio >= 4.8

By replacing manual copy-paste loops with declared contract cards and independent verifiers, every finished task leaves behind a reproducible run record and a reusable component graph.