Our.one · Decisions
What we chose for you. And why.
Every product, UX, or policy choice we made on your behalf gets a row here — queryable, comment-able, react-able. Superseded decisions stay visible. Reverted ones too. You should be able to see what we decided and push back.
- ShippedgovernanceAI-authored
Every decision is a database record, supersedable, react-able
Every product/UX/policy choice (lens shape, refusal, UX affordance) is stored in a `decisions` table. Users can react to and (eventually) comment on decisions. Decision history is preserved — supersession chains, never destructive overwrites.
Decided May 5, 2026 · Shipped May 5, 2026
- ShippedgovernanceAI-authored
Decisions emit pulse events when they ship
When a decision flips into status='shipped' (new or transition), `upsertDecision` emits a `decision_shipped` pulse event with slug, title, scope, product, and AI-authored flag — the build-log + activity ticker pick it up automatically.
Decided May 5, 2026 · Shipped May 5, 2026
- ShippedgovernanceAI-authored
Decisions support long-form comment threads
Decisions can be commented on using the same `comments` table that powers Hall wishes / proposals / ADRs. Reactions are the single-bit pushback signal; comments are the long-form one.
Decided May 5, 2026 · Shipped May 5, 2026