# concurrency
This home projects declared interleaving explorations into ordinary Rust at the declaration site.
An adopter names a physical harness path and a set of explorations whose budgets and generation lineage are fixed by the declaration.
Those authored facts become canonical compiler content in authored order, so changing the destination or an exploration's declared meaning changes the projection the compiler is asked to produce.
The strand set and transition contract stay at the generated call boundary.
They are living values owned by the adopter, and putting either into this grammar would duplicate meaning that belongs to the calling target.
## The crossing
The projection leaves as one module of generic exploration functions.
Each function asks the harness's public constructors to inform the declared values, runs the harness exploration road, and returns both the reading and the conclusion that road earns.
The reading remains the owner of schedule evidence and replay material; the conclusion remains ordinary report vocabulary.
The physical harness binding is declared input because this projection compiles where it stands.
A dependency alias and a facade re-export therefore cross through the same grammar without a package name hidden in the renderer.
## The boundary
This home owns the declaration grammar, its canonical content, and the destination vocabulary the generated Rust spells.
It does not own name admission, exploration bounds, schedule semantics, transitions, or verdicts.
Values that only the harness can judge reach its public guards and return the harness's typed refusals without being reinterpreted here.
No thread, clock, scheduler backend, or subject policy enters this projection.