|
| 1 | +# See Also Pattern |
| 2 | + |
| 3 | +A systems thinking approach to connecting related concepts in our knowledge base, creating an emergent knowledge graph. |
| 4 | + |
| 5 | +## Systems Perspective |
| 6 | + |
| 7 | +Knowledge isn't linear - it's a network. The "See Also" pattern acknowledges that understanding emerges from seeing connections between concepts. Like synapses in a neural network, these links strengthen the overall system's intelligence. |
| 8 | + |
| 9 | +## When to Consider Adding Links |
| 10 | + |
| 11 | +Add a "See Also" section when you notice: |
| 12 | +- **Resonance**: Two concepts vibrate at similar frequencies (e.g., Jonah personality resonates with throughput definition through constraint thinking) |
| 13 | +- **Implementation relationships**: A procedure actualizes a principle in practice |
| 14 | +- **Complementary perspectives**: Different angles on the same truth enhance understanding |
| 15 | +- **Source relationships**: Concepts flowing from the same wellspring of wisdom |
| 16 | +- **Tension relationships**: Concepts that create productive friction when juxtaposed |
| 17 | + |
| 18 | +## Natural Emergence |
| 19 | + |
| 20 | +Rather than forcing bidirectional links, let connections emerge organically: |
| 21 | +- **One-way links are valid**: Sometimes A illuminates B without B needing to reference A |
| 22 | +- **Asymmetric relationships exist**: A principle might inform many procedures, but those procedures might not all link back |
| 23 | +- **Discovery over prescription**: Links should feel like "aha!" moments, not checkboxes |
| 24 | + |
| 25 | +## Format |
| 26 | + |
| 27 | +Place the "See Also" section at the end, after main content: |
| 28 | + |
| 29 | +```markdown |
| 30 | +## See Also |
| 31 | +- [Link Text](relative/path/to/file.md) - Nature of the connection |
| 32 | +- External Resource - How this enriches understanding |
| 33 | +``` |
| 34 | + |
| 35 | +## Guiding Principles |
| 36 | + |
| 37 | +1. **Quality over symmetry**: A meaningful one-way link beats a forced bidirectional pair |
| 38 | +2. **Context reveals connection**: Brief descriptions help others see what you see |
| 39 | +3. **Relative paths for resilience**: Enable navigation regardless of repository location |
| 40 | +4. **Restraint maintains signal**: Link only when the connection genuinely enhances understanding |
| 41 | +5. **Evolution over perfection**: Links can be added, removed, or changed as understanding deepens |
| 42 | + |
| 43 | +## Examples |
| 44 | + |
| 45 | +**When a principle influences practice:** |
| 46 | +```markdown |
| 47 | +## See Also |
| 48 | +- [Git Workflow](../procedures/git-workflow.md) - How this principle manifests in daily practice |
| 49 | +- [Subtraction Creates Value](subtraction-creates-value.md) - Complementary principle for decision-making |
| 50 | +``` |
| 51 | + |
| 52 | +**When discovering source wisdom:** |
| 53 | +```markdown |
| 54 | +## See Also |
| 55 | +- The Goal by Eliyahu M. Goldratt - Wellspring of Theory of Constraints thinking |
| 56 | +- [Throughput Definition](../throughput-definition.md) - How we've adapted ToC for AI agent management |
| 57 | +``` |
| 58 | + |
| 59 | +## System Benefits |
| 60 | + |
| 61 | +- **Emergent understanding**: Patterns become visible through the network of connections |
| 62 | +- **Reduced cognitive load**: Follow links rather than holding everything in memory |
| 63 | +- **Natural documentation**: The link structure itself documents relationships |
| 64 | +- **Future tooling potential**: Graph visualization, link analysis, concept clustering |
| 65 | + |
| 66 | +This pattern embodies [Systems Stewardship](../principles/systems-stewardship.md) by creating structures that reveal rather than impose order. |
0 commit comments