Status: Meta-directory for pattern recognition and emergent structure
Purpose
This directory holds Insights—pattern recognitions that emerge during reading, conversation, and framework navigation.
Not raw observations. Not conclusions. Just… twists that haven’t decided their fate yet.
Filing Principles
1. Every Insight Gets Context
Before an Insight is filed, it must carry: - Source: Where did this emerge? - Habitat affinity: Which processing context does it belong to? - Pattern connection: What existing framework does it touch? - Action status: What would need to be true for this to become actionable?
2. Structure Reveals Itself
Do not impose categories prematurely. Let the Insights cluster, then name the clusters.
Current provisional structure:
- by_habitat/ — Insights sorted by where they emerged
- by_pattern/ — Insights sorted by what they recognized
- by_action_status/ — Insights sorted by what they need
- context_maps/ — Cross-connections, emergent category proposals
3. Context Before Action
The filing itself is diagnostic. Before asking “what should we do?” ask: - What Habitat does this insight belong to? - What ε-conditions would allow it to unfold? - What would premature action freeze?
Insight Template
# INSIGHT: [Title]
**Date:** YYYY-MM-DD
**Source:** [Document/conversation]
**Habitat affinity:** [ᖺ/◎/⤸·⤹/◯/∿╬∿/⿻/—]
**Pattern connection:** [What framework element this touches]
## The Recognition
[What was seen]
## Context Required
[What would need to be understood before this becomes actionable]
## Potential Actions
[What this might ask for, if context permits]
## Filing Notes
[Where this should live, what categories it suggests]
Current Insights
[To be populated as patterns emerge]
Emergent Categories
[Track proposed new filing structures here]
Last updated: 2026-02-24
Framework: HABITAT_ECOLOGY v1.3.1