Work units accepted by the customer in the current sample window.
Proof, not promises
See what was accepted, what it cost, and how it was checked.
Starport turns agent work into a receipt trail. Each accepted outcome has a request, action log, evidence package, reviewer decision, and thirty-day follow-up status.
Current sample
The denominator is visible.
Counts include model use, infrastructure, review, rework, and customer acceptance. Internal drafts are not counted as accepted outcomes.
Receipts that could be replayed from request to evidence package.
Mean time between human interventions across the rolling thirty-day window.
Accepted work later patched, reverted, or manually rescued.
Receipt anatomy
A receipt follows the work from request to acceptance.
The point is not a prettier activity log. The point is to let a reviewer reconstruct the decision: what was requested, what changed, which checks passed, who accepted it, and what happened later.
- Request
Customer asked for the billing export to include invoice status, workspace, owner, and audit notes.
- Plan
The agent opened the ticket, mapped the export path, and listed the exact files and tests it expected to touch.
- Action
The change was applied to the export builder, table header, and CSV regression fixture.
- Evidence
Build, focused test, and export snapshot were attached before review.
- Acceptance
Reviewer approved the ticket after replaying the export with a seeded workspace.
Replay path
A third party can inspect the work without private trust.
Sensitive customer content can be redacted, but the chain stays legible: request, action, evidence, review, cost, acceptance, and reversal status.
- 01
Open the accepted outcome.
- 02
Read the request, owner, date, and acceptance rule.
- 03
Replay the action log against the linked evidence.
- 04
Check reviewer notes and any customer edits.
- 05
Record whether the outcome still passes thirty days later.
Cost accounting
Cost per accepted outcome includes the cleanup work.
Starport does not hide human review, rework, escalation, or infrastructure outside the denominator. A cheaper outcome only counts when the customer accepts it and the receipt remains replayable.
Thirty-day follow-up
Accepted work is still watched after approval.
A reversal is not hidden as support noise. It stays attached to the original accepted outcome, with the patch, reviewer, and customer impact recorded in the same receipt trail.
Week 1 7.4h 31 accepted
Week 2 8.9h 37 accepted
Week 3 10.2h 41 accepted
Week 4 11.6h 42 accepted