Creating Decisions
Create a decision in the dashboard with the right title, scope, context, and publish flow.
Use this page when you want to create a new decision from the dashboard instead of from an IDE workflow.
What You Need First
You need write access to decisions and a clear idea of the scope you want to capture. If the decision applies across the workspace, make it organization-scoped. If it only applies to one repository, choose repository scope and specify the target repository.
Create A Draft In The Editor
Open /decisions/new to enter the draft editor. The editor supports two working styles. You can start with a one-line intent and use generation to produce a first draft, or you can write the title and document content directly yourself.
The editor is organized around the sections most teams expect in a decision record:
- context
- decision
- alternatives
- consequences
- rollout
Choose the decision type, confirm the scope, and then fill in the content until the draft describes the problem, the choice, and the expected effect clearly enough for review.
Save Vs Publish
Saving creates the draft and sends you to the detail view. Publishing is the later lifecycle step that moves the record into an accepted state after the team is ready. If you are still shaping the decision, save the draft first.
What Success Looks Like
A saved draft appears in /decisions, opens cleanly in the detail page, and can be edited or reviewed by the right people in the workspace.