Files
zeekayandHanzo Dev 20ccbfd011 a reading of the bank expires, and memberships name a person
The cash breaker could not be armed safely and could be billed around.

funding: a State that stops being refreshed went on being the answer
forever, because nothing here aged it. The package doc has always named
two unknowns — never published, and the day rolled over — but only the
first could be seen, so a reading captured at the ceiling would refuse
every paid request until the process restarted. State.Until lets a
reading expire and Current returns the zero State once it has, which is
the same ALLOW every other unknown already lands on. Refuse stays a pure
function of what it was told; only the accessor that decides what is
known consults a clock. An unset Until never expires, so the publisher
that exists today is unchanged.

iam: the machine inference reads a shape — the principal's name equals
its audience — and assumed a person could never reach it. A person can.
The audience is the app's client id, those client ids are the app names
(hanzo-cloud), and usernames are ^[a-z0-9][a-z0-9._-]{0,62}$ with no
reserved list, so signing up as hanzo-cloud makes name == aud on an
ordinary person's token. That token typed as a machine, and Payer's
machine branch pays from the org — in the signup org, the difference
between a wallet that starts at zero and the platform pool. IAM already
signs the distinction: every person carries a membership set seeded with
their home org, a client-credentials token carries none, and cloud
already reads exactly that (authz.Claims.Machine). The inference now
defers to it, so the two readers agree rather than disagree. A stated
class still wins outright.

Both are pinned by tests that fail without the change: the breaker
refuses a funded caller at the ceiling and before the balance read, a
stale reading admits again, and a colliding username keeps its own
wallet.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-14 08:01:01 -07:00
..