Tracking committed decisions

Business Summary: Tracking committed decisions gives you an audit-ready trail of who approved what, when, and on what evidence — so you can revisit precedents, satisfy compliance requests, and connect outcomes to the runs that produced them.

Accountability does not end at approval. Nimbus records who decided what, when, and on what evidence so you can revisit precedents and satisfy audit requests.

Note: Per-workstream Activity is live. Org-wide Audit & History at Audit & History may show sample events in demo workspaces and can be empty otherwise. Lifecycle Graph tree view is planned.

How this fits in Nimbus

After sign-off, committed decisions flow into Activity, Outputs, and (when available) org-wide audit views. The same HITL flow that paused the run leaves a durable record you can filter by event type or milestone.

flowchart LR
  SO[Sign-off] --> Act[Workstream Activity]
  SO --> Out[Outputs]
  SO --> MS[Milestones]
  Act --> Audit[Audit and History]
  Out --> Trace[Decision trace]

Workstream Activity tab

The most practical place to track commits today is the workstream Activity tab: run started and completed events, checkpoint opened/approved/rejected, output published to Outputs, Committed to entries naming external destinations, and NTU consumed per run (links to billing detail).

Filter mentally by event type when reviewing a quarterly close or board cycle — approvals cluster around milestone dates.

Outputs and decision trace

Each published artifact in Outputs should link back to the agent run that produced it, approvers who signed off, and source connectors and wiki references used.

The decision trace summarizes how the agent reached its conclusion — which specialists contributed and which gates fired. Use it when stakeholders ask "why this recommendation?"

See .

Overview pending approvals

Before a decision is committed, track open work on the Overview page Pending approvals table — HITL items waiting for sign-off across workstreams you can access. Once approved, items drop from pending and appear in Activity.

Milestones

Milestones mark progress toward your goal. When a checkpoint blocks a milestone, the milestone panel shows waiting state until sign-off completes — then records completion with timestamp. Checkpoints are governance pauses; milestones are progress markers. They often appear together.

Org-wide audit and history

Audit & History at Audit & History is designed for cross-workstream queries — who approved exports, configuration changes, and significant agent runs. Today this page is partial: a demo workspace shows sample rows; production orgs may see an empty state until the org-wide audit log is fully available. Per-workstream Activity remains authoritative for recent commits.

See What works today.

Lifecycle and Knowledge graphs

When lifecycle graph linking is enabled, Lifecycle Graph connects org → workstreams → runs → artifacts → governance events, and Lifecycle Graph shows domain entities the decision referenced. Lifecycle Graph has no dedicated web page yet. Use Lifecycle Graph for domain context today.

Example scenario

During a board cycle, the CFO asks for proof that the revenue forecast was approved before publication. You open the workstream Activity tab, filter for checkpoint and output events around the board date, and follow the decision trace from the published report in Outputs back to two approvers on a Strict Critical gate. You export Activity notes for the audit packet and cross-reference the run ID with NTU usage on the billing dashboard.

What you'll see

What you'll see: Activity rows with timestamps, actor names, event labels like "Output approved" or "Write committed to Salesforce," and links to run detail. Outputs cards show version and approval metadata when HITL was required.

FAQs {#faqs}

Q: Can I export a list of committed decisions? A: Export from Activity and Outputs is evolving. Org audit export is planned with Audit & History maturity.

Q: How long is Activity retained? A: Retention follows your organization's deployment policy. Treat Outputs as the durable artifact store.

Q: I need proof of dual approval — where is it? A: Activity should list both approvers for Strict governance Critical gates. If missing, check run detail or contact support with the run reference from Activity.

Q: Does billing usage prove a decision happened? A: NTU ledger entries prove a run occurred, not the business content. Pair usage entries with Activity for full traceability. See Reading your usage dashboard.

Q: Can viewers see committed decisions? A: Viewers with workstream access can read Outputs and Activity but cannot approve or re-run without contributor role.

Q: What's the difference between Activity and Audit & History? A: Activity is per workstream and live today. Audit & History is org-wide and still rolling out for cross-workstream queries.