You are @you on GitHub. Your receipts go to Payments at Acme (the demo company).
- Write, done
- Sign, next
- Send
What did you get done this week?
Built out key financial features and docs while cracking settlement batching
Built 4 things and figured out 1 problem. 5 AI sessions, $128 (Codex $125, Claude Code $2.16).
Written privately by 0gm-1.0-35b-a3b-sia on 0G, TEE verified.
Check it yourself
Each link opens the place where the record lives- 0G
The private AI that wrote this week ran in a hardware enclave
0G's TEE check of the providerOpens here
What you got
5 items, $128- BuiltTeam spend dashboardidea to code 37m · code to commit 57m · PR in 5m · merged in 34h$10.60
- BuiltAPI quickstart docsidea to code 38m · code to commit 2h · PR in 13m · merged in 15h$60.58
- BuiltCI cache implementationidea to code 17m · code to commit 1h · PR in 13m · merged in 38h$31.05
- BuiltCover payout edge casesidea to code 27m · code to commit 47m · PR in 11m · merged in 2d 5h$23.14
- Figured outSettlement batching logic$2.16
- Built $125
- Figured out $2.16
Pull requests4 PRs, 4 merged. Always included when you send your receipt
- docs: API quickstart$60.58acme-demo/payments-api#129, merged
- chore: CI cache$31.05acme-demo/web-app#130, merged
- test: cover payout edge cases$23.14acme-demo/infra#132, merged
- feat: team spend dashboard$10.60acme-demo/web-app#131, merged
Each one opens on github.com.
How this was writtenPrivate AI on 0G, 1 private AI call
Written by 0gm-1.0-35b-a3b-sia on the 0G Private Computer, in private mode: only providers running the model inside a TEE could answer, and every answer's TEE signature was checked.
The requests reach 0G over HTTPS through its router and are not end-to-end sealed today, so the router could read them in transit.
- Each session went in as a private digest: what you asked, what the AI said at the end, tool counts, the GitHub outcome and the cost.
- The AI answered with a category and a short title. Only those are kept, never the prompts.
- One more call saw only the titles and merged them into this list and its one sentence.
- 5429f81d-9ff1-4de2-813c-5264fa55b3db
Where money leaked1 tip
- No obvious waste this period. Most spend landed in shipped work.
Cost by difficultyCompared with your team
Work is only compared with work of the same difficulty, never across people.
| Difficulty | PRs | You, per shipped change | Team median |
|---|---|---|---|
| 2 | $40.38 | $73.59 | |
| 1 | $23.67 | $18.48 | |
| 1 | $37.93 | $25.43 |
How the week wentIdea to merged in 38h
Typical time between steps, from log and GitHub timestamps. No AI involved.
- 1. Idea to code32mover 4
- 2. Code to commit1hover 4
- 3. Commit to PR12mover 4
- 4. PR to merge36hover 4
From idea to merged: 38h typical, over 4. Time with the AI before writing code: 3h.
Pull requests
4 merged of 4 opened.
AI cost per shipped change (merged PR or push to main): $31.34
Where the money went
- Shipped $125
- Learning $2.16
- In progress $0.00
- Wasted $0.00
Waste, by reason
- Plans nobody acted on0
- Left on the AI's question0
- Went in circles0
- Code that never shipped0
- Answers stopped midway0
What the categories mean
- Built
- Made something new that works: a feature, page, tool or script.
- Fixed
- Fixed a bug or something broken.
- Figured out
- Understood or diagnosed something: how it works, why it fails.
- Researched
- Compared options, read docs or the web.
- Wrote
- Docs, posts, specs, emails or scripts in words.
- Planned
- Designed or planned the work.
- Wasted
- Went in circles or produced nothing usable.