Blueprint Gallery
Reusable BarkBowl blueprints help teams write clearer feature, incident, claim-boundary, and handoff notes. Each blueprint is a starting point that still needs human review.
Blueprint Gallery
Purpose: Use before a “tiny” feature enters the bowl.
When not to use: Do not use as approval. Requires owner, non-goals, and acceptance criteria.
Related snack: Feature Kibble
Related lesson: Tiny Features Grow Teeth
Evidence required: Acceptance Criteria, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use after a route, cart, or REST failure produces evidence.
When not to use: Do not use to close an incident automatically.
Related snack: Incident Snacks
Related lesson: Incidents Cost More Than the Fix
Evidence required: Telemetry, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use when another agent or human continues the release.
When not to use: Do not use as memory continuity proof.
Related snack: UAIX Handoff Chews
Related lesson: Handoffs Need Receipts
Evidence required: UAIX Memory, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use when copy wants to claim proof, safety, or authority.
When not to use: Do not use to widen claims without review.
Related snack: Claim Boundary Dental Stick
Related lesson: Autonomy-Washing: Claims That Need a Muzzle
Evidence required: Claim Boundary, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use when theme, plugin, docs, checksum, and public diagnostics must agree.
When not to use: Do not ship with mismatched WordPress headers.
Related snack: Version Parity Kibble
Related lesson: Evidence Dashboard Literacy
Evidence required: Version Parity, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use when the safest action is preserving state.
When not to use: Do not hide uncertainty; explain it.
Related snack: No-Op Senior Blend
Related lesson: No-Op Is a Feature
Evidence required: No-Op Dominance, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use to verify expiry, recovery, and telemetry.
When not to use: Do not silently extend TTL during read-only page views.
Related snack: TTL Timeout Treats
Related lesson: Fail-Forward Dogfood Loops
Evidence required: TTL, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]
Purpose: Use when duplicate or inconsistent terms appear.
When not to use: Do not delete useful concepts without redirecting meaning.
Related snack: Glossary Drift Biscuits
Related lesson: Filter Overload Is a Product Smell
Evidence required: Semantic Drift, owner, timestamp UTC, and review outcome.
Decision: [draft]\nEvidence: [link]\nBoundary: [what this does not prove]\nOwner: [human]\nReviewed at UTC: [timestamp]