coulomb/ops-mason
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Construction-plan format + first real plan draft (MASON-WP-0001-T01)

Browse source 
docs/construction-plan-format.md: one file per plan (plans/<id>.md),
frontmatter status tracker (draft -> reviewed -> approved -> built ->
catalogued, the phase-4 hard gate), six body sections threading all
four phases through one document.

Proven against real demand: plans/rein-openweights-openrouter-approle.md,
phases 1-2 filled in. Found and reasoned through a real existing-structure
question along the way -- the openrouter-llm-connect catalog lane could
technically be reused, but its auth_method is interactive-caller-shaped
and its policy is shared/high-risk; recommends a dedicated, narrowly
scoped AppRole instead, same reasoning agent-harness-binky-mail used for
its own dedicated lane.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-27 00:47:15 +02:00
parent d3dbad34e1
commit a762be9e17
3 changed files with 219 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

15
workplans/MASON-WP-0001-foundation.md
View file

@ -26,9 +26,22 @@ tear-down, each with a stated reuse-vs-new rationale). Document in
not a database — so a plan can be reviewed in a diff and stored next to
the workplan that requested it.
**Done (2026-07-27).** `docs/construction-plan-format.md`: one file per
plan at `plans/<id>.md`, YAML frontmatter (`status: draft -> reviewed ->
approved -> built -> catalogued`, the phase-4 hard gate), six body
sections (demand, existing-structure survey, proposed changes, phase-2
review notes, phase-3 executive summary, phase-4 build result) — one
document threaded through all four phases, not four separate artifacts.
Proven against a real demand, not a synthetic one:
`plans/rein-openweights-openrouter-approle.md`, phases 1-2 filled in —
including a genuine finding in the existing-structure survey (an
existing `openrouter-llm-connect` catalog lane that could theoretically
be reused, and an explicit, reasoned decision *not* to reuse it, scoped
narrowly instead). Phases 3-4 wait on `MASON-WP-0001-T03`/`T04`/`T05`.
```task
id: MASON-WP-0001-T01
status: todo
status: done
priority: high
state_hub_task_id: "6b25e7ca-52a0-41c2-b5a0-b5e46c824264"
```