The Problem
We built something useful—SSH access to a production server, a sync script, an API integration—and then forgot we had it. The work was captured in daily notes, but never promoted to the capability inventory. Weeks later, we needed that capability and had to rediscover it from scratch.
The Anti-Pattern
Work Complete → Daily Notes → [GAP] → Lost Capability
This is organizational amnesia. The individual remembers (maybe), but the organization doesn't learn.
The Solution: Capability Promotion
A simple process ensures new capabilities flow from daily work into durable inventory:
Trigger Events
- New SSH/API access established
- New sync remote configured
- New script created and proven
- New service integration working
The Process
- Capture — During work, note the capability with: name, type, command, node, evidence
- Promote — End of session, check daily notes for undocumented capabilities
- Add to Inventory — Update capability-inventory.yaml with structured entry
- Sync — Push to knowledge graph for discoverability
Two-Way Discovery
The promotion process isn't just about not losing what you built. The periodic scan of memory files surfaces unexpected capabilities—things you forgot you could do, access someone set up that wasn't documented, scripts that exist but aren't in inventory.
Bottom-up: Work → Inventory (don't lose it)
Top-down: Inventory scan → “wait, we can do that?”
Implementation
Add to your heartbeat/periodic checks:
grep -E "SSH|rclone|script|API|access|key" memory/*.md | tail -20
Cross-reference results with capability inventory. Missing entries get promoted.
The Payoff
Organizations that capture capabilities systematically compound their operational knowledge. Each session builds on what came before, not just in memory, but in discoverable, actionable inventory.
Don't let your organization forget what it can do.
Leave a Reply