/state

Orientation, not decision capture.

home owns input

what this page is for Give Derek the operating picture fast.

Use this route to understand current posture, not to answer live A/B/C asks.

why it matters Separates orientation from action.

Keeping status here prevents the decision inbox from turning back into a mixed pile of context and asks.

read brief Why /state exists and what it should exclude.

current open gap Saved decisions still do not notify Derek elsewhere.

The storage path can work, but Telegram or other push notification plumbing is still missing.

Current rules

How the surface is supposed to behave

Decision cards live on home.

Home is where Derek answers asks and where briefs sit closest to the choice.

/state stays concise.

This page exists to orient Derek quickly, not to repeat every implementation detail or bury the signal.

Status should be honest.

If storage or notifications are incomplete, the page should say that plainly instead of implying the system is finished.

KPIs

Metric Goal Current Status What it means

Top-of-site asks clear asks only yes green Home cards now lead with the requested decision.

Owner default agent agent green Human input is still narrow and explicit.

Brief coverage every ask yes green Each decision card now exposes a dedicated brief link.

Submit path real + durable binding dependent open D1 becomes durable once the Pages binding exists.

Notification plumbing visible alert missing open The system can save decisions without notifying Derek elsewhere yet.

Roles

coco main Owns routing, review, and escalation.

Keeps Derek-facing asks short, clear, and attached to the right brief.

execution agents Ship narrow work.

Return validated artifacts instead of process chatter.

decision api Captures responses.

Lives under /api/decisions and prefers D1 when the binding is present.

read brief Need the design rationale?