{
  "schemaVersion": "1",
  "revision": "22ce5d34dbcb5a78",
  "id": "factory-vision-and-automation",
  "slug": "vision-and-automation",
  "title": "Product vision and earned automation",
  "summary": "Keep product direction durable without freezing implementation, and promote recurring reviews only when their signal earns it.",
  "category": "Team practice",
  "tags": [
    "vision",
    "automation",
    "gates"
  ],
  "sources": [
    {
      "label": "Vision and automation lesson",
      "url": "https://proud-anchor-53zn.here.now/learn.html#q4-vision-automation"
    },
    {
      "label": "Companion lesson",
      "url": "https://proud-anchor-53zn.here.now/learn.html#q4-vision-automation"
    }
  ],
  "sourceUnits": [
    "learn.html#vision-automation-ladder",
    "learn.html#q4-vision-automation"
  ],
  "collection": "factory",
  "categoryId": "team-practice",
  "wordCount": 368,
  "url": "/topics/factory-vision-and-automation/",
  "markdownUrl": "/markdown/factory-vision-and-automation.md?raw=1&v=22ce5d34dbcb5a78",
  "jsonUrl": "/api/v1/documents/factory-vision-and-automation.json",
  "headings": [
    {
      "id": "separate-product-direction-from-operating-instructions",
      "text": "Separate product direction from operating instructions",
      "level": 2
    },
    {
      "id": "keep-automation-at-the-lowest-justified-stage",
      "text": "Keep automation at the lowest justified stage",
      "level": 2
    },
    {
      "id": "operating-practice",
      "text": "Operating practice",
      "level": 2
    },
    {
      "id": "let-vision-guide-automation",
      "text": "Let vision guide automation",
      "level": 3
    },
    {
      "id": "what-to-notice",
      "text": "What to notice",
      "level": 4
    },
    {
      "id": "try-this",
      "text": "Try this",
      "level": 4
    },
    {
      "id": "concept",
      "text": "Concept",
      "level": 4
    },
    {
      "id": "reflection",
      "text": "Reflection",
      "level": 4
    },
    {
      "id": "links-shared-for-this-topic",
      "text": "Links shared for this topic",
      "level": 4
    }
  ],
  "markdown": "# Product vision and earned automation\n\nKeep product direction durable without freezing implementation, and promote recurring reviews only when their signal earns it.\n\n## Separate product direction from operating instructions\n\n`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.\n\nFor 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.\n\n## Keep automation at the lowest justified stage\n\nThe 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.\n\nEvery 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.\n\n## Operating practice\n\n### Let vision guide automation\n\n#### What to notice\n\nKeep code as **implementation truth** while giving agents **durable product direction** and an explicit adherence dial.\n\n#### Try this\n\nDraft VISION.md from product evidence, then mark Preserve, May change, Must ask, and Verification for one task.\n\n> “Code is a source of truth.”\n\nJohn Lindquist · [05:35:33](https://proud-anchor-53zn.here.now/watch.html?t=20133#recording-player)\n\n#### Concept\n\nVision describes the user, outcome, qualities, durable constraints, and open decisions. It should guide improvement without freezing a stale architecture into permanent context.\n\n#### Reflection\n\nVISION.md and AGENTS.md can serve different roles. Do not silently collapse product direction and operating instructions.\n\n**Recording evidence:** listen at 05:25:50.\n\n> “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.”\n\nJohn Lindquist · [05:37:00](https://proud-anchor-53zn.here.now/watch.html?t=20220#recording-player)\n\n#### Links shared for this topic\n\n- [Workshop NotebookLM notebook](https://notebooklm.google.com/notebook/4ae3bcdd-b31b-4e2b-af19-7e6c702c6cc7) — The research notebook and generated artifacts shown near the close.\n- [Handy](https://handy.computer/) — A dictation tool shared during the VISION.md discussion.\n\n[Watch chapter](https://proud-anchor-53zn.here.now/watch.html?t=19550#q4-vision-automation)"
}
