Decision Briefs
Who approved this, and on what basis?
Turn selected signals into a reviewed brief. A committee can see the supporting sources, the approver, and the approval date.
The problem
Recommendations arrive without accountability
A useful brief shows the recommendation, supporting sources, assumptions, approver, and approval date.
- 1
Select
Pick the signals that bear on the decision from the feed, with each one carrying its source attribution.
Analyst-selected, not auto-selected
- 2
Synthesise
Create a structured draft from the selected signals.
Draft checked before it is saved
- 3
Review
A human reads the draft against its cited evidence and the assumptions it declares, and edits or rejects it.
Draft state until a person acts
- 4
Approve and record
Approval is recorded against the decision with the approver and the reason, creating the trail a committee can reconstruct later.
Approver + reason required
What you get
What a brief leaves behind
Brief from selected signals
You choose the signals. The brief records the selected inputs so a reviewer can inspect them.
Selected signals remain linked to the brief
Decision record
A brief that leads to a decision records what was decided, why it was decided, and when it was approved. The supporting signals stay linked to the decision.
Decision and supporting signals are saved together
Named approval
Recommendations touching capital, contracts, hedges, production operations, or counterparties do not proceed on a model's say-so. They wait for a named approver.
Approval record with an explicit reason
Recommendation drafts for human review
The output is framed as a draft for review. That framing lives in the product, not just in this copy.
Drafts, explicitly labeled as such
Export for the pack
Export the brief for an investment-committee pack without retyping the analysis.
Dedicated brief export path
Clear empty state
When no signals are available, the page says so and does not create a placeholder brief.
No signals available
Access status
Decision briefs run inside Compute Desk and require an approved organization account. Each output is presented as a draft recommendation for human review.
Questions
What committees ask
Does the system make decisions?
No. It prepares recommendations for human review. A named person must approve consequential decisions, and GreenCIO records that approval.
What is saved?
The brief, the signals it was built from, the decision record, and the approval. They are written together so a decision cannot end up separated from the evidence that produced it.
Is there a scored track record of past briefs?
Not today. A decision outcome ledger that scores recommendations against what actually happened is on the roadmap, and we do not claim a measured record in its absence.
See the outcome ledger entryWhat happens if the underlying signals are unavailable?
The page states that no signals are available. It does not replace missing signals with sample content.
Test it on a decision you already made
The clearest test of a decision record is a decision you remember. We will build the brief and show you the trail it leaves.