Outcomes

Open Outcomes to see the real work your team shipped in the last 7 days, and how much tracked time is linked to each piece of it.

Who this is for

Anyone signed in can open Outcomes, but seeing what shipped needs the permission that reads outcomes, and, like the rest of Proof Ledger, only the Owner role carries it by default. A manager or member without it sees a message instead of the list. Connecting or syncing a system, and confirming or rejecting a suggested link, need a further permission that's also owner-only by default. Notably, the Confirm and Reject buttons on a link show up for anyone who can open the page, whether or not they hold that permission. Selecting one without it just produces an error, rather than the buttons being hidden.

What you'll see

• A lede reading What shipped, with receipts. Real deliverables from the last 7 days (pull requests, issues, tasks) linked to the time your team spent on them.
• Two headline numbers: Shipped this week and Time attributed.
• A This week in review written summary, tagged AI summary or Summary depending on how it was produced.
• A Connectors section. Today only GitHub can actually be connected. A note underneath says Jira, Linear, Asana, CRM connectors, inbound webhooks, and the public API are on the roadmap. Once GitHub is connected, a Sync now button pulls the latest merged pull requests and closed issues; before that, a Connect GitHub button starts the connection.
• A list of This week's deliverables: each one shows its title (linking back to the source system), its state, and how much time is attributed to it. Underneath, any tracked time the system has matched to it shows as its own row: the member's name, a confidence badge showing a percentage match, and (once reviewed) a confirmed or rejected tag. A deliverable with no matches yet says "No time linked yet. This shipped, but no tracked work matched it."
• A disclosure line under the list: *"Outcome links are automatically suggested, confidence-scored, and may be wrong. They are advisory only, correctable and disputable, and are never used on their own for pay, scheduling, or discipline."*
• A collapsed Activity signals (secondary) note at the bottom, for anyone who wants the supporting activity context. It's explicit that this is motion, not output, and is never used alone for pay, scheduling, or discipline.

What happens next

A suggested link starts out proposed. Selecting Confirm marks it confirmed; selecting Reject marks it rejected. Either way, this only changes whether the link counts as matched to that piece of shipped work. It never changes the underlying time entry itself.

If it doesn't work

• Without the read permission, the deliverables list shows: "The outcomes view needs the outcomes:read permission."
• Any other load failure shows the server's own message, or "Couldn't load what shipped."
• Selecting Confirm or Reject without the manage permission: "Confirming links needs the outcomes:manage permission."
• Trying to sync or connect without that permission: "Syncing needs the outcomes:manage permission." / "Couldn't start the connect flow."
• If GitHub OAuth isn't set up on your server yet, the Connectors section just says so: "GitHub OAuth isn't configured on this server yet." There's nothing to click until that's fixed.
• Nothing shipped yet: "Nothing shipped in the last 7 days" / "Connect GitHub and run a sync, or check back after your team merges some work."

Related

• Proof Ledger (overview)
• Certificates
• Connect GitHub as a source of deliverables