Context tree: organic Obsidian-like graph layout (stacked on #68) by kateebonner · Pull Request #70 · harmoniqs/opencode

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner · 2026-07-27T21:54:49Z

Stacked on #68 — diff unique here is the last commit.

Kate: "should the context tree look more like an obsidian graph??? i think so." Agreed, with bones kept: pure force clouds lose the turn structure, so this is organic-with-structure.

Deterministic force settle: root pinned at center, turns seeded on a ring in session order, leaves fanned around their turn, then a fixed repel+spring iteration count with zero randomness — identical trees settle identically (tests stay meaningful, no layout jitter between visits).
Recall links are weak springs: context that multiple turns keep touching physically drifts between them — the cloud's shape shows what the session returns to.
Obsidian idioms: straight edges, labels centered under nodes, hover brightens the node's whole neighborhood (edges + neighbor labels).
Architecture unchanged: settle runs synchronously in setTree, the render loop lerps nodes to the new equilibrium (that drift IS the organic feel — no per-frame physics cost). Pointer, wheel-zoom, keyboard nav, aria-live announcements, reduced-motion all untouched.
ADR 0003 + CONTEXT.md glossary updated to the organic description.

Verification: ui 345 + app 442 tests green, typecheck clean, lint 0 errors.

🤖 Generated with Claude Code

…d graph Kate's call (2026-07-27): the tidy left-to-right tree reads as a diagram; the context should read as a living graph. Layout is now a deterministic force settle — root pinned at center, turns seeded on a ring in session order, each turn's context clustering around it; recall links act as weak springs so shared context physically sits between the turns that keep returning to it. Straight Obsidian-style edges, labels centered under nodes, hovered node's neighborhood brightens. Same declarative setTree/lerp architecture (the settle runs synchronously; the render loop drifts nodes to the new equilibrium — no per-frame physics), so interactivity, keyboard nav, and reduced motion are untouched. Docs updated (ADR 0003 + CONTEXT.md). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

kateebonner force-pushed the kate/context-tree-organic branch from dd4e134 to c8468a4Compare July 27, 2026 22:22