Principlev1
Design tool stack architecture with explicit data flows,
Design tool stack architecture with explicit data flows, defined boundaries, and clear integration points rather than accumulating tools as isolated utilities.
Why This Is a Principle
This derives from system behavior arising from structure (The behavior of a system arises from its structure, not from), systems being perfectly designed for their results (Every system is perfectly designed to get the results it), and schemas organizing knowledge at all abstraction levels (Schemas as Knowledge Organization Structures). The principle prescribes treating tools as an integrated system rather than a collection.
Source Lessons
L-0920
Your tool stack is your cognitive infrastructure
The tools you choose and how you configure them define the capabilities of your extended mind.
L-0918
The tool audit
Periodically review your tool stack for redundancy gaps and misalignment.
L-0904
The tool stack
Your complete set of tools should work together as a coherent system.
Connections
Derived From (8)
AxiomExponential Information DecayAxiomOpen-Loop Cognitive Cost (Zeigarnik)AxiomSchemas as Knowledge Organization StructuresAxiomHuman memory under stress and cognitive load is unreliableAxiomCatastrophic failures in complex systems rarely result fromAxiomTask switching between different types of cognitive workAxiomThe behavior of a system arises from its structure, not fromAxiomEvery system is perfectly designed to get the results it