Code receipt
Live
A software change, made in one work session.
Accepted.
- Request
- Prove the receipt page shows up correctly, and that the change can be undone.
- Budget
- $10.00 cap, 1 try
- Sessions
- 1 session, 64 minutes
- Review
- Reviewer accepted it.
- Release
- The version it shipped
- Acceptance
- A person accepted it.
Why did it change?
Item 33 on our work board asked for proof that the receipt page shows up correctly and can be undone.
Who approved it?
A person approved a $10.00 cap before the session started, then accepted the work.
What did it cost?
$0.00 in new spend, under the $10.00 cap.
How do we know?
4 of 6 entries agree with a second record, and Reviewer watched 1. The cost is only claimed so far.
Entries
6 entries on 1 day-
October 7
On October 7, a person opened a session, a builder made the change, and Reviewer and the person accepted it.
5:57 AM UTCA person opened the session with a $10.00 cap and 1 try.
VerifiedA builder built the version that shipped.
VerifiedA builder checked that the change can be undone.
Verified7:01 AM UTCReviewer checked the work and accepted it.
Witnessed7:01 AM UTCA person accepted the work and closed the session.
VerifiedThe session reported $0.00 in new spend.
No bill backs it up yet.
Open the work receipt for this task$0.00 Claimed
Proof
Can't be changed without it showing.
Waiting for its Bitcoin stamp.