span: scope the crossing refusal and reuse it for held time #25
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "land/locus-consumption-surface"
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?
A trace is a role, not a process, so concurrent work under one trace crosses without nesting as a matter of course. The refusal is now scoped to the crossing window and reported as a
tangledrecord; on a real report that turns zero output into eleven declarations at a cost of 302 spans out of 196197. A third inspect mapping,held-time-nanoseconds, runs the same derivation, so both surfaces refuse the same crossings.