Merge pull request #2 from operatorstack/sync/intelligence-flow-fcc2faa55ac3

Sync Boatstack from Intelligence Flow fcc2faa55ac3

Author: bigboateng

CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 # Contributing
 
-Boatstack is a generated distribution. Propose changes to workflow semantics, templates, evidence rules, or generated presentation in [Intelligence Flow](https://github.com/operatorstack/intelligence-flow/tree/aae685d2513cd25537284e4e68177411ace7ac9a/examples/12-product-engineering-loop).
+Boatstack is a generated distribution. Propose changes to workflow semantics, templates, evidence rules, or generated presentation in [Intelligence Flow](https://github.com/operatorstack/intelligence-flow/tree/fcc2faa55ac3c2332ce4a19293d89023f578784d/examples/12-product-engineering-loop).
 
 The Boatstack repository receives those changes through a generated pull request. Review the PR's `UPSTREAM.json`, tests, adapter diff, and context-size change; do not hand-edit generated output on `main`.
 

README.md

@@ -4,7 +4,7 @@
 
 **Plan the route. Prove the work. Ship.**
 
-Boatstack is loop engineering for coding agents: a model-neutral path from a product request to an explicitly approved, tested, reviewed pull request. Its behavior is generated from [Intelligence Flow at `aae685d2513cd25537284e4e68177411ace7ac9a`](https://github.com/operatorstack/intelligence-flow/tree/aae685d2513cd25537284e4e68177411ace7ac9a/examples/12-product-engineering-loop).
+Boatstack is loop engineering for coding agents: a model-neutral path from a product request to an explicitly approved, tested, reviewed pull request. Its behavior is generated from [Intelligence Flow at `fcc2faa55ac3c2332ce4a19293d89023f578784d`](https://github.com/operatorstack/intelligence-flow/tree/fcc2faa55ac3c2332ce4a19293d89023f578784d/examples/12-product-engineering-loop).
 
 It is not a claim that a longer prompt writes better code. Here is what the loop actually does.
 
@@ -73,6 +73,26 @@ That is the approval boundary in code: conversation cannot silently turn a draft
 
 See the complete, linked [worked example](examples/diagram-json/README.md).
 
+## Bring your own product context
+
+Boatstack does not impose a documentation structure or maintain a second product memory. Keep feature briefs, vision, roadmaps, ADRs, gaps, and engineering rules wherever they already live in the repository. Cursor, Codex, or Claude discovers the relevant surrounding code and documents; Boatstack controls how that context becomes an approved change.
+
+Point the host at an existing product document:
+
+```text
+/auto-plan Build team notification preferences.
+Product brief: docs/features/team-notifications.md
+Relevant decisions: docs/architecture/notifications.md
+```
+
+Or begin with only the request and let the host inspect the smallest relevant repository slice. Boatstack separates discoverable facts from product questions, then produces the consistent handoff:
+
+```text
+existing product docs + code -> questions -> feature spec -> approval -> engineering plan
+```
+
+Product documents define what and why. ADRs record durable technical decisions. Gaps record known incomplete work. Boatstack references these sources without rewriting them. No context map or documentation migration is required in V1; the project config may list useful starting paths when a repository wants stable defaults.
+
 ## Install into a repository
 
 ```bash

UPSTREAM.json

@@ -13,8 +13,8 @@
     ".github/workflows/ci.yml": "9480a65a3a4d24b42f7854566ad4a55100b7f2c2b25bffc6bb6b368ba0848104",
     ".github/workflows/sync-upstream.yml": "f8c84e316e296ac5928bc0222cef64848ea0fda6846a42f540b0747e8c4eb5f7",
     ".gitignore": "94fa252979321511b0ce5fa598f71905f6dc29c5bef6660ff4498a5a39c167ba",
-    "CONTRIBUTING.md": "217090f78f44da12890d7ad4aa555f1233c64bfe2119877d497e7c13fb4b3f91",
-    "README.md": "adc08d8b50f731f5f9336bc4eaca3ce0a4ebb64c75e94aa6e6f0dabfe26e028c",
+    "CONTRIBUTING.md": "125729f68cbf129ce27a72973d7c633ae04cf8159a39ebeaaed98a2d3d13a40c",
+    "README.md": "8262db68e8217f4c367fbc4b2575e235ee0e57651d4e169265b27fa855bc4c7e",
     "boatstack/SKILL.md": "335731973cea2c5d0eb67b9d3870cc332490d1188e3943bb185ab78ab4b4b886",
     "boatstack/agents/openai.yaml": "8429c65868025e798d345cc2a9bd78f2bc3280ee982f8f7874504395d6d68368",
     "boatstack/assets/templates/adr.md": "c577a3c1c1319061f61deb053597e6e853657022185fe28b8f733327e2a78565",
@@ -35,14 +35,14 @@
     "boatstack/scripts/export_repo.py": "42444369b2b4d8430b5347761626ac7725aae25aa4726b5bdca5325a4fc80ad0",
     "docs/benchmark-corpus-audit.md": "f2d206fe8579a514f9da82b2c96c19b343ac004be67617e1bd34f0f8e0e5e6c6",
     "docs/benchmark-submission-audit.md": "9518abdd17690729c6423f87cab20418ed47b0915b5faa44b9ef975e9e9c3b79",
-    "docs/loop-engineering.md": "2cddb0aa963f15149c69102a8215401d32848d228acbf55c3df20db27b654a34",
+    "docs/loop-engineering.md": "63b114e57c129379757a57938e33abb2da21eed3fef19c1731dba22ea58b5baf",
     "docs/research-and-design.md": "543836387090f8dc01381b1e46d1c6760bcbf8119b4004ece8d6f6f68d08db4f",
     "examples/diagram-json/README.md": "51871b16438cbef2bbdf5077dda0b5b06e77cbe76882d34e4a05c17c8f13a2b3",
     "examples/diagram-json/compiled/evidence.md": "1ba1c989ade070a8ef9a508fbd788d100d7292f2dbacbb2bce895468019f619d",
     "examples/diagram-json/compiled/tasks.json": "d66d693df1ba7dd34f65ce93afea54006563c14d642a1bf0d1d9311b3fcfb37b",
     "examples/diagram-json/compiled/test-matrix.json": "0497cf73f84515cfc493e4904eda4c2be6c0621fc0a11a3b1349803b5acf91cb",
     "examples/diagram-json/plan.json": "d1208003042a9d10f5efb010fc32fc7ac7bdefa427938260586e90daa0cb4414",
-    "examples/diagram-json/plan.lock.json": "e6f5a6a7d3898eacaeacb1f38d84f34b6c7bee25b1d1eb79cb7ca3157cb897ea",
+    "examples/diagram-json/plan.lock.json": "3e0bb70807c5a06dd7ac7a87c691a19abfc2e27131754830fe1d32b365a20bba",
     "examples/diagram-json/questions.md": "1a0050041cac0a8d53e6ebfe04cbec4a298cdc8c50efeeb6fa15aeb663c5ec76",
     "examples/diagram-json/request.md": "0808fc41c36779c404f4a3a121167da6e76cac56df526e70f9ed6d3e0d4c02ed",
     "examples/diagram-json/spec.md": "a943c81cf2a88d23d5b300e6b9dc1dafc80923a9b6b9ab5297a67b4e2054b9d5",
@@ -52,7 +52,7 @@
   "generator": "operatorstack/intelligence-flow:boatstack-distribution",
   "schema_version": 1,
   "source": {
-    "commit": "aae685d2513cd25537284e4e68177411ace7ac9a",
+    "commit": "fcc2faa55ac3c2332ce4a19293d89023f578784d",
     "path": "examples/12-product-engineering-loop",
     "repository": "operatorstack/intelligence-flow"
   }

docs/loop-engineering.md

@@ -87,6 +87,6 @@ A failed task can suggest a better move, but one anecdote cannot silently rewrit
 
 ## What is evidence-backed
 
-The current moves were derived from the Intelligence Flow benchmark corpus and product-repository studies. The generated source commit is [`aae685d2513cd25537284e4e68177411ace7ac9a`](https://github.com/operatorstack/intelligence-flow/tree/aae685d2513cd25537284e4e68177411ace7ac9a/examples/12-product-engineering-loop).
+The current moves were derived from the Intelligence Flow benchmark corpus and product-repository studies. The generated source commit is [`fcc2faa55ac3c2332ce4a19293d89023f578784d`](https://github.com/operatorstack/intelligence-flow/tree/fcc2faa55ac3c2332ce4a19293d89023f578784d/examples/12-product-engineering-loop).
 
 The evidence supports specific failure mechanisms and guardrails. It does not establish that Boatstack is optimal, that control-theory notation proves software quality, or that one workflow dominates every team. Those are evaluation questions, so the distribution preserves measurements, provenance, gaps, and negative results.

examples/diagram-json/plan.lock.json

@@ -6,7 +6,7 @@
   "plan_path": "examples/diagram-json/plan.json",
   "plan_sha256": "d1208003042a9d10f5efb010fc32fc7ac7bdefa427938260586e90daa0cb4414",
   "schema_version": 1,
-  "source_commit": "aae685d2513cd25537284e4e68177411ace7ac9a",
+  "source_commit": "fcc2faa55ac3c2332ce4a19293d89023f578784d",
   "spec_path": "examples/diagram-json/spec.md",
   "spec_sha256": "a943c81cf2a88d23d5b300e6b9dc1dafc80923a9b6b9ab5297a67b4e2054b9d5",
   "status": "APPROVED",