1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
// Copyright 2024-2026 Jonathan Shook
// SPDX-License-Identifier: Apache-2.0
//! SRD-67 — parent-gated Polydat sub-context construction.
//!
//! This module is the typed entry point for constructing a Polydat
//! child kernel as a function of a parent kernel. It implements
//! the protocol from
//! [subcontext_construction.md](../../../docs/design/subcontext_construction.md):
//!
//! 1. Parent yields a builder via [`ScopeKernel::subcontext_builder`].
//! 2. Builder accumulates module matter (imports, exports, body
//! fragments, pull consumers) via [`SubcontextBuilder`].
//! 3. `finalize` closes the builder, validates imports against the
//! parent's exports, compiles the body into a [`ScopeModule`] with
//! a typed [`ScopeContract`].
//! 4. Parent spawns the child via [`ScopeKernel::spawn`] — the single
//! chokepoint where every cross-binding is resolved.
//!
//! ## Phase scope
//!
//! SRD-67's five phases have all landed: the typed surface
//! (Phase 1), the Rule 2 write-through rewrite in
//! [`SubcontextBuilder::finalize`] (Phase 2), the synthesiser
//! migrations (Phase 3), the `pub(crate)` seal on the legacy
//! construction primitives (Phase 4), and
//! [`SubcontextBuilder::add_result_bindings`] (Phase 5). The
//! design document is the implemented specification; "Phase N"
//! in this module's comments names the push that landed a piece,
//! not pending work.
//!
//! Cross-binding rules from SRD-67 §"Cross-binding rules" are
//! enforced at [`SubcontextBuilder::finalize`] and
//! [`ScopeKernel::spawn`]:
//!
//! * Rule 1 — import resolution at finalize.
//! * Rule 2 — export collision with `final` parent surfaces as
//! [`ContractViolation::FinalShadow`]; collision with `shared`
//! parent rewrites the body's `X := <expr>` into
//! `extern X: <type>` + `__write_X := <expr>` and records a
//! `WriteThroughBinding` on the artifact. Per-cycle eval
//! calls [`ScopeKernel::commit_write_throughs`] to fan values
//! through the parent's `SharedCell`.
//! * Rule 4 — coordinate routing handled by `materialize_wiring_from_outer`'s
//! IterationExtern input-kind.
//! * Rule 5 — closure-binding economy: unused imports surface as
//! finalize diagnostics rather than errors.
//!
//! ## Cross-crate boundary
//!
//! [`PullConsumer`] is defined as a trait so that `nbrs-runtime`'s
//! `ScopeFixture` can implement it without `polydat`
//! depending on `nbrs-runtime` (the crate dependency runs the
//! other way). Phase 1 ships a minimal trait shape — the names a
//! consumer wants to pull at cycle time — sufficient for the
//! activity-side `ScopeFixture::register_consumer` adapter to
//! absorb. The eventual seal of the SRD-32 `PullPlan` happens on
//! the activity side; the artifact only carries the requested
//! names.
//!
//! ## Walled-off invariant (SRD-67 Phase 4)
//!
//! Per SRD-67 §"Walled-off invariant", the legacy
//! cross-binding primitives `PolydatKernel::materialize_wiring_from_outer` and
//! `PolydatKernel::from_program` are `pub(crate)` after Phase 4.
//! External consumers must go through the typed surface:
//! [`SubcontextBuilder`] / [`ScopeKernel::spawn`] for child
//! construction, `instance_program` for parentless re-instancing
//! of a compiled program, `chain_kernel_under_parent` for top-
//! level kernel chaining.
//!
//! The compile-fail cases under `tests/ui/seal/` guard the seal: one
//! calls `materialize_wiring_from_outer` from outside the crate, one
//! calls `PolydatKernel::from_program`, and neither may compile. If
//! either starts compiling, the seal is broken and a Phase 4
//! invariant has regressed.
pub use ;
pub use ;
pub use PolydatMatterInner;
pub use ;
pub use ;
pub use ;
pub use ChildName;
pub use ;
pub use ;