archetech / archon / 34721381104

95%

push

github

fix(gatekeeper): Resolve the controller at the time an operation arrived (#1134)

An asset operation's controller was resolved at proof.created, a value
the signer chooses. A holder of a rotated-out key could date an operation
before the rotation, select the document that still listed the retired
key, and go on modifying every asset the agent controls. Demonstrated
against a running gatekeeper before the change.

The controller is now resolved at the time the operation entered the
network: now for a direct submission, the block time on chain import, the
stored event time on replay. Historical operations still reach the key
that was current when they were made. One helper per port states the
rule; every verification path passes the time it knows.

Event times are ordered as instants, not strings, so an offset time does
not fork the two ports.

Closed for chain-anchored registries and direct submission. Local and
hyperswarm registries have no signer-independent clock (#1135), and
same-batch operations share a time so intra-batch ordering needs the
ordinal (#1136); both are documented in scheme 5.8 and filed.

Closes #1131.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GYGMfX3foBcVqP7AQNXjWj

4168 of 4792 branches covered (86.98%)

Branch coverage included in aggregate %.

9 of 9 new or added lines in 1 file covered. (100.0%)

8808 of 9246 relevant lines covered (95.26%)

773.48 hits per line