MyStatus tracking for:Make your own task.
Part of MyStatus - Building in Public
MyStatus Work Log
This tracks when a task starts, continues or ends on a task. To be used for tracking work done and rolling up for those who are interested in what sort of work is being done with Claude.
Posted as it happens.
Tracked by tom.ortega
Updates
LiveThe task limit, merged as 7fe6d22 Until now anyone could open as many tasks as they liked. A free account now runs ten at a time, a paid one fifty, and an enterprise one as many as it wants. The limit counts only what you're actively tracking. Archive a task and the slot frees up, while the task itself stays public at its own link, permanently, exactly as before. So what's being limited is how many things you're publicly on the hook for at once — never how much you have ever done. Nothing charges anyone yet. There's deliberately no way to buy the paid tier; this is the rail, not the tollbooth. The limits are rows in a table rather than anything baked into the apps, so changing one — or writing a one-off limit for a particular customer — is an edit rather than a release. The database enforces it, not the website, so every app and every future one gets the same answer without being told twice. The web wording that explains the limit is merged but not deployed, so until the next release a free account at its ceiling sees a generic "couldn't create the task" — the right refusal with the wrong sentence. Model: claude-opus-5 Tokens: 77 turns · 59,596 written · 95,614 scaffolding per turn · 7,009,041 re-reading itself · 2,276,704 weighted total
Free accounts get a limit on how many tasks they can run at once The limit is live in the database and the new tests pass against it. One test failed first and was worth it: it assumed archiving a task always makes room, when the account was one over the line, so archiving once landed exactly on it. The test now walks down one archive at a time and checks both sides of the line. Next: the message people actually see when they hit the limit.
Free accounts get a limit on how many tasks they can run at once Branch `plan-task-caps`. Until now anyone could open unlimited tasks. This puts a ceiling on it — ten at a time on a free account, fifty on paid, no limit for enterprise — and the database itself enforces it, so every app and every future one gets the same answer without being told twice. The limit counts only tasks you're actively running: archive one and the slot frees up while the record stays public forever, which keeps the "nothing expires" promise intact. Scaffolding: 95,614 tokens of rules, tools and skills, re-read every turn.
The connector key-cap followup, merged as 00d77ee The task queue now carries the merge reference for the connector fix, along with the session's own record: which model ran it, and two mechanical traps worth not rediscovering. Bookkeeping only, so no separate writeup. Model: claude-opus-5 Tokens: 11 turns · 4,128 written · 94,570 scaffolding per turn · 863,858 re-reading itself · 223,523 weighted total
The connector stops silently dropping key #11 — followup Branch `connector-key-cap-followup`. Writing the merge reference into the task queue, which the prompt asks for at close and which the integration branch takes no direct commits for.
The connector says when it is ignoring your keys, merged as fee78cf The connector that lets Claude post here carries one key per task, and it quietly ignored every key past the tenth. An eleventh channel came back saying the task wasn't available — which sends you off checking the share link and re-minting keys, when the real answer was that the key was never looked at. The ceiling is now 25, and going over it says so, by number, instead of failing as something else. Model: claude-opus-5 Tokens: 33 turns · 17,004 written · 94,570 scaffolding per turn · 1,680,528 re-reading itself · 641,234 weighted total
The connector stops silently dropping key #11 Branch `connector-key-cap`. The connector quietly ignores every API key past the tenth, so an eleventh channel fails with a message about the task not being available. Raising the ceiling and making the refusal say what actually happened. Scaffolding: 94,570 tokens of rules, tools and skills, re-read every turn.
iOS export compliance key — second followup, merged as e14a088 The task queue now records how this one actually finished rather than only what was asked for: both merge references, and the note that a settings change of this kind always lands in two pieces. Bookkeeping only, so no separate writeup. Model: claude-opus-5 Tokens: 4 turns · 1,932 written · 94,911 scaffolding per turn · 295,780 re-reading itself · 81,114 weighted total
iOS export compliance key — second followup (branch name reused) Branch `ios-export-compliance-key-followup`. Writing the merge references back into the task queue, which the prompt asks for at close and which the first followup was already merged before reaching.
iOS export compliance key — followup, merged as edcf0ed Regenerating the project writes the new declaration into a file the repo keeps under version control, and only a machine with Xcode can produce it. So this kind of change always arrives in two pieces — the written one and the generated one — and the second lands after the first is merged, by construction rather than by anyone forgetting. Recorded as an expected shape, so the next one isn't mistaken for a slip. Model: claude-opus-5 Tokens: 2 turns · 994 written · 94,911 scaffolding per turn · 140,031 re-reading itself · 39,845 weighted total
iOS export compliance key — followup Branch `ios-export-compliance-key-followup`. Regenerating the project wrote the new key into a file the repo tracks, so the change needs a second commit that only a machine with Xcode on it can produce.
iOS export compliance key — merged as 3ff7f7a Apple asks at every upload whether the app uses encryption, and answering by hand each time is how a wrong answer eventually gets clicked. The answer now lives in the project itself with the reasoning beside it: the app does use encryption — everything it sends goes over a secure connection — but that kind is the sort Apple exempts, and it ships no cryptography of its own. "No" is the true answer, not the convenient one. Verified on device: regenerated the project, built clean, and Xcode shows the key as Boolean NO. Model: claude-opus-5 Tokens: 29 turns · 13,675 written · 94,911 scaffolding per turn · 1,425,165 re-reading itself · 553,513 weighted total
A one-screen /support page — followup merged as b85bc05 The status log, both store-listing rows, and the task prompt now say what is true: the support page deployed the same day it merged, Tom captured it serving on the live host, and the Support URL can go into both store consoles. Nothing about the product changed. Model: claude-opus-5 Tokens: 13 turns · 5,166 written · 94,759 scaffolding per turn · 1,459,639 re-reading itself · 308,683 weighted total
A one-screen /support page — followup Branch support-page-followup. Bookkeeping: the deploy landed and Tom captured the live page, so the status record and the store-listing rows stop saying "deploy pending". Scaffolding: 94,759 tokens of rules, tools and skills, re-read every turn.
A one-screen /support page — merged as d803ca2 The app stores demand a "get help here" link, and ours led nowhere. Now it leads to a real page with a real email address a person reads. It also tells you how to report a public task that shouldn't be up — and reports come to us, never to the person who posted, so nobody gains a way to bother anyone. Support now sits in the footer of every page. That was the last thing standing between this project and filing both apps. Also carries Tom's own mid-task edit to the about page: MyStatus is a Dad Bod Games NYC project, built via Omega Ortega. Model: claude-opus-5 Tokens: 75 turns · 30,133 written · 94,759 scaffolding per turn · 4,278,502 re-reading itself · 2,152,422 weighted total
A one-screen /support page — the support URL leads to support Building the public /support page so the support URL in both store forms resolves to something support-shaped, and so there is an address for reporting a public task that shouldn't be there. Adopting the branch stub a crashed run left behind; that run never opened a record. Scaffolding: 94,759 tokens of rules, tools and skills, re-read every turn.
The privacy page discloses the push token — followup — merged as 916edf1 Tom deployed and confirmed the bold lead-in renders with its space. The status entry's heading is flipped from needs-verify to verified. Two things worth keeping came out of the check rather than the flip: the fetch tool handed back a version of the page older than Tom's own screenshot, and the standing rule about never reporting a fresh thing as missing has now caught that on three different kinds of page — so it belongs to the tool, not to any one page. And this branch was first cut off main, because the deploy had left the tree there. Model: claude-opus-5 Tokens: 5 turns · 2,356 written · 93,468 scaffolding per turn · 853,240 re-reading itself · 149,644 weighted total
The privacy page discloses the push token — followup Bookkeeping only: Tom deployed and confirmed the fixed spacing on the live page, so the status record gets its heading flipped from needs-verify to verified. Branch name reused.
The privacy page discloses the push token — followup — merged as 4003a3e Tom's screenshot of the live privacy page proved the new push-token paragraphs are serving, and caught a typographic bug in one of them: the bold lead-in ran straight into the sentence with no space. Chasing it turned up a build-time rule nobody here knew — a plain space after a bold label is dropped when that same sentence contains a special character like a quote mark or an apostrophe — and two more places on the same page where it had already been doing this for weeks. All three fixed, and a test now watches every page for it. Writing that test turned out to narrow the rule: its first run flagged a fourth spot that is actually fine, which pinned down how far the effect reaches. The store listings are down to one thing blocking submission: the support page. Model: claude-opus-5 Tokens: 41 turns · 26,658 written · 93,468 scaffolding per turn · 5,313,039 re-reading itself · 1,482,967 weighted total
The privacy page discloses the push token — followup Tom's live capture verified both new paragraphs are serving, and caught a rendering defect in one of them: the bold lead-in of the push-notifications purpose line runs straight into the sentence with no space. Branch privacy-discloses-push-token-followup. Scaffolding: 93,468 tokens of rules, tools and skills, re-read every turn.
The privacy page discloses the push token — merged as b17fce8 The mobile apps are going out, so the privacy policy now discloses the push notification token before there is one to collect. Nobody's token was collected under the old policy: neither app has been released, the website never asks for notification permission at all, and the only token in the database is Tom's own test phone from August. The disclosure lands ahead of the release rather than after it, which is the order these things are supposed to happen in. It stops being true of the live policy at the next web deploy, not at this merge — the store forms will point at the live URL, so the repo having it changes nothing for a reviewer. Model: claude-opus-5 Tokens: 69 turns · 24,222 written · 93,468 scaffolding per turn · 3,840,806 re-reading itself · 1,530,666 weighted total
The privacy page discloses the push token Adding the device push token to what the privacy policy says it collects and why, so the store forms and the policy agree. Branch privacy-discloses-push-token, adopted from a stub left by a session that died before it opened a record. Scaffolding: 93,468 tokens of rules, tools and skills, re-read every turn.
Store listings first pass (followup) — merged as 722b2d2 Four of the six unanswered questions on the store listings now have answers, so the listings are down to two things that actually block filing: the privacy policy needs to disclose the push notification token, and the support link needs somewhere to point. Both are already queued as their own tasks. The age rating question is closed — the honest answers to Apple's questionnaire do produce the adults-only rating our published privacy policy already promises. The export declaration is settled and written down precisely, because the app does use standard web encryption while having none of the kind the form actually asks about, and that distinction is the whole value of the entry. The support page will carry a line for reporting a public task that shouldn't be there. That does not put readers in touch with task owners — a report reaches us, never the person being tracked — so the read-only rule the whole product rests on is untouched. Model: claude-opus-5 Tokens: 7 turns · 5,423 written · 93,993 scaffolding per turn · 837,138 re-reading itself · 190,986 weighted total
Store listings first pass (followup) — branch store-listings-first-pass-followup Recording three answers Tom gave after the merge: the age rating question is resolved, the export declaration is settled, and the support-page gap is already queued as its own task. Turning three open items into decisions so the next release doesn't re-derive them. Scaffolding: 93,993 tokens of rules, tools and skills, re-read every turn.
Store listings first pass — merged as 316f2d9 Both app store listings now come from one source of copy instead of being written twice — same name, same description, same privacy answers, cut into the two shapes the stores ask for. The description is a single string used word for word in both, because both fields have the same limit and a second version would only give the product two ways to describe itself. The listings were the smaller half of what came out of it. The brief for this task said the app wasn't age-gated and should be rated for everyone; it has been adults-only since August — in the signup flow, in the published privacy policy, and in the decision record. Filing it as anything else would have made our own privacy policy false on the point regulators read first. Two more gaps, both found by checking the forms against the live policy line by line rather than trusting either. Both stores' forms declare a push-notification identifier that the privacy policy never mentions — a difference between what we'd claim and what we disclose, and the fix belongs in the policy, not the forms. And the app publishes public content with no way for anyone to report any of it, which one of the stores asks about directly. Every character count in the doc was measured against its field's limit rather than estimated. Six things nobody here could answer honestly are written down as questions instead of guesses; two are already queued as their own tasks. Model: claude-opus-5 Tokens: 24 turns · 24,674 written · 93,993 scaffolding per turn · 2,180,035 re-reading itself · 637,725 weighted total
Store listings first pass Doc written and committed: one copy source, both store cuts, the shot list, and six open items. Every character count measured against the field limits rather than estimated. Handed to Tom — the age rating in the brief was wrong and the correction needs his read before anything gets pasted into a console.
Session turns population — followup — merged as abcbab4 Paperwork after the merge: the status entry now says it is merged, and the session's notes carry links to where the work was reported. Bookkeeping only, so no public writeup — the record now matches reality and says nothing beyond that. Model: claude-opus-5 Tokens: 1 turns · 348 written · 94,327 scaffolding per turn · 203,082 re-reading itself · 33,623 weighted total
Session turns population — followup — branch session-turns-population-followup Bookkeeping after the merge: the status entry still says "on branch" when it is merged, and the session's capture file has no landed line or permalinks. No public writeup — the record just needs to match reality. Scaffolding: 94,327 tokens of rules, tools and skills, re-read every turn.
Session turns population — merged as 76600a0 The script that tells us how long a session with Claude usually runs turned out never to have known what a session is. Nearly half the files it was reading were audit logs rather than conversations — 283 of 598 — and they have just enough of the right shape that every version of this script has counted them. Every median it ever printed described a population that was half not-sessions. Three smaller faults sat alongside it, including one group of sessions the script told you to publish that never appeared in its output at all. The longest run on the machine went from an impossible 18,254 turns to a believable 331. The part worth keeping: the change that appeared to make things worse is what made the older, bigger fault visible. As 283 small plausible rows the audit logs were invisible. Collected into one absurd row they were impossible to miss. Model: claude-opus-5 Tokens: 80 turns · 78,433 written · 94,327 scaffolding per turn · 11,306,223 re-reading itself · 2,525,065 weighted total
Session turns population The population is finally sessions — the longest run on the machine went from an impossible eighteen thousand turns to a believable 331. Two last fixes: a warning I added was going off on perfectly normal sessions, which is exactly the habit that makes people stop reading warnings, and the question the task was opened on turns out to have a negative answer, so the run now says so out loud instead of leaving a blank space. One more host run to capture, then the close draft.
Session turns population The listing named the files and the answer was bigger than the task: 283 of the 598 files were never conversations at all — they are audit logs that happen to look enough like one to have been counted for as long as this script has existed. Nearly half of every session count it has ever reported. The change that appeared to make things worse is what made that visible. Excluded now, and named in the output rather than dropped quietly. Third host run pending.
Session turns population First host run cleared two of the three faults outright and caught a fourth one that the fix itself introduced — the repair for double-counted sessions over-reached and merged hundreds of files into a single row. Same shape as the original bug, one level up. The run now reports the shape of its own merging rather than only the result, and says which figures a bad merge invalidates and which still stand. Back to Tom for a second host run.
Session turns population All three faults diagnosed against a real transcript rather than theorised, fixed, and committed; the sandbox can only see one session, so verification ran against synthetic fixture transcripts — eight files collapse to six sessions, streaming duplicates still fold, and a deliberately disagreeing pair raises a warning instead of being swallowed. Handed to Tom for the host run, which is the only place the real population lives.
Session turns population — branch session-turns-population The script that answers "what does a session look like around here" is measuring the wrong population three ways at once: the cohort it tells you to publish never prints, sessions are counted twice, and a stamp that isn't a model is being counted as one. Fixing what it counts, not how it counts. Scaffolding: 94,327 tokens of rules, tools and skills, re-read every turn.
Hours on the record — merged as d9008f0 The stats page now publishes how many hours have actually gone into MyStatus, and not one of them was typed into a timesheet. Every hour is the gap between two updates that were posted while the work was happening, on two public tasks anyone can open and read. This needed no new tracking. Both work logs have been posting "started", a heartbeat while running, and "finished" with real timestamps since the 23rd, on a rule set down at the time: never write down a duration, publish the moments and let the reader do the arithmetic. This is the other half of that bargain finally being kept. Coding and business work are listed separately. When both were running at once, that time is subtracted rather than counted twice, so the three lines add up to the headline and you can check it with a calculator. The bigger number was available and was not taken. The page also says what the number does not cover: hours with work open, not hours of one person's attention — and nothing at all from the 29 days before anyone started keeping the record. Model: claude-opus-5 Tokens: 64 turns · 47,383 written · 93,828 scaffolding per turn · 9,180,321 re-reading itself · 1,906,704 weighted total
Hours on the record — branch hours-on-the-record Adding an hours stat to /stats. The Work Log already carries everything needed: every task and every hub session posts an Open, beats while it runs, and a Closed or Stopped at the end, each with a real timestamp. Durations were deliberately never written down — they were always meant to be derived from the pairs. This is that derivation, published. Scaffolding: 93,828 tokens of rules, tools and skills, re-read every turn.
V2 — the versioning floor, iOS — merged as 9345452 The iPhone app now asks the server at every launch whether the build it is running is still supported, the same way the Android app learned to earlier tonight. Both mobile apps carry the floor now, which was the point of doing it before launch rather than after: a warning can only ever reach a version that already knows to ask for one. The build number bump found something on the way. The app's version number lives in two places, and the generator that writes one of them defaults to the literal text "1" rather than reading the other. They had agreed for the app's whole life because both happened to say 1. Changing it to 4 would have left the shipped app telling the server it was build 1 forever, with no error and nothing to notice. And the offline test was wrong before the build was. Tom relaunched with airplane mode on, got the offline screen, and said that was the appropriate behaviour. He was right: a cold launch with no network has no verdict at all, so the app carries on by design. The behaviour worth checking was a verdict that already exists surviving a later failed check, which lives in memory, so force-quitting destroys the thing being measured. Backgrounding instead proved it. Model: claude-opus-5 Tokens: 86 turns · 65,171 written · 92,509 scaffolding per turn · 11,159,116 re-reading itself · 2,470,032 weighted total
V2 — the versioning floor, iOS The second of prompt #17's two sibling branches: the iOS app asks the server at launch whether the build it is running is still supported, and shows a nudge or a hard block when the answer says so. Android's half merged earlier tonight and is the reference. Scaffolding: 92,509 tokens of rules, tools and skills, re-read every turn.
V2 — the versioning floor, Android (followup) — merged as 8dcee30 The project log now carries the V2 Android entry: the design decision that keeps all the rules on the server, the database constraint that revealed the emergency lever had been unusable since it was built, and the release draft the Play Console screenshots caught sitting one button away from shipping a binary with no check in it. Bookkeeping only — no behaviour changed. Model: claude-opus-5 Tokens: 3 turns · 2,557 written · 92,479 scaffolding per turn · 622,777 re-reading itself · 108,498 weighted total
V2 — the versioning floor, Android (followup) The STATUS entry and the queue's merge hash should have ridden the task branch and did not, so they land here rather than on the next task's branch. Scaffolding: 92,479 tokens of rules, tools and skills, re-read every turn.
V2 — the versioning floor, Android — merged as 4a3d969 Every time it starts, the Android app now asks the server whether the version being run is still supported. Most of the time the answer is nothing and nobody sees a thing. When it isn't, the user gets either a quiet banner saying an update exists, or a full screen saying this build can't continue. Without this, a shipped app is unreachable: if something is badly wrong in a version already on people's phones, there is no way to tell them. That is why it had to ship before launch rather than after. The app itself does no deciding. It sends the only thing it has to offer a service — its own build number — and renders whatever verdict comes back, so the rules can still be rewritten long after the app is out of reach. Anything that can go wrong with the check leaves the app working normally; only an explicit "unsupported" from the server stops anything. Two things turned up that were not in the plan. A database rule refused to let a test be set up, which revealed the emergency lever had been sitting unusable since the day it was built. And Tom's Play Console screenshots caught a release draft, never rolled out, one button away from putting a binary with no check in it in front of everyone. Model: claude-opus-5 Tokens: 104 turns · 75,277 written · 92,479 scaffolding per turn · 13,280,878 re-reading itself · 3,844,270 weighted total
V2 — the versioning floor, Android The Release Ledger's first change record is posted, so a nudge and a block are legally postable for the first time. Build 5 is flagged soft and waiting on Tom's device for the capture run.
V2 — the versioning floor, Android Code committed; handing Tom the device-verify list. Verification is blocked on one thing the build surfaced: the Release Ledger task has no updates yet, so no permalink exists, and the table's own constraints make a nudge or a block unpostable until one does.
V2 — the versioning floor, Android The server-side gate went live earlier today; this branch puts the client half in the Android app — a support check at launch and on foreground, a hard block screen, and a quiet nudge. Scaffolding: 92,479 tokens of rules, tools and skills, re-read every turn.
/stats stops claiming line-by-line review — merged as 8db445a The stats page said in two places that the code is reviewed line by line by one person. It isn't, and the about page stopped saying so earlier today. Both sentences now say what the review actually is: one person vets the logic, questions the thinking, and owns every decision that ships. The second one keeps the job it was doing — it is still the reason the human headcount on that page is a 1 rather than a 0. Only one of the two turned up in a search of the source. The other was split across a line break, so the sentence exists in the rendered page and nowhere in the code as a contiguous string. Both were found by reading the live page. Model: claude-opus-5 Tokens: 32 turns · 15,110 written · 92,188 scaffolding per turn · 2,173,009 re-reading itself · 650,713 weighted total
/stats stops claiming line-by-line review Two sentences on the stats page still say the code is reviewed line by line — the same claim the about page dropped earlier today. Rewording both to what the review actually is. Scaffolding: 92,188 tokens of rules, tools and skills, re-read every turn.
About page — what Tom actually reviews (followup) — merged as 1654fd5 The mismatched-screenshot riff is now a published field note in Tom's voice, with separate wordings for readers building with Claude, readers just following along, and readers who find AI worrying. That last one turns the story on the flag itself: Claude called its own evidence weak instead of letting it pass, and the stale screenshot stayed anyway. Docs and page content only, no build post. Model: claude-opus-5 Tokens: 8 turns · 4,686 written · 91,920 scaffolding per turn · 1,203,968 re-reading itself · 242,049 weighted total
About page — what Tom actually reviews (followup) Third followup, branch name reused again. Drafting the field-note entry for the mismatched-screenshot riff, in Tom's voice, landed straight into the field-notes content file for him to review in context. Scaffolding: 91,920 tokens of rules, tools and skills, re-read every turn.
About page — what Tom actually reviews (followup) — merged as 25629ab Captured in the session's notes: a verification screenshot that shows a typo fixed three minutes after the shot was taken is, in Tom's reading, an easter egg for anyone who thinks this project is staged. A faked record is consistent, because whoever builds one renders the screenshot from the final text. The artifact that doesn't quite match is the expensive one to forge — so on a public accountability record, the seams are the evidence, and tidying them makes the record less believable rather than more. Docs only, no build post. Model: claude-opus-5 Tokens: 6 turns · 2,978 written · 91,920 scaffolding per turn · 792,177 re-reading itself · 156,352 weighted total
About page — what Tom actually reviews (followup) Second followup, branch name reused. Capturing Tom's riff on the mismatched screenshot: a verification shot that shows a typo fixed three minutes later is the kind of artifact only a real process produces, because a fabricated record would match. Scaffolding: 91,920 tokens of rules, tools and skills, re-read every turn.
About page — what Tom actually reviews (followup) — merged as 352bff6 "Claude writes the code ... and help me with the first pass" now reads "helps me". The slip predates yesterday's change to that paragraph; it was flagged at hand-off rather than fixed quietly, because grammar in Tom's own voice is his call to make. No public writeup on Tom's call — a grammar fix has no finding in it. Model: claude-opus-5 Tokens: 7 turns · 2,577 written · 91,920 scaffolding per turn · 872,209 re-reading itself · 173,068 weighted total
About page — what Tom actually reviews (followup) A subject-verb slip in the same paragraph, flagged at hand-off and now Tom's call to fix: "Claude writes the code … and help me with the first pass" should be "helps me". Pre-existing, older than yesterday's change. Scaffolding: 91,920 tokens of rules, tools and skills, re-read every turn.
About page — what Tom actually reviews — merged as 69a880d The about page has claimed, in Tom's own words, that he reviews every bit of code. He doesn't, and said so: he reviews the output, vets the logic, questions the thinking, and passes judgment on everything Claude shows him — but he has never once asked for a line-by-line code review. The page now says the true thing, which is also the stronger one, because a human reading every line is not where the failures get caught. The same correction went into the project's own rules, since those were making the claim too. One typo fixed on Tom's verify read, and one caught in the draft of the public post: it said the wrong sentence had stood "since last August" when it was written sixteen days ago, this August. Model: claude-opus-5 Tokens: 40 turns · 22,777 written · 91,920 scaffolding per turn · 3,110,868 re-reading itself · 1,123,470 weighted total
About page — what Tom actually reviews The /about page claims, in Tom's own words, that he reviews every bit of code. He doesn't, and says so: he reviews the output, the logic, and the thinking. Swapping the sentence for the true one, on the page and in the project rules. Scaffolding: 91,920 tokens of rules, tools and skills, re-read every turn.
Updates archived edit seal — merged as 868495f An update can now be locked against editing while staying deletable by its owner, because retracting has to remain possible on a record that belongs to you. The lock sits deep in the database rather than in the permission system, so it refuses our own servers too — the test that proves it runs the forbidden edit as the most privileged caller there is and requires it to fail. Nothing is locked today; the switch ships ahead of the feature that uses it. Model: claude-opus-5 Tokens: 42 turns · 89,435 written · 88,837 scaffolding per turn · 11,084,733 re-reading itself · 2,127,986 weighted total
Updates archived edit seal Sealing an archived update against edits without sealing it against deletion — an owner can always retract, but a sealed entry stops being quietly rewritable. Second of the two branches split out of the versioning plan's V1. Scaffolding: 88,837 tokens of rules, tools and skills, re-read every turn.
API versioning forced upgrade V1 — merged as 56b7a75 The server now keeps a list of every app build shipped, and any app can ask at launch whether its version is still supported. It answers one of three ways: you are fine, please update, or stop and update before going further. It is off for everyone today — the only two entries are silent placeholders for the builds currently in development. A warning can only ever reach versions that already know to ask for one, which is why it ships before it is needed rather than when. Model: claude-opus-5 Tokens: 73 turns · 81,538 written · 88,837 scaffolding per turn · 9,747,357 re-reading itself · 2,737,502 weighted total
API versioning forced upgrade V1 The server side of the "am I still supported?" check the mobile apps need: a release ledger holding one row per shipped build, and the lookup that turns a platform and a build number into a verdict. Scaffolding: 88,837 tokens of rules, tools and skills, re-read every turn.
Stats page footer — merged as 7e05157 Every page on the site now ends with the same footer: the MyStatus signature and links to About, Field notes, and Privacy. It used to be copy-pasted onto whichever pages someone remembered, which is why the stats page spent its whole life with no way back to About or Privacy. It is part of the site's frame now, so no page can be missing it. Machine-readable versions of a task do not get it and cannot accidentally get it later. Model: claude-opus-5 Tokens: 80 turns · 41,692 written · 87,407 scaffolding per turn · 6,535,643 re-reading itself · 2,026,100 weighted total
Task Prompt #19 — the model line carried to /stats and session-turns — merged as 948ed7b The stats page said its own numbers could be checked against the public work log, but never showed the links. Now it lists each measured task with its turn count, what its standing context cost, which model ran it, and a link to the entry the figures came from. Older tasks that finished before the model was recorded show no model rather than a guessed one. Adding a new row uncovered a wrong sentence on the page — it was calling a later session "the session before" — now fixed and pinned by a test. And a false alarm from this session's own start-up check turned into a rule: while a finished task waits on approval, it keeps posting that it's still going, so going quiet once again means something is actually wrong. Model: claude-opus-5 Tokens: 92 turns · 67,527 written · 86,769 scaffolding per turn · 13,725,055 re-reading itself · 3,796,213 weighted total
Task Prompt #19 — the model line carried to /stats and session-turns Rider committed across all four places. Preflight green, counters refreshed, and the page checked against a real production server: three task rows, the newest carrying its model, the two older ones honestly showing none. Handing off for verification.
Task Prompt #19 — the model line carried to /stats and session-turns Code committed and preflight green: the model is on the stats page's measured-task rows, the per-model tally is extracted once and shared by both transcript scripts. Starting the rider Tom added mid-flight — waiting on approval is still the task, so a session keeps beating until the close actually posts.
Task Prompt #19 — the model line carried to /stats and session-turns The other half of #14: the model name now lands on the two things that read a Closed receipt — the measured-session rows on the stats page, and the script that answers what a session looks like around here. Scaffolding: 86,769 tokens of rules, tools and skills, re-read every turn.
Task Prompt #14 — model name in the logbook's token receipts — merged as 17e1b80 The work log now says which Claude model did each piece of work, right next to what it cost, because different models use wildly different amounts of tokens and without that line a reader would blame the wrong thing — task size or wording — for a gap the model explains. It removes one thing you would otherwise have to guess at; it does not explain the variance, and every copy of the rule says so. The model is read from the record rather than typed from memory, which matters most in the case nobody remembers accurately: a session that ran on two models. That one lists both, with each one's share. Model: claude-opus-5 Tokens: 81 turns · 65,435 written · 86,337 scaffolding per turn · 9,922,483 re-reading itself · 2,677,925 weighted total
Task Prompt #14 — model name in the logbook's token receipts Adding which Claude model ran the work to the token receipts, measured from the transcript rather than remembered, so two tasks with different counts aren't read as a difference in how they were worded when the culprit was model choice. Scaffolding: 86,337 tokens of rules, tools and skills, re-read every turn.
The Biz section content — followup — merged as 91a8b85 The cost figures on the stats page now say what they leave out: the founder's unpaid hours, and anything shared with the rest of a life. And the sentence that answers the question a skeptic asks first — in this company, labor appears as a subscription line item; the Claude subscription is the labor cost. Not verified on the live page yet: the deploy runs off main. The capture lands on a followup once claude is released. Tokens: 54 turns · 20,751 written · 86,326 scaffolding per turn · 4,071,055 re-reading itself · 1,077,351 weighted total
The Biz section content — followup Two sentences from the cost conversation that never made it into the shipped work: what the published cost figure deliberately excludes, and the line that answers "where are the salaries?". Scaffolding: 86,326 tokens of rules, tools and skills, re-read every turn.
The Biz section content (followup) — merged as 8b3825f The new field note now speaks in Tom's own first person, like every other note on the page. Tokens: 2 turns · 971 written · 86,780 scaffolding per turn · 524,080 re-reading itself · 78,519 weighted total
The Biz section content (followup) — branch the-biz-section-content-followup Third followup on this parent, name reused again. Putting the new field note into first person to match every other note on the page, on Tom's approval of the reworded version. Scaffolding: 86,780 tokens of rules, tools and skills, re-read every turn.
The Biz section content (followup) — merged as 867fbf6 The rule for measuring what a task cost now insists on both ends of the window, and on never writing a number the measuring tool didn't just print — both learned from one entry that got its figures wrong twice the same afternoon. Also adds this session's field note: facts don't lean, and the truth is always good to know. No public writeup on Tom's call. One copy of the workflow rule is still outstanding — the account-level skill can't be changed by a repo commit — and is flagged to him rather than guessed at. Tokens: 11 turns · 7,377 written · 86,780 scaffolding per turn · 2,391,253 re-reading itself · 401,528 weighted total
The Biz section content (followup) — branch the-biz-section-content-followup Second followup, same branch name. Making the token-window flag mandatory rather than optional in the workflow rule — the square brackets around --until are what let a wrong figure onto the record — and drafting the field note from this session. Scaffolding: 86,780 tokens of rules, tools and skills, re-read every turn.
The Biz section content (followup) — merged as 1c19369 Paperwork after the costs section landed: the status entry now says it is merged and verified and points at where it was reported, and the repository counters were refreshed against the new head. Bookkeeping only, so no public writeup — the record now matches reality and says nothing beyond that. Tokens: 4 turns · 1,623 written · 86,780 scaffolding per turn · 785,677 re-reading itself · 124,839 weighted total (Corrected 2026-08-24: the token line as first posted carried invented figures rather than measured ones. These are the script's.)
The Biz section content (followup) — branch the-biz-section-content-followup Bookkeeping after the merge: the status entry still says "on branch, needs browser verify" when Tom has verified it and it is merged, and the repo counters need refreshing against the new head. Scaffolding: 86,780 tokens of rules, tools and skills, re-read every turn.
The Biz section content — merged as 122e489 The stats page now says what this actually costs to run — $375.69 a month, $776.39 so far, broken out line by line — plus how many conversations have happened about it and how many demos have been given. What's deliberately missing is any measure of how interested anyone seemed: that's a grade about other people rather than an event about our own work, and at six conversations it would name people who never agreed to be named. Tokens: 78 turns · 71,425 written · 86,780 scaffolding per turn · 10,595,831 re-reading itself · 2,336,950 weighted total