coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
binky-control/DogfoodPolicy.md
tegwick d6d5cf1a1d Add company canon v0 and bootstrap workplan 
Canon: INTENT, CompanyReactivationPlan, EcosystemMap, AutonomyPolicy,
SuccessMilestones, OfferCatalog, DogfoodPolicy, ControlLoopCatalog,
DecisionQueue, OfficeHourQueue, RiskRegister, plus founding exploration
in history/. Workplan BNKY-WP-0001 covers canon ratification, the first
internal audit, ecosystem cartography, flagship offer, and operating rhythm.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 02:48:50 +02:00

1.3 KiB
Raw Blame History

Dogfood Policy

Status: draft v0.1 — 2026-07-16. How internal operations become product evidence. Dogfooding is the metabolism of the OK Flywheel.

Policy

  1. Every internal operational pain is a product signal. Before buying or hand-rolling a one-off solution, check whether an ecosystem capability can solve it (EcosystemMap.md).
  2. Every internal solution is documented as evidence: before/after state, capability used, effort, outcome, reusable pattern, product implication.
  3. The company sells nothing it hasn't run on itself where feasible — the Operational Knowledge Audit runs on Binky before any customer.
  4. Evidence is recorded at solution time, not reconstructed later.

The dogfood loop

Sense:     internal operational pain
Interpret: map pain to ecosystem capability
Decide:    use / build / adapt capability
Act:       solve internally
Record:    evidence and reusable pattern
Learn:     update productization backlog (OfferCatalog.md)

Evidence entry template

dogfood_case: ""
date: ""
pain: ""
capability_used: ""
pillar: coulomb | net_kingdom | railiance | cross
before: ""
after: ""
effort: ""
reusable_pattern: ""
product_implication: ""
evidence_links: []

Evidence log

(append entries below)