slots: refuse rather than warn #131
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "land/task/santi-slot-refusal"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
slots: refuse rather than warn
Pressure delivered as information did not carry this. A reminder that
reached the soul inside the turn, naming the share consumed and the bytes
still free and growing more urgent as it went, produced one late
compaction after two earlier bands passed unanswered. An action that
arrives late and unreliably cannot be what a runtime depends on, for the
same reason nothing depends on anyone remembering to free memory.
So the limits refuse. A compaction whose summary exceeds a slot is not a
compaction but a copy, and says so. A compaction that would open a slot
beyond the ceiling is refused unless it absorbs, which leaves exactly one
legal move and leaves the choice of what survives where it belongs. And
while either ceiling is exceeded, ordinary calls are refused outright:
the soul stays inside its turn, holding an error that names the only way
forward, rather than being thrown out of the context in which it could
act.
Occupancy is read through the same function the audit reports, so a
stated occupancy and an enforced one cannot disagree.
Two things this leaves. Every refusal wording had to be classified before
it could reach its caller, because an unclassified message still defaults
to an internal fault that the caller may not read; that default remains
the reason such defects appear. And a strand can now sit in violation
without noticing until it acts, which is intended: the block is a
condition of working, not an alarm.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com