---
schema_version: 1
revision: "22ce5d34dbcb5a78"
id: "factory-vision-and-automation"
title: "Product vision and earned automation"
---

# Product vision and earned automation

Keep product direction durable without freezing implementation, and promote recurring reviews only when their signal earns it.

## Separate product direction from operating instructions

`VISION.md` describes the user, intended outcome, product qualities, durable constraints, and open decisions. Code remains implementation truth. `AGENTS.md` can instead describe how an agent operates. Do not silently merge those roles or treat an old architectural diagram as a permanent restriction.

For a concrete task, make adherence explicit: **Preserve / May change / Must ask / Verification**. Strict refactoring constraints and open-ended improvement are different contracts. An agent can improve the architecture without abandoning the product’s end ideal.

## Keep automation at the lowest justified stage

The promotion ladder is **manual run → deterministic script → bounded agent → non-blocking CI report → blocking gate**, with schedules and human approval as deliberate choices rather than inevitable destinations.

Every promotion needs an owner, evidence threshold, false-positive tolerance, latency and cost boundary, stop condition, and recovery path. Collect repeated manual receipts before making a result blocking. General curation and review schedules can become noise; useful on-demand execution is better than automated interruption without a decision to change.

## Operating practice

### Let vision guide automation

#### What to notice

Keep code as **implementation truth** while giving agents **durable product direction** and an explicit adherence dial.

#### Try this

Draft VISION.md from product evidence, then mark Preserve, May change, Must ask, and Verification for one task.

> “Code is a source of truth.”

John Lindquist · [05:35:33](https://proud-anchor-53zn.here.now/watch.html?t=20133#recording-player)

#### Concept

Vision describes the user, outcome, qualities, durable constraints, and open decisions. It should guide improvement without freezing a stale architecture into permanent context.

#### Reflection

VISION.md and AGENTS.md can serve different roles. Do not silently collapse product direction and operating instructions.

**Recording evidence:** listen at 05:25:50.

> “This defines the end ideal of this product. And no matter what the state of the product is in, it can always push more towards that vision.”

John Lindquist · [05:37:00](https://proud-anchor-53zn.here.now/watch.html?t=20220#recording-player)

#### Links shared for this topic

- [Workshop NotebookLM notebook](https://notebooklm.google.com/notebook/4ae3bcdd-b31b-4e2b-af19-7e6c702c6cc7) — The research notebook and generated artifacts shown near the close.
- [Handy](https://handy.computer/) — A dictation tool shared during the VISION.md discussion.

[Watch chapter](https://proud-anchor-53zn.here.now/watch.html?t=19550#q4-vision-automation)

## Original references

- [Vision and automation lesson](https://proud-anchor-53zn.here.now/learn.html#q4-vision-automation)
- [Companion lesson](https://proud-anchor-53zn.here.now/learn.html#q4-vision-automation)
