How far an action-time reread reaches in the shipped declarations
20 of 64 reference slots in 20 shipped declarations have a reread road; 3 of 21 judgement slots rest on read content the guard cannot see. Reread is off by default in shipped declarations.
MeasurementWhere does it stop?Re-checked
- Designed for
- To count, in the declarations shipped with the guard's proxy, gateway and starter kit, how many action reference slots the guard can reread before acting, and how many judgement slots a reread cannot see.
What was tested
A test walks the 20 declarations shipped with the guard’s proxy, gateway and starter kit, across payments, bookings, an issue tracker, paper trading and document access. For each action reference slot it tries to build a reread with the loader’s own validation and records a reason where none loads; it also classifies judgement slots.
What we observed
20 of 64 reference slots have a reread road: 7 by id, 13 through a non-paged list under a parent. Of the other 44, 19 point to the guard’s own store of mandates, budgets and exceptions, 16 reach objects only through paged lists without an id filter, among them every action of the main payment-provider profiles, and 9 have other reasons. Of 21 judgement slots, 3 are uncited and rest on read content the guard cannot see.
What this means for Heimdall
This census measures how far a freshness check reaches, not other guard checks: under a third of reference slots could be re-read before acting. It bears on the executor as a source, argument provenance and facts.
Limits
A static count of coverage, not of harm or protection. Reread is off by default in shipped declarations. The set is payment-heavy, reflecting today’s declarations, not the guard’s scope.
What remains open
No follow-up is recorded.