carlos / platform Public

OUTSTANDING item 1 records the replicator's third build

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

claude 3 weeks ago c86276949a423fc8960ea64945b32ac22f025d1f parent 9480fe3

1 file changed, +1 −1

implementation/carloku-paid-launch/OUTSTANDING.md +1 −1

CI passed — run details

diff --git a/implementation/carloku-paid-launch/OUTSTANDING.md b/implementation/carloku-paid-launch/OUTSTANDING.md

index a7df8a303..fe90ff0b1 100644

--- a/implementation/carloku-paid-launch/OUTSTANDING.md

+++ b/implementation/carloku-paid-launch/OUTSTANDING.md

@@ -32,7 +32,7 @@ Each is concrete. None is waived.

### Meters (the complete metered model cannot invoice until both are proven)

-1. **Replication writes (`durability_writes_1k`) cannot be proven on any box.** The external replicator writes outside the ledger. Path A (scoped attestation) was built, reviewed in round six, and cannot prove an exclusive writer; it is off this branch and parked on `feat/carloku-scoped-attestation-20261001`. Path B (the platform's own replicator as the only writer) is **partial, unwired**, on `feat/carloku-metered-replicator-20261001` (`f4fe6f2b`, on the forge; the full local gate passes on it; first review: both reviewers rejected it, on an owner resolved once and never re-checked and on paths compared as text, among others. Both of those are fixed since: ownership is decided on the file, a tenant's link is refused, shadow state left the tenant's directory; and ownership is read under the registry's change witness, with every request refused once the registry changes. Five of the P2 findings are fixed or partly fixed too (the store kept private, unclaimed databases named, unreadable directories refused, platform identities the ledger accepts, the fleet's recovery window). None of the fixes has been read by a reviewer, and the rest is open, see `DISPOSITIONS-metered-replicator.md` on that branch): a litestream store whose every replica client is metered with no unmetered fallback, an owner for each database the box replicates, and a fleet store that refuses anything it cannot meter, each with tests. **Absent**: the agent wiring that binds those meters to the box's ledger, a restore path that does not shell out to the external binary, the unit change, moving the replica credentials so nothing else on the box holds them (the unit runs as the same user as the agent today), and any attestation. Until all of that exists and is approved for a box, this meter is incomplete every month and nothing is invoiced.

+1. **Replication writes (`durability_writes_1k`) cannot be proven on any box.** The external replicator writes outside the ledger. Path A (scoped attestation) was built, reviewed in round six, and cannot prove an exclusive writer; it is off this branch and parked on `feat/carloku-scoped-attestation-20261001`. Path B (the platform's own replicator as the only writer) is **partial, unwired, rejected at both of its reviews**, on `feat/carloku-metered-replicator-20261001` (`9480fe3f`, on the forge; the full local gate passes on it). Its second review found the ownership fence built after the first did not hold: a refused request was still sent, and the registry witness was moved by the replicator's own writes. A third build, not yet reviewed, makes the two changes that needed: a request gate in `internal/lease` that stops an attempt before it is sent, and an ownership generation in the registry that only ownership moves; with them a fleet that holds every recorder's days in doubt and watches without a request, one strict inventory with file checks (one name, ordinary siblings, no link or mount, the tree owner's, under a platform directory) and a second look on a timer, and shadow state made private before litestream can make it. Still open there: a swap after a look and before litestream's next open by path (needs litestream to open beneath a pinned root), a process dying between a change and the rebuild, the prefix-lineage and shrink guards, and that any tenant can stop a rebuild for the box. `DISPOSITIONS-metered-replicator.md` on that branch has every finding and what each build did about it. What is there: a litestream store whose every replica client is metered with no unmetered fallback, an owner for each database the box replicates, and a fleet store that refuses anything it cannot meter, each with tests. **Absent**: the agent wiring that binds those meters to the box's ledger, a restore path that does not shell out to the external binary, the unit change, moving the replica credentials so nothing else on the box holds them (the unit runs as the same user as the agent today), and any attestation. Until all of that exists and is approved for a box, this meter is incomplete every month and nothing is invoiced.

2. **Store transfer (`store_egress_gb`) has no source.** No Cost and Usage Report export exists on the account. It needs the scoped infrastructure approval, a first real delivery, an IAM principal inventory in the AWS provisioner (not built), and the bucket ownership attestation for stores that already exist (designed, not built).

3. **A store's partial first hour** with a charged line holds the month, and nothing releases it. It holds by default and nobody is asked to waive it. What can release it is evidence: an operator door that records, for one bucket-hour, who is shown to have owned it and on what evidence, which the fold then honours. **Partial, unwired into this branch**, on `feat/carloku-bucket-hour-evidence-20261001` (`b50f29bc`; code at `58c1870c`): the record, the fold change and three operator API doors, with tests and mutation checks. It accepts only the hour a complete ledger began vouching in and only the owner that ledger names. The full local gate passes on it. First review: Astra rejected it, Opus accepted with fixes. Both confirmed that through the fold it releases nothing but that hour for that owner. Both also found that the evidence is free text that the same operator records and that stands at once, which in practice is a waiver: what counts as evidence, and whether a second person must approve it, needs Paul's ruling (approval J) before more is built. Nothing fixed yet (`DISPOSITIONS-bucket-hour-evidence.md` on that branch). No CI run, no CLI verb, and its operator-facing sentences are unreviewed.

4. **A box's first minutes** before its ledger opened hold that day for everyone. Same as item 3: it holds by default, and the release is an operator evidence door, not a waiver. **Absent**.