Handbook
Blueprints as Executable Policy, Not Static Docs
Generated draft. Review source-of-truth ownership, claims, and links before promotion.
Updated
Generated draft. Review source-of-truth ownership, claims, and links before promotion.
Reader Problem
Readers need a human-oriented explanation of 'Blueprints as Executable Policy, Not Static Docs' before they can act on the technical detail.
Outcome
They understand the business meaning, the Forge mechanism, and the next safe step.
Forge Mechanism
Forge Platform connects methodology, contracts, workcells, evidence, and approval boundaries.
Trust Boundary
The hydration agent generates review drafts only; humans choose whether and where to promote them.
Draft Narrative
This methodology draft should only be promoted if the seed introduces reusable process guidance. Keep it prescriptive: define the decision point, the human owner, the artifact that records the decision, and the evidence expected before the next step.
Suggested CTAs
- Map the idea to Forge ceremonies and artifact ownership.
- Check whether the concept belongs in Blueprints before duplicating it elsewhere.
Promotion Notes
- Blueprints is prescriptive framework text; do not add product-specific claims.
- Use relative Markdown links and avoid generated site-only syntax.