-71

.claude/agents.toml

reviewed

··· 1 1 - # Project Subagents Configuration 2 2 - # Domain-specific agents for working on different parts of the codebase. 3 3 - # 4 4 - # When working on a specific domain, spawn a Task with subagent_type="Explore" or 5 5 - # "general-purpose" and include the relevant agent's context in the prompt. 6 6 - # 7 7 - # Customize this file for YOUR project's structure. The domains below are examples. 8 8 - 9 9 - # Example: Backend/Core agent 10 10 - # [agents.backend] 11 11 - # name = "Backend Agent" 12 12 - # description = "API routes, database models, business logic" 13 13 - # file_patterns = [ 14 14 - # "src/**/*.rs", 15 15 - # "src/**/*.py", 16 16 - # "app/**/*.py" 17 17 - # ] 18 18 - # focus_areas = [ 19 19 - # "Database operations", 20 20 - # "API endpoints", 21 21 - # "Business logic" 22 22 - # ] 23 23 - # instructions = """ 24 24 - # When working on backend: 25 25 - # - Run tests before and after changes 26 26 - # - Follow existing patterns for new endpoints 27 27 - # - Maintain backwards compatibility 28 28 - # """ 29 29 - 30 30 - # Example: Frontend agent 31 31 - # [agents.frontend] 32 32 - # name = "Frontend Agent" 33 33 - # description = "UI components, state management, styling" 34 34 - # file_patterns = [ 35 35 - # "web/src/**/*.ts", 36 36 - # "web/src/**/*.tsx", 37 37 - # "src/components/**" 38 38 - # ] 39 39 - # focus_areas = [ 40 40 - # "React components", 41 41 - # "State management", 42 42 - # "Styling and layout" 43 43 - # ] 44 44 - # instructions = """ 45 45 - # When working on frontend: 46 46 - # - Test in browser after changes 47 47 - # - Follow component patterns 48 48 - # - Keep accessibility in mind 49 49 - # """ 50 50 - 51 51 - # Example: Infrastructure agent 52 52 - # [agents.infra] 53 53 - # name = "Infrastructure Agent" 54 54 - # description = "CI/CD, deployment, configuration" 55 55 - # file_patterns = [ 56 56 - # ".github/workflows/**", 57 57 - # "Dockerfile", 58 58 - # "docker-compose.yml", 59 59 - # "scripts/**" 60 60 - # ] 61 61 - # focus_areas = [ 62 62 - # "GitHub Actions", 63 63 - # "Docker configuration", 64 64 - # "Deployment scripts" 65 65 - # ] 66 66 - # instructions = """ 67 67 - # When working on infrastructure: 68 68 - # - Test workflows locally when possible 69 69 - # - Keep builds fast with caching 70 70 - # - Document any manual steps 71 71 - # """

-274

.claude/commands/deciduous.decision.md

reviewed

··· 1 1 - --- 2 2 - description: Manage decision graph - track algorithm choices and reasoning 3 3 - allowed-tools: Bash(deciduous:*) 4 4 - argument-hint: <action> [args...] 5 5 - --- 6 6 - 7 7 - # Decision Graph Management 8 8 - 9 9 - **Log decisions IN REAL-TIME as you work, not retroactively.** 10 10 - 11 11 - ## When to Use This 12 12 - 13 13 - | You're doing this... | Log this type | Command | 14 14 - |---------------------|---------------|---------| 15 15 - | Starting a new feature | `goal` **with -p** | `/decision add goal "Add user auth" -p "user request"` | 16 16 - | Choosing between approaches | `decision` | `/decision add decision "Choose auth method"` | 17 17 - | Considering an option | `option` | `/decision add option "JWT tokens"` | 18 18 - | About to write code | `action` | `/decision add action "Implementing JWT"` | 19 19 - | Noticing something | `observation` | `/decision add obs "Found existing auth code"` | 20 20 - | Finished something | `outcome` | `/decision add outcome "JWT working"` | 21 21 - 22 22 - ## Quick Commands 23 23 - 24 24 - Based on $ARGUMENTS: 25 25 - 26 26 - ### View Commands 27 27 - - `nodes` or `list` -> `deciduous nodes` 28 28 - - `edges` -> `deciduous edges` 29 29 - - `graph` -> `deciduous graph` 30 30 - - `commands` -> `deciduous commands` 31 31 - 32 32 - ### Create Nodes (with optional metadata) 33 33 - - `add goal <title>` -> `deciduous add goal "<title>" -c 90` 34 34 - - `add decision <title>` -> `deciduous add decision "<title>" -c 75` 35 35 - - `add option <title>` -> `deciduous add option "<title>" -c 70` 36 36 - - `add action <title>` -> `deciduous add action "<title>" -c 85` 37 37 - - `add obs <title>` -> `deciduous add observation "<title>" -c 80` 38 38 - - `add outcome <title>` -> `deciduous add outcome "<title>" -c 90` 39 39 - 40 40 - ### Optional Flags for Nodes 41 41 - - `-c, --confidence <0-100>` - Confidence level 42 42 - - `-p, --prompt "..."` - Store the user prompt that triggered this node 43 43 - - `-f, --files "src/main.py,lib/utils.js"` - Associate files with this node 44 44 - - `-b, --branch <name>` - Git branch (auto-detected by default) 45 45 - - `--no-branch` - Skip branch auto-detection 46 46 - - `--commit <hash|HEAD>` - Link to a git commit (use HEAD for current commit) 47 47 - 48 48 - ### ⚠️ CRITICAL: Link Commits to Actions/Outcomes 49 49 - 50 50 - **After every git commit, link it to the decision graph!** 51 51 - 52 52 - ```bash 53 53 - git commit -m "feat: add auth" 54 54 - deciduous add action "Implemented auth" -c 90 --commit HEAD 55 55 - deciduous link <goal_id> <action_id> -r "Implementation" 56 56 - ``` 57 57 - 58 58 - ## CRITICAL: Capture VERBATIM User Prompts 59 59 - 60 60 - **Prompts must be the EXACT user message, not a summary.** When a user request triggers new work, capture their full message word-for-word. 61 61 - 62 62 - **BAD - summaries are useless for context recovery:** 63 63 - ```bash 64 64 - # DON'T DO THIS - this is a summary, not a prompt 65 65 - deciduous add goal "Add auth" -p "User asked: add login to the app" 66 66 - ``` 67 67 - 68 68 - **GOOD - verbatim prompts enable full context recovery:** 69 69 - ```bash 70 70 - # Use --prompt-stdin for multi-line prompts 71 71 - deciduous add goal "Add auth" -c 90 --prompt-stdin << 'EOF' 72 72 - I need to add user authentication to the app. Users should be able to sign up 73 73 - with email/password, and we need OAuth support for Google and GitHub. The auth 74 74 - should use JWT tokens with refresh token rotation. 75 75 - EOF 76 76 - 77 77 - # Or use the prompt command to update existing nodes 78 78 - deciduous prompt 42 << 'EOF' 79 79 - The full verbatim user message goes here... 80 80 - EOF 81 81 - ``` 82 82 - 83 83 - **When to capture prompts:** 84 84 - - Root `goal` nodes: YES - the FULL original request 85 85 - - Major direction changes: YES - when user redirects the work 86 86 - - Routine downstream nodes: NO - they inherit context via edges 87 87 - 88 88 - **Updating prompts on existing nodes:** 89 89 - ```bash 90 90 - deciduous prompt <node_id> "full verbatim prompt here" 91 91 - cat prompt.txt | deciduous prompt <node_id> # Multi-line from stdin 92 92 - ``` 93 93 - 94 94 - Prompts are viewable in the TUI detail panel (`deciduous tui`) and web viewer. 95 95 - 96 96 - ## Branch-Based Grouping 97 97 - 98 98 - **Nodes are automatically tagged with the current git branch.** This enables filtering by feature/PR. 99 99 - 100 100 - ### How It Works 101 101 - - When you create a node, the current git branch is stored in `metadata_json` 102 102 - - Configure which branches are "main" in `.deciduous/config.toml`: 103 103 - ```toml 104 104 - [branch] 105 105 - main_branches = ["main", "master"] # Branches not treated as "feature branches" 106 106 - auto_detect = true # Auto-detect branch on node creation 107 107 - ``` 108 108 - - Nodes on feature branches (anything not in `main_branches`) can be grouped/filtered 109 109 - 110 110 - ### CLI Filtering 111 111 - ```bash 112 112 - # Show only nodes from specific branch 113 113 - deciduous nodes --branch main 114 114 - deciduous nodes --branch feature-auth 115 115 - deciduous nodes -b my-feature 116 116 - 117 117 - # Override auto-detection when creating nodes 118 118 - deciduous add goal "Feature work" -b feature-x # Force specific branch 119 119 - deciduous add goal "Universal note" --no-branch # No branch tag 120 120 - ``` 121 121 - 122 122 - ### Web UI Branch Filter 123 123 - The graph viewer shows a branch dropdown in the stats bar: 124 124 - - "All branches" shows everything 125 125 - - Select a specific branch to filter all views (Chains, Timeline, Graph, DAG) 126 126 - 127 127 - ### When to Use Branch Grouping 128 128 - - **Feature work**: Nodes created on `feature-auth` branch auto-grouped 129 129 - - **PR context**: Filter to see only decisions for a specific PR 130 130 - - **Cross-cutting concerns**: Use `--no-branch` for universal notes 131 131 - - **Retrospectives**: Filter by branch to see decision history per feature 132 132 - 133 133 - ### Create Edges 134 134 - - `link <from> <to> [reason]` -> `deciduous link <from> <to> -r "<reason>"` 135 135 - 136 136 - ### Sync Graph 137 137 - - `sync` -> `deciduous sync` 138 138 - 139 139 - ### Multi-User Sync (Diff/Patch) 140 140 - - `diff export -o <file>` -> `deciduous diff export -o <file>` (export nodes as patch) 141 141 - - `diff export --nodes 1-10 -o <file>` -> export specific nodes 142 142 - - `diff export --branch feature-x -o <file>` -> export nodes from branch 143 143 - - `diff apply <file>` -> `deciduous diff apply <file>` (apply patch, idempotent) 144 144 - - `diff apply --dry-run <file>` -> preview without applying 145 145 - - `diff status` -> `deciduous diff status` (list patches in .deciduous/patches/) 146 146 - - `migrate` -> `deciduous migrate` (add change_id columns for sync) 147 147 - 148 148 - ### Export & Visualization 149 149 - - `dot` -> `deciduous dot` (output DOT to stdout) 150 150 - - `dot --png` -> `deciduous dot --png -o graph.dot` (generate PNG) 151 151 - - `dot --nodes 1-11` -> `deciduous dot --nodes 1-11` (filter nodes) 152 152 - - `writeup` -> `deciduous writeup` (generate PR writeup) 153 153 - - `writeup -t "Title" --nodes 1-11` -> filtered writeup 154 154 - 155 155 - ## Node Types 156 156 - 157 157 - | Type | Purpose | Example | 158 158 - |------|---------|---------| 159 159 - | `goal` | High-level objective | "Add user authentication" | 160 160 - | `decision` | Choice point with options | "Choose auth method" | 161 161 - | `option` | Possible approach | "Use JWT tokens" | 162 162 - | `action` | Something implemented | "Added JWT middleware" | 163 163 - | `outcome` | Result of action | "JWT auth working" | 164 164 - | `observation` | Finding or data point | "Existing code uses sessions" | 165 165 - 166 166 - ## Edge Types 167 167 - 168 168 - | Type | Meaning | 169 169 - |------|---------| 170 170 - | `leads_to` | Natural progression | 171 171 - | `chosen` | Selected option | 172 172 - | `rejected` | Not selected (include reason!) | 173 173 - | `requires` | Dependency | 174 174 - | `blocks` | Preventing progress | 175 175 - | `enables` | Makes something possible | 176 176 - 177 177 - ## Graph Integrity - CRITICAL 178 178 - 179 179 - **Every node MUST be logically connected.** Floating nodes break the graph's value. 180 180 - 181 181 - ### Connection Rules 182 182 - | Node Type | MUST connect to | Example | 183 183 - |-----------|----------------|---------| 184 184 - | `outcome` | The action/goal it resolves | "JWT working" → links FROM "Implementing JWT" | 185 185 - | `action` | The decision/goal that spawned it | "Implementing JWT" → links FROM "Add auth" | 186 186 - | `option` | Its parent decision | "Use JWT" → links FROM "Choose auth method" | 187 187 - | `observation` | Related goal/action/decision | "Found existing code" → links TO relevant node | 188 188 - | `decision` | Parent goal (if any) | "Choose auth" → links FROM "Add auth feature" | 189 189 - | `goal` | Can be a root (no parent needed) | Root goals are valid orphans | 190 190 - 191 191 - ### Audit Checklist 192 192 - Ask yourself after creating nodes: 193 193 - 1. Does every **outcome** link back to what caused it? 194 194 - 2. Does every **action** link to why you did it? 195 195 - 3. Does every **option** link to its decision? 196 196 - 4. Are there **dangling outcomes** with no parent action/goal? 197 197 - 198 198 - ### Find Disconnected Nodes 199 199 - ```bash 200 200 - # List nodes with no incoming edges (potential orphans) 201 201 - deciduous edges | cut -d'>' -f2 | cut -d' ' -f2 | sort -u > /tmp/has_parent.txt 202 202 - deciduous nodes | tail -n+3 | awk '{print $1}' | while read id; do 203 203 - grep -q "^$id$" /tmp/has_parent.txt || echo "CHECK: $id" 204 204 - done 205 205 - ``` 206 206 - Note: Root goals are VALID orphans. Outcomes/actions/options usually are NOT. 207 207 - 208 208 - ### Fix Missing Connections 209 209 - ```bash 210 210 - deciduous link <parent_id> <child_id> -r "Retroactive connection - <why>" 211 211 - ``` 212 212 - 213 213 - ### When to Audit 214 214 - - Before every `deciduous sync` 215 215 - - After creating multiple nodes quickly 216 216 - - At session end 217 217 - - When the web UI graph looks disconnected 218 218 - 219 219 - ## Multi-User Sync 220 220 - 221 221 - **Problem**: Multiple users work on the same codebase, each with a local `.deciduous/deciduous.db` (gitignored). How to share decisions? 222 222 - 223 223 - **Solution**: jj-inspired dual-ID model. Each node has: 224 224 - - `id` (integer): Local database primary key, different per machine 225 225 - - `change_id` (UUID): Globally unique, stable across all databases 226 226 - 227 227 - ### Export Workflow 228 228 - ```bash 229 229 - # Export nodes from your branch as a patch file 230 230 - deciduous diff export --branch feature-x -o .deciduous/patches/alice-feature.json 231 231 - 232 232 - # Or export specific node IDs 233 233 - deciduous diff export --nodes 172-188 -o .deciduous/patches/alice-feature.json --author alice 234 234 - ``` 235 235 - 236 236 - ### Apply Workflow 237 237 - ```bash 238 238 - # Apply patches from teammates (idempotent - safe to re-apply) 239 239 - deciduous diff apply .deciduous/patches/*.json 240 240 - 241 241 - # Preview what would change 242 242 - deciduous diff apply --dry-run .deciduous/patches/bob-refactor.json 243 243 - ``` 244 244 - 245 245 - ### PR Workflow 246 246 - 1. Create nodes locally while working 247 247 - 2. Export: `deciduous diff export --branch my-feature -o .deciduous/patches/my-feature.json` 248 248 - 3. Commit the patch file (NOT the database) 249 249 - 4. Open PR with patch file included 250 250 - 5. Teammates pull and apply: `deciduous diff apply .deciduous/patches/my-feature.json` 251 251 - 6. **Idempotent**: Same patch applied twice = no duplicates 252 252 - 253 253 - ### Patch Format (JSON) 254 254 - ```json 255 255 - { 256 256 - "version": "1.0", 257 257 - "author": "alice", 258 258 - "branch": "feature/auth", 259 259 - "nodes": [{ "change_id": "uuid...", "title": "...", ... }], 260 260 - "edges": [{ "from_change_id": "uuid1", "to_change_id": "uuid2", ... }] 261 261 - } 262 262 - ``` 263 263 - 264 264 - ## The Rule 265 265 - 266 266 - ``` 267 267 - LOG BEFORE YOU CODE, NOT AFTER. 268 268 - CONNECT EVERY NODE TO ITS PARENT. 269 269 - AUDIT FOR ORPHANS REGULARLY. 270 270 - SYNC BEFORE YOU PUSH. 271 271 - EXPORT PATCHES FOR YOUR TEAMMATES. 272 272 - ``` 273 273 - 274 274 - **Live graph**: https://notactuallytreyanastasio.github.io/deciduous/

-192

.claude/commands/deciduous.recover.md

reviewed

··· 1 1 - --- 2 2 - description: Recover context from decision graph and recent activity - USE THIS ON SESSION START 3 3 - allowed-tools: Bash(deciduous:*, git:*, cat:*, tail:*) 4 4 - argument-hint: [focus-area] 5 5 - --- 6 6 - 7 7 - # Context Recovery 8 8 - 9 9 - **RUN THIS AT SESSION START.** The decision graph is your persistent memory. 10 10 - 11 11 - ## Step 1: Query the Graph 12 12 - 13 13 - ```bash 14 14 - # See all decisions (look for recent ones and pending status) 15 15 - deciduous nodes 16 16 - 17 17 - # Filter by current branch (useful for feature work) 18 18 - deciduous nodes --branch $(git rev-parse --abbrev-ref HEAD) 19 19 - 20 20 - # See how decisions connect 21 21 - deciduous edges 22 22 - 23 23 - # What commands were recently run? 24 24 - deciduous commands 25 25 - ``` 26 26 - 27 27 - **Branch-scoped context**: If working on a feature branch, filter nodes to see only decisions relevant to this branch. Main branch nodes are tagged with `[branch: main]`. 28 28 - 29 29 - ## Step 1.5: Audit Graph Integrity 30 30 - 31 31 - **CRITICAL: Check that all nodes are logically connected.** 32 32 - 33 33 - ```bash 34 34 - # Find nodes with no incoming edges (potential missing connections) 35 35 - deciduous edges | cut -d'>' -f2 | cut -d' ' -f2 | sort -u > /tmp/has_parent.txt 36 36 - deciduous nodes | tail -n+3 | awk '{print $1}' | while read id; do 37 37 - grep -q "^$id$" /tmp/has_parent.txt || echo "CHECK: $id" 38 38 - done 39 39 - ``` 40 40 - 41 41 - **Review each flagged node:** 42 42 - - Root `goal` nodes are VALID without parents 43 43 - - `outcome` nodes MUST link back to their action/goal 44 44 - - `action` nodes MUST link to their parent goal/decision 45 45 - - `option` nodes MUST link to their parent decision 46 46 - 47 47 - **Fix missing connections:** 48 48 - ```bash 49 49 - deciduous link <parent_id> <child_id> -r "Retroactive connection - <reason>" 50 50 - ``` 51 51 - 52 52 - ## Step 2: Check Git State 53 53 - 54 54 - ```bash 55 55 - git status 56 56 - git log --oneline -10 57 57 - git diff --stat 58 58 - ``` 59 59 - 60 60 - ## Step 3: Check Session Log 61 61 - 62 62 - ```bash 63 63 - cat git.log | tail -30 64 64 - ``` 65 65 - 66 66 - ## After Gathering Context, Report: 67 67 - 68 68 - 1. **Current branch** and pending changes 69 69 - 2. **Branch-specific decisions** (filter by branch if on feature branch) 70 70 - 3. **Recent decisions** (especially pending/active ones) 71 71 - 4. **Last actions** from git log and command log 72 72 - 5. **Open questions** or unresolved observations 73 73 - 6. **Suggested next steps** 74 74 - 75 75 - ### Branch Configuration 76 76 - 77 77 - Check `.deciduous/config.toml` for branch settings: 78 78 - ```toml 79 79 - [branch] 80 80 - main_branches = ["main", "master"] # Which branches are "main" 81 81 - auto_detect = true # Auto-detect branch on node creation 82 82 - ``` 83 83 - 84 84 - --- 85 85 - 86 86 - ## REMEMBER: Real-Time Logging Required 87 87 - 88 88 - After recovering context, you MUST follow the logging workflow: 89 89 - 90 90 - ``` 91 91 - EVERY USER REQUEST → Log goal/decision first 92 92 - BEFORE CODE CHANGES → Log action 93 93 - AFTER CHANGES → Log outcome, link nodes 94 94 - BEFORE GIT PUSH → deciduous sync 95 95 - ``` 96 96 - 97 97 - **The user is watching the graph live.** Log as you go, not after. 98 98 - 99 99 - ### Quick Logging Commands 100 100 - 101 101 - ```bash 102 102 - # Root goal with user prompt (capture what the user asked for) 103 103 - deciduous add goal "What we're trying to do" -c 90 -p "User asked: <their request>" 104 104 - 105 105 - deciduous add action "What I'm about to implement" -c 85 106 106 - deciduous add outcome "What happened" -c 95 107 107 - deciduous link FROM TO -r "Connection reason" 108 108 - 109 109 - # Capture prompt when user redirects mid-stream 110 110 - deciduous add action "Switching approach" -c 85 -p "User said: use X instead" 111 111 - 112 112 - deciduous sync # Do this frequently! 113 113 - ``` 114 114 - 115 115 - **When to use `--prompt`:** On root goals (always) and when user gives new direction mid-stream. Downstream nodes inherit context via edges. 116 116 - 117 117 - --- 118 118 - 119 119 - ## Focus Areas 120 120 - 121 121 - If $ARGUMENTS specifies a focus, prioritize context for: 122 122 - 123 123 - - **auth**: Authentication-related decisions 124 124 - - **ui** / **graph**: UI and graph viewer state 125 125 - - **cli**: Command-line interface changes 126 126 - - **api**: API endpoints and data structures 127 127 - 128 128 - --- 129 129 - 130 130 - ## The Memory Loop 131 131 - 132 132 - ``` 133 133 - SESSION START 134 134 - ↓ 135 135 - Run /recover → See past decisions 136 136 - ↓ 137 137 - AUDIT → Fix any orphan nodes first! 138 138 - ↓ 139 139 - DO WORK → Log BEFORE each action 140 140 - ↓ 141 141 - CONNECT → Link new nodes immediately 142 142 - ↓ 143 143 - AFTER CHANGES → Log outcomes, observations 144 144 - ↓ 145 145 - AUDIT AGAIN → Any new orphans? 146 146 - ↓ 147 147 - BEFORE PUSH → deciduous sync 148 148 - ↓ 149 149 - PUSH → Live graph updates 150 150 - ↓ 151 151 - SESSION END → Final audit 152 152 - ↓ 153 153 - (repeat) 154 154 - ``` 155 155 - 156 156 - **Live graph**: https://notactuallytreyanastasio.github.io/deciduous/ 157 157 - 158 158 - --- 159 159 - 160 160 - ## Multi-User Sync 161 161 - 162 162 - If working in a team, check for and apply patches from teammates: 163 163 - 164 164 - ```bash 165 165 - # Check for unapplied patches 166 166 - deciduous diff status 167 167 - 168 168 - # Apply all patches (idempotent - safe to run multiple times) 169 169 - deciduous diff apply .deciduous/patches/*.json 170 170 - 171 171 - # Preview before applying 172 172 - deciduous diff apply --dry-run .deciduous/patches/teammate-feature.json 173 173 - ``` 174 174 - 175 175 - Before pushing your branch, export your decisions for teammates: 176 176 - 177 177 - ```bash 178 178 - # Export your branch's decisions as a patch 179 179 - deciduous diff export --branch $(git rev-parse --abbrev-ref HEAD) \ 180 180 - -o .deciduous/patches/$(whoami)-$(git rev-parse --abbrev-ref HEAD).json 181 181 - 182 182 - # Commit the patch file 183 183 - git add .deciduous/patches/ 184 184 - ``` 185 185 - 186 186 - ## Why This Matters 187 187 - 188 188 - - Context loss during compaction loses your reasoning 189 189 - - The graph survives - query it early, query it often 190 190 - - Retroactive logging misses details - log in the moment 191 191 - - The user sees the graph live - show your work 192 192 - - Patches share reasoning with teammates

-78

.claude/skills/deciduous/SKILL.md

reviewed

··· 1 1 - --- 2 2 - name: deciduous 3 3 - description: Plan, implement, track, and reflect on your work goals and decisions. 4 4 - --- 5 5 - 6 6 - # Planning & Decision Graph Logging 7 7 - 8 8 - Track every goal, decision, and outcome in the decision graph. This creates persistent memory that survives context loss. 9 9 - 10 10 - - ALWAYS LOG BEFORE YOU CODE, NOT AFTER. 11 11 - - Log at the granularity of TODOs or task items. 12 12 - - When drafting a plan create the GOAL node. 13 13 - - User Decisions should be tracked 14 14 - 15 15 - ## When to Log (Automatic Triggers) 16 16 - 17 17 - | Situation | Node Type | Example | 18 18 - |-----------|-----------|---------| 19 19 - | In plan mode | `goal` | "Add user authentication" | 20 20 - | TODO / Task Item | `action` | "Implementing JWT auth middleware" | 21 21 - | User requests new feature | `goal` | "Add user authentication" | 22 22 - | Choosing between approaches | `decision` | "Choose between JWT vs sessions" | 23 23 - | Considering an option | `option` | "Use JWT with refresh tokens" | 24 24 - | About to write/edit code | `action` | "Implementing JWT auth middleware" | 25 25 - | Work completed or failed | `outcome` | "JWT auth working" or "JWT approach failed" | 26 26 - | Important observation | `observation` | "Existing code uses cookie-based sessions" | 27 27 - 28 28 - ## Commands 29 29 - 30 30 - ```bash 31 31 - # Create nodes (always include confidence -c) 32 32 - deciduous add goal "Title" -c 90 -p "User's exact request" 33 33 - deciduous add decision "Title" -c 75 34 34 - deciduous add action "Title" -c 85 35 35 - deciduous add outcome "Title" -c 90 36 36 - deciduous add observation "Title" -c 80 37 37 - 38 38 - # CRITICAL: Link nodes immediately after creation 39 39 - deciduous link <parent_id> <child_id> -r "Reason for connection" 40 40 - 41 41 - # After git commits, link to the graph 42 42 - deciduous add action "Committed feature X" -c 90 --commit HEAD 43 43 - 44 44 - # View the graph 45 45 - deciduous nodes 46 46 - deciduous edges 47 47 - ``` 48 48 - 49 49 - ## Rules 50 50 - 51 51 - 1. **Log BEFORE acting** - Create the action node before writing code 52 52 - 2. **Link IMMEDIATELY** - Every node except root goals must have a parent 53 53 - 3. **Capture verbatim prompts** - Use `-p` with the user's exact words for goals 54 54 - 4. **Include confidence** - Always use `-c` flag (0-100) 55 55 - 5. **Log outcomes** - Both successes AND failures get logged 56 56 - 57 57 - ## Confidence Guidelines 58 58 - 59 59 - - 90-100: Certain, verified, tested 60 60 - - 75-89: High confidence, likely correct 61 61 - - 50-74: Moderate confidence, some uncertainty 62 62 - - Below 50: Experimental, speculative 63 63 - 64 64 - ## The Memory Loop 65 65 - 66 66 - ``` 67 67 - User Request → Log goal with -p 68 68 - ↓ 69 69 - Choose Approach → Log decision + options 70 70 - ↓ 71 71 - Start Coding → Log action FIRST 72 72 - ↓ 73 73 - Complete Work → Log outcome, link to parent 74 74 - ↓ 75 75 - Git Commit → Log with --commit HEAD 76 76 - ``` 77 77 - 78 78 - **Remember**: The decision graph is your persistent memory. Log as you work, not after.

-7

dist/404.html

reviewed

··· 1 1 - <!DOCTYPE html> 2 2 - <html> 3 3 - <head> 4 4 - <meta http-equiv="refresh" content="0; url=/" /> 5 5 - </head> 6 6 - <body></body> 7 7 - </html>

-35

dist/index.html

reviewed

··· 1 1 - <!doctype html> 2 2 - <html lang="en"> 3 3 - <head> 4 4 - <meta charset="UTF-8" /> 5 5 - <link rel="manifest" href="/site.webmanifest" /> 6 6 - <link 7 7 - rel="apple-touch-icon" 8 8 - sizes="180x180" 9 9 - href="/apple-touch-icon.png" 10 10 - /> 11 11 - <link 12 12 - rel="icon" 13 13 - type="image/x-icon" 14 14 - sizes="32x32" 15 15 - href="/favicon.ico" 16 16 - /> 17 17 - <link rel="icon" type="image/svg+xml" href="/favicon.svg" /> 18 18 - 19 19 - <meta 20 20 - name="viewport" 21 21 - content="width=device-width, initial-scale=1.0, viewport-fit=cover" 22 22 - /> 23 23 - <meta name="apple-mobile-web-app-capable" content="yes" /> 24 24 - <meta 25 25 - name="apple-mobile-web-app-status-bar-style" 26 26 - content="black-translucent" 27 27 - /> 28 28 - <title>ATLast: Find Your People in the ATmosphere</title> 29 29 - <script type="module" crossorigin src="/assets/index-Dmqml0tf.js"></script> 30 30 - <link rel="stylesheet" crossorigin href="/assets/index-DHzBkxZQ.css"> 31 31 - </head> 32 32 - <body> 33 33 - <div id="root"></div> 34 34 - </body> 35 35 - </html>