nx_director_pipeline.nx

nx_director_pipeline.nx -- end-to-end demonstration: the substrate IS the director. One pure NishiLang program walks the canonical pipeline: 1. allocate a multi-stage arc (a "day-as-a-movie" event) 2. for each stage, resolve into a DirectorsNote (the per-moment decision the director hands to the crew) 3. simulate a "render outcome" by writing per-element survival verdicts into a SurvivalReport 4. aggregate -> PreflightTier (GOOD / DRIFT / BROKEN) 5. count session totals + emit a final director-summary verdict No Python, no service layer, no subprocess. Per the arc-and-moment- are-king cardinal: arcs + moments live in NishiLang, not in glue code. Per the graduated-intervention cardinal: any MISSING -> BROKEN (regen with corrective phrasing) any PARTIAL (no missing) -> DRIFT (ship + log trend, NO regen) any UNMEASURED (rest ok) -> DRIFT all SURVIVED -> GOOD (ship + archive as exemplar) genealogy_id: kurosawa_director_centric + jenkins_pipelines lineage_id: substrate_native_director