Enter Piping development

At this basis, the published Piping loop says “none selected for a successor undertaking.” The revised entry uses the shared graph, closeout and memory arrangement, but its notice does not replace an in-flight run's accepted basis, repin a contract mirror or resume development/release. Establish the receiving loop's actual adoption and recover continuing work under its own pins. Piping loop · Piping development-loop notice

Use projects/chirality-piping, its project AGENTS.md, and init/dev-loop-init-prompt.md → loop/LOOP_INIT.md. Follow docs/PRD.md, execution/_Decomposition/SOFTWARE_DECOMP.md, applicable amendments, and execution/_DAG/_LATEST.md for the actual source basis. Older README or workplan selectors cannot displace the current entry. However, live instructions explicitly retain F-PIP-1 through F-PIP-4 by reference to the historical workplan's fence section; its old F-PIP-5 selection procedure is superseded. Historical location and live incorporation are different facts. Piping instructions · Piping loop

Recover the graph selected by the live loop, then its linked resume procedure, phase events, handoff, and later owner directions. When a summary and its events disagree, establish what actually ran and which candidate was examined before continuing. A selected reconciliation program retains its activation, method pins, evidence restrictions, and separate repair authority. Apply the selected run's actual testing instructions; the general development commands below cannot override a narrower audit brief. Piping loop · Reconciliation contract

The principal product surfaces are core/ Rust crates, apps/desktop/ frontend and native Tauri shell, and tests/ plus validation/ benchmarks, hand calculations, and witnesses. Deliverable production and evidence remain under the execution hierarchy and owning run locations. There is no project-root Cargo workspace manifest at this basis: select the affected crate manifest or the maintained runner's discovered set. Frontend build or browser testing does not establish a native packaged witness. Piping package manifest · Piping operational source map

The profile registers desktop-test, desktop-build, piping-pytest, evidence-sweep, and shared harness checks. Project npm scripts expose build:wasm:desktop, test:desktop, and build:desktop. Standalone desktop tests need the generated WASM when absent. Product-code merges additionally require the DEC-025 sweep on a clean candidate, applicable CI, and fresh independent review of the complete candidate. Select work and commands from the actual brief and instructions; a partial capability sweep cannot establish the full gate. Piping profile · Piping package manifest · Piping software checks

The domain boundary is critical. domains/piping-design/ includes vetted conceptual prose, but extracted equation artifacts remain unreviewed OCR/pdf2md material pending the maintainer's manual review. They may not supply authoritative equations for physics models, solver/kernel work, or analytical verification. Use the maintainer's vetted engineering sources and report review status. Keep software verification, engineering validation, practitioner usability, code-compliance claims, professional reliance, lifecycle issuance, and release distinct. Piping knowledge-source and claim fences

Under the revised loop, perform one bounded documentation/governance closeout after intended implementation/evidence integration and before the final PR. Substantive slices carry their needed document consequences. Preserve future requirements and accepted bespoke representations; do not convert formats incidentally. Existing Remaining entries stay accessible until their separately authorized retirement accounts for each meaning and verifies the destination. Graph/result records carry current continuity; still-pinned methods retain their own output contracts. Piping loop §§3–6 · Piping deliverable-record rules