Lessons tagged “cognitive-architecture”
14 published lessons with this tag.
Agent scope should be narrow
Each agent should handle one specific situation — multi-purpose agents are fragile.
Multiple agents must coordinate to be effective
When you run several cognitive agents they need to work together not interfere with each other.
Agent conflicts arise from overlapping scope
When two agents try to handle the same situation they may give conflicting instructions.
Agent sequencing
Some agents must run in a specific order — define the sequence explicitly.
Agent dependency mapping
Draw the dependencies between your agents to see the full coordination picture.
Well-coordinated agents feel like effortless competence
When your agents work together smoothly the result looks like natural ability to others.
Master delegators appear to do less but accomplish more
Effective delegation means your results exceed what your personal effort alone could produce.
Agent reliability metrics
Track how often each agent fires when it should and does not fire when it should not.
Scope optimization
An agent that tries to do too much does nothing well. Optimize by narrowing scope to what matters.
The agent creation process
Creating an agent is a deliberate design act — not something that just happens.
Agent templates
Create reusable templates for common agent patterns to accelerate creation of new agents.
Willpower for emergency use only
Reserve willpower for genuine emergencies rather than daily operations.
Teams think collectively
A team is not just individuals — it has collective cognitive processes that can be designed and improved.
Meeting design as cognitive architecture
Meetings are the primary site where teams think together. A poorly designed meeting wastes collective cognitive capacity. A well-designed meeting is a cognitive tool that produces thinking no individual could achieve alone.