coulomb/binky-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
binky-control/DogfoodPolicy.md
tegwick 5b1a4f62f5 Ratify company canon v1.0 (DEC-2026-001, approved with edits) 
Founder edits: Railiance role refined to reliable deployment & operations;
Operational Knowledge added as fourth ecosystem pillar. Edits propagated to
EcosystemMap and DogfoodPolicy. DEC-2026-001 resolved; workplan task
BINKY-WP-0002-T01 closed in file and hub.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-16 03:15:11 +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 | operational_knowledge | cross
before: ""
after: ""
effort: ""
reusable_pattern: ""
product_implication: ""
evidence_links: []

Evidence log

(append entries below)