Boatstack is a generated content distribution. Propose changes to workflow semantics, templates, evidence rules, or generated presentation in Intelligence Flow.
The Boatstack repository receives product/runtime 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. .github/workflows is the exception: it is Boatstack's executable control plane, excluded from scheduled projection and changed only through a separate manually reviewed Boatstack PR.
Repository-specific examples and outcome reports can be proposed upstream as new evidence. A failure becomes a durable move only after its mechanism and non-regression gate are documented.
Any user-facing upgrade must state the user problem, supporting observation or requirement, current evidence status, and the README or guide it changes. If no public document changes, explain why the behavior is internal. Material public claims must appear in docs/public-claims.json and link to a readable explanation.
Every Intelligence Flow change that touches the Boatstack lab must add one release-level Markdown fragment under labs/12-product-engineering-loop/boatstack-distribution/release-notes/. Name it YYYY-MM-DD-<slug>.md, begin with a level-three heading, and describe user impact rather than commits, diffs, or test commands. Fragments are append-only after merge; publish a new correction fragment instead of rewriting history.
Write each fragment in Simplified Technical English, the same standard the README follows. Keep sentences short. Use the active voice and the present tense. State one idea per sentence, put the condition first, and choose the simple, common word. Write for a reader who translates or skims the note.
Use Huashu Design for README and beginner-guide review when it is installed. The portable requirements remain in the public-surface contract: plain outcomes first, one dominant product journey, progressive disclosure, accessible assets, no invented proof, and explicit separation between verified behavior and outcomes still being evaluated.