A trustworthy software factory loop

Bound one recurring task, name the consequential action, and earn autonomy with observable evidence.

Bound one recurring task, name the consequential action, and earn autonomy with observable evidence.

The unit of work is a loop, not an agent

A software factory is not a pile of agents. The agent is one machine inside an inspectable loop:

Input → Boundary → Action → Evidence → Decision → Receipt.

Start with one recurring task and one costly failure. Define the minimum context, permission boundary, exact human gate, and success evidence before adding autonomy. A gate is a named stop, named evidence, and explicit approval before a consequential action—not a request to review something eventually.

The operating stages are Bound → Compose → Run → Verify → Preserve → Promote:

  • Bound: state the desired outcome, inputs, exclusions, and the first expensive, destructive, public, or hard-to-reverse action.
  • Compose: gather current, relevant evidence that changes the decision, implementation, or verification; do not equate volume with completeness.
  • Run: execute the smallest reversible experiment inside the agreed permission boundary.
  • Verify: demand the exact observable signal that proves the result; an agent saying “done” is not that signal.
  • Preserve: save the outcome, settled decision, rejection reason, failed attempts, and repeatable check so another session can continue from evidence.
  • Promote: automate only after repeated manual receipts establish that the signal is useful, owned, affordable, and recoverable.

Put each kind of rule in its proper place

Repository files explain stable intent. Launch wrappers normalize repeated choices. Command decorators bring warnings to the moment of action. Human gates protect consequential work. Automated checks prove the condition they actually measure. None substitutes for the others.

Safety is a layered design, not a permission-bypass switch. A shell function that can be bypassed with command is guidance with teeth, not confinement. A stripped prompt context is not a filesystem or network sandbox. A dry run or stub can prove wiring without proving behavior against a real service.

Choose a route by the problem

A complete first pass connects the core boundary audit, environment policy, annotated image, focused context packet, repeatable flow, structural alternatives, independent reasoning, and product vision. A quick start takes the core loop, one visual task, and a small set of alternatives. A problem-led route enters at the current bottleneck:

  • Control and safety: bound the task, place policy near the action, make proof visible.
  • Prompt and context: use visual evidence, compose a focused packet, promote repeated prompts into inspectable flows.
  • Design and taste: expose structural alternatives and preserve why one won.
  • Continuity and debugging: recover trustworthy state and join human testimony to runtime facts.
  • Advanced reasoning and video: escalate a hard decision, not an entire workflow by default.
  • Vision and automation: state durable direction, promote proven signals, and keep unresolved work explicit.

For each topic, move through orientation → concept → evidence → practice → reflection → next action. Copying a prompt, attempting it, and verifying its result are separate states. “Now” establishes the core loop; “Next” makes it repeatable; “Later” adds expensive or specialized capabilities; “Reference” retains unresolved status.

Operating practice

Bound one factory loop

What to notice

Turn one recurring task into an inspectable loop with inputs, permissions, proof, a human gate, and a durable receipt.

Try this

Write Input → Boundary → Action → Evidence → Decision → Receipt for one task you already repeat.

“If the agents can't see it, it doesn't exist.”

John Lindquist · 00:23:25

Concept

A software factory is not a pile of agents. The agent is one machine inside the loop. Start with the smallest reversible bet, then name the exact action that must stop for human approval.

Reflection

A gate is not “review this sometime.” It is a named stop, named evidence, and explicit approval before a consequential action.

Recording evidence: listen at 00:15:52.

“Alignment is the key word here. Is the agent aligned with your vision?”

John Lindquist · 00:32:52

Open How Agentic Work Is Evolving

Watch chapter

Evidence limits that matter

A file appearing, a command running, and a check passing are separate events. Preserve failed attempts instead of upgrading them into success. The environment demonstration surfaced diagnostics, and the recorded MDFlow wrapper exercise did not become a clean success. Those are failure-aware examples, not universal installation proofs.

Tool versions, model names, prices, subscription eligibility, limits, and predictions are contextual claims from the recorded discussion—not current purchasing guidance. Current dotfiles and comparative model-cost guidance remained unresolved. The Markers material is a prepared follow-up, not a dedicated recorded section.

Keep exact published resource links separate from uncertain text read off a screen. A transcript establishes what was said; a recording can reveal visible action; a prepared recipe establishes intended behavior; only the appropriate check establishes success.

Source references