@djjones — the non-merge demo PR for the sidebar UX redesign is open for your review:
This is the D50 feel-check we agreed on at last week’s dev call — the inspectable branch you said you’d run the harness against before deciding the merge path for the real implementation.
What’s in the branch
Phases 0–5 from the sidebar-ux build plan, plus a sub-scope simplification (D52) that landed today after evaluating the layout against the live dev runtime:
- App scope is a first-class chat scope. Click Your Budget from the Finances sidebar → opens
budget.md+ scopes the chat to Budget. Breadcrumb Budget segment is clickable to re-open the state file. - One Your Agent concept across the product. Anchored at BD root only — the chat surface for the BD+1 meta-agent. At project + app scope,
AGENT.mdis demoted to Advanced as a customization knob (the agent is rooted; sub-scopes only tune it). - App sidebar simplified. Your Agent, Your Budget, and Your Rules peer items removed. Just Your Files (Reports + Statements) + Advanced. Breadcrumb does the rest.
- Reports + statements relocated into
budget/— they’re budget assets, not generic Finance reference. - Labels: Finance → Finances (plural life-area name);
Message your BrainDrive…→Message your agent…everywhere. - Your To-Do row removed per D51;
me/todo.md+ memory-layer access retained so the agent still surfaces todos conversationally.
Source decisions: D46 (orientation pattern), D48 (breadcrumb), D49 (BD+1 root), D50 (two-Dave alignment + demo PR), D51 (drop Your To-Do), D52 (sub-scope simplification).
Two open items I want your eyes on
-
Chat is visually scope-aware but NOT agent-aware. When you click into Budget the empty-state intro switches (“Let’s work on your budget”) and
{app: "budget"}lands in message metadata — but the gateway bootstrap doesn’t yet loadbudget/AGENT.mddifferently. The agent behaves as the parent-scope agent regardless. The visual implies more than the agent does. Most important remaining gap before app-scope chat is real. -
Your prefix asymmetry. Root + project use Your X peers (Your Goals, Your Plan, Your Budget). App scope dropped them in favor of breadcrumb + Your Files + Advanced. Deliberate — the breadcrumb signals ownership once you’re zoomed in — but worth your sanity check before we lock the convention.
Your call
Per D50 this isn’t merging directly. After your run-through, the real question is the merge path for the actual implementation — likely you rebuild against the architecture-migration trunk with these conventions, rather than merging this branch as-is. Open to whatever feels right.
Tests are green; tsc --noEmit is clean. Boot with npm run dev from builds/typescript/ and try clicking around Finances → Budget.