Use this route to understand current posture, not to answer live A/B/C asks.
/state
Orientation, not decision capture.
Keeping status here prevents the decision inbox from turning back into a mixed pile of context and asks.
The homepage still captures decisions into D1, and each successful save can emit an active Telegram alert from the Pages Function.
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
Current read on the surface
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
live
green
Production saves now persist durably in Cloudflare D1 through the bound DECISION_DB Pages binding.
Notification plumbing
visible alert
Telegram live
green
Successful saves now trigger a Telegram alert to Coco/OpenClaw from the Pages Function.
Roles
Who owns what
Keeps Derek-facing asks short, clear, and attached to the right brief.
Return validated artifacts instead of process chatter.
Lives under /api/decisions and prefers D1 when the binding is present.