stage-6-blueprintlisted

Stage 6: the implementation blueprint. The MVP Pack answers **what, why, and where the boundary is**; this stage answers **exactly how, at the product level** — so that "vô số vấn đề phát sinh khi implement" get answered here, with the founder, instead of being invented mid-build by whoever is typing. Output: `blueprint/` beside `mvp-pack/`. Quality bar: the **level-2 cold-start test** — a competent build session reading only pack + blueprint can implement every feature **without inventing any product decision**. Load `method-rules`; read `state.json`; resolve the operating cycle (fragment cycles use `cycles/<id>/blueprint/`). Templates: the `stage-6-blueprint-templates` skill. The BP contract: the **`method-rules-gate-contracts-bp` skill** (a satellite since v1.7.0 — only stage 6, `amend-blueprint` and a BP gate check load it). **Working posture for the whole stage**: the model drafts, the founder decides. Resolution order for every open decision is normative: **(1) pack trace → (2) standing charter rule, cited by item id and replayed at the next checkpoint → (3) ask the founder.** Consulting the charter FIRST matters: it is the declared interpretive authority, and re-asking what the founder already settled is how decision fatigue produces rubber-stamping. Every detail not derivable from the pack starts `[GUESS]`; it is lifted only by founder confirmation (intent), a pack trace (derivation), or an explicit journaled **delegation**, recorded as a row in `blueprint-overview.m