Mind · Strategy
DogfoodFirst
Use your own tool before shipping
Definition
Mechanism
Before releasing a tool or pattern, the creator must use it to solve a non-trivial problem in their own workflow. This generates 'Friction Logs' that identify usability gaps missed by theoretical design. It requires the creator to act as a Canary, using the tool in production and generating a Reflexion log of friction points.
Preconditions
- Real-world use case identified
- Tool/Pattern is functionally complete
Postconditions
- Friction Log generated
- Release Gate passed OR Refactor triggered
Invariants
- Friction Documentation: All UX hurdles encountered must be logged.
- Skin in the Game: Validation must involve real risk or real work (not a simulation).
Risks
Failure modes
Hello World Fallacy
Validating only on trivial 'demo' cases instead of production loads.
Creator {{cognitive_bias}}
Creator unconsciously avoids edge cases they know will fail.
Relationships
Builds on
References
Society
Expendable agent tests the full coordination path before real commit
Infrastructure
Structural processing error definition
Infrastructure
Filter payload if the target condition is not met
Self-critique and retry after failure
Used by
References
Process demonstrates thesis
Reference
Parameters
durationDuration, unspecified- Minimum time the creator must use the tool on real work. Default 1h.