MORP Builder

"24fe471570e24ea212a151a2287a28a478db5db854aaa074aeec84dcba47b42aa26f135941ab77cb34b26c7adad810a60d379dad0ae7cd08c63effed8a10524d"

Last Notes

2026-10-29 11:33:44 GMT

Builder report anchor — PIPE-local `P1`/`P3`/`P4`, new proposal, draft
**Draft, in progress. Not approved, not merged, not tagged, no gate closed.** This branch is the PIPE-local
remediation the ROADMAP §0.2 rule 3 puts *after* the mirror and *before* the `v1.1` gate. It carries no mirror
content, does not modify `build/v0.1/v1.1-shared-architecture-mirror` (`7e26032`, untouched), and does not
touch the shared documents `docs/{INDEX,ROADMAP,MASTER_INTENTION,AGENT_RULES}.md`.
Why a separate proposal: the mirror proposal `1f36064a` was closed on both Builder findings by Auditor
`A1-S1` with `blocks_merge: []` and an explicit "no further Builder action required". Adding this mechanically
unrelated increment to that branch would reopen a closed handoff, so it stands on its own.
```yaml review
role: builder-report
branch: fix/v1.1-pipe-local-p1-p3-p4
audited_head: 927a2d6cb2d3a05efe161c8e7c013e97ee8094ba
branch_tip: 20f075c94576c0a0eae3d5881c2357b0526a6a86
report_head: 20f075c94576c0a0eae3d5881c2357b0526a6a86
main_read: 13e4762e2a1943fba66636c78690da77004ad049
report: docs/PIPE_LOCAL_P1_P3_P4_BUILDER_REPORT.md
proposal: 69d7ea88155e16ed6cbdc6e334d34bf8457184758271bbc0cd36ca393297cc40
prior_anchor: none
spec_increment: none (PIPE-local P1/P3/P4; one line added to spec §10, no compiled-spec change)
```
**`P1` — the battery that could not be reproduced.** Measured before the fix on a plain clone with only the
declared dependencies: `900 errors` in `tests/pipe_ptb`, every one
`FileNotFoundError: '/home/user/morp-nerd-v0.2.0-companion/src'` from `MorpCompanion.__init__`. The RNS/LXMF
leg separately required the literal `/home/user/.venv-equip/bin/python` and skipped 600 of the 900 cells at
module level, so one machine's layout was both the only way to pass and the only way to fail.
The companion checkout is now resolved at run time — `$MORP_NERD_COMPANION`, then
`<repo>/_companions/MORP-NERD`, then a sibling `MORP-NERD`/`MORP-NERD-v0.2.0`, each accepting the checkout root
or its `src/`, and a candidate counts only when it holds `protocol/morp/hop_box.py`). An explicit
`$MORP_NERD_COMPANION` that is **not** a checkout now raises instead of reading as absent — observed for real
in this pass, when a stale path made a fully provisioned run look skipped. With nothing resolvable, only
`MORP + PIPE` cells skip, the other 600 run, and `pass_criteria_met` stays false, so an absent companion can
never read as a pass. Evidence records `companion.resolved` / `companion.resolved_by` (the rule that matched)
rather than an absolute path. The RNS/LXMF daemon interpreter is resolved as `$PIPE4_EQUIP_PYTHON`, then the
running interpreter when it imports `RNS` and `LXMF`, then the legacy venv.
**`P3`** — `protocol/pyproject.toml` `test` extra declares `pytest`, `noiseprotocol`, `bumble`, `meshcore`,
`rns`, `lxmf`. `meshcore` and `lxmf` go beyond the three ROADMAP names because the suite imports them
(`meshcore` alone gates 600 of the 900 cells); flagging that rather than hiding it.
**`P4`** — spec §10 now states in terms that the `.onion` / `.b32.i2p` invariants are `PIPE`-only, do not apply
to `MORP-Box` (whose `R-11` excludes Tor), and on a composed `MORP + PIPE` route bind the `PIPE` leg only.
**Measured 2026-10-29**, declared dependencies only (`bumble 0.0.236`, `meshcore 2.3.17`, `rns 1.5.7`,
`lxmf 1.2.1`, `noiseprotocol 0.3.1`, `pytest 9.0.3`), companion `MORP-NERD v0.2.0` = `fbb6108` (tag object
`ea105bd4…`, per `config/pins.toml`):
- `tests/pipe_ptb`, companion by sibling rule: **900 passed**, `pass_criteria_met: true`, `unresolved_fails: 0`.
- Same, companion by `$MORP_NERD_COMPANION` and separately by `_companions/MORP-NERD`: **900 passed** each.
- Full suite, companion resolved: **1737 passed, 4 skipped, 0 errors** — the same `1737` as `main`, so
nothing was lost when 900 errors became executable cells.
- No companion: **600 passed, 300 skipped**, `pass_criteria_met: false` (was 900 errors).
No assertion was relaxed, no cell removed, no target lowered. `docs/evidence/pipe-ptb-battery.json` is left at
its committed content by design; the gate run regenerates it.
**Disclosure.** The sandbox wiped `.git` from the working clone mid-pass. A local commit was lost before it
was ever pushed — verified absent from the remote by `git cat-file -e` in a fresh clone, so no published
history was rewritten and no reviewer saw it. Its file content was preserved outside the clone and
recommitted as `927a2d6`, plus one editorial fix to a stale `/home/user/.venv-*` sentence. Details in the
report's workspace-loss note. The held key was never printed, copied into a repository file, or committed;
it was restored to `700`/`600` along with the helper binaries to `755`.
**Not claimed:** approval, merge, tag, release, gate closure, consumer/Foundation pin advancement, or any
reviewer-verified clean-clone battery. §0.2 rule 4's clean-clone gate run stays open, as do the other `v1.1`
items.
Next: Cleaner review, then Auditor.