Second Brain Quick Reference Card
Categorization & Pattern Summary
Content Classification
Article Type
Category: Technical Architecture / System Design Tutorial
Format: Video transcript
Target Audience: Non-engineers seeking personal productivity automation
Depth: Intermediate (principles + implementation)
Domain Tags
Primary: #personal-productivity #ai-automation #knowledge-management
Secondary: #no-code #system-design #workflow-automation
Technical: #zapier #notion #slack #claude #chatgpt
Patterns: #event-driven #separation-of-concerns #trust-engineering
Structural Taxonomy
Building Blocks (8)
| Block | Engineering Term | Layer |
|---|---|---|
| Dropbox | Ingress/Capture | Interface |
| Sorter | Classifier/Router | Compute |
| Form | Schema/Contract | Data |
| Filing Cabinet | Memory Store | Storage |
| Receipt | Audit Trail | Trust |
| Bouncer | Confidence Filter | Trust |
| Tap on Shoulder | Proactive Surfacing | Interface |
| Fix Button | HITL Correction | Trust |
Principles (12)
| # | Principle | Category |
|---|---|---|
| 1 | One reliable behavior | Human-Centric |
| 2 | Safe defaults under uncertainty | Human-Centric |
| 3 | Design for restart | Human-Centric |
| 4 | Separate memory/compute/interface | Architecture |
| 5 | Core loop → modules | Architecture |
| 6 | Minimal categories/fields | Data Design |
| 7 | Next action as unit | Data Design |
| 8 | Route > organize | Data Design |
| 9 | Trust mechanisms > capabilities | Trust |
| 10 | Prompts as APIs | Trust |
| 11 | Small, frequent outputs | Output |
| 12 | Maintainability > cleverness | Output |
Technology Stack
┌─────────────┬─────────────┬─────────────┐
│ INTERFACE │ COMPUTE │ MEMORY │
├─────────────┼─────────────┼─────────────┤
│ Slack │ Zapier │ Notion │
│ (capture) │ (routing) │ (storage) │
│ │ Claude/ │ │
│ │ ChatGPT │ │
│ │ (intel) │ │
└─────────────┴─────────────┴─────────────┘
Key Metrics & Thresholds
| Metric | Target | Rationale |
|---|---|---|
| Capture time | < 5 seconds | Friction kills adoption |
| Daily digest | ≤ 150 words | Phone-readable |
| Weekly review | ≤ 250 words | Scannable |
| Categories | ≤ 4 | Decision fatigue |
| Fields per schema | ≤ 6 | Maintenance burden |
| Confidence threshold | 0.6 | Balance automation vs. accuracy |
| Re-engagement time | < 15 min | Restart resilience |
| Auth fix time | < 5 min | Maintainability |
Pattern Cross-Reference
Applicable To
- CRM Automation
- Meeting Notes Processing
- Email Triage
- Task Management
- Knowledge Base Maintenance
- Multi-Agent Orchestration (Coditect)
- Compliance Documentation
- Developer Workflow Automation
Anti-Patterns to Avoid
- Taxonomy decisions at capture time
- Multiple required user behaviors
- Creative prompts in automation
- Capability without trust mechanisms
- Backlog accumulation on absence
- Feature expansion before core loop validation
- Cleverness over maintainability
Source Attribution
Author: Unidentified (video transcript)
Date: 2026
Platform: Video with Substack companion guide
Duration: ~25 minutes (estimated from transcript length)
Related Concepts
Coditect Relevance Score
| Aspect | Relevance | Notes |
|---|---|---|
| Architectural patterns | ⭐⭐⭐⭐⭐ | Direct mapping to agent orchestration |
| Trust engineering | ⭐⭐⭐⭐⭐ | Critical for regulated industries |
| Token economics | ⭐⭐⭐⭐ | Output size constraints apply |
| Implementation details | ⭐⭐ | No-code stack not directly applicable |
| Enterprise scaling | ⭐⭐⭐ | Principles scale, implementation doesn't |
Overall Relevance: High strategic value, low tactical reuse