Parallelism boundary — Bend s05

Name Claim Surface vs Host Work Surface. Do not treat CUDA marketing as rust-tops law coverage.

<!-- hal:authoritative:yaml -->

Name the line between Bend’s parallel-compute claims and Hedronite host work. Do not treat CUDA marketing as rust-tops law coverage.

§I. Frame

Asr session 05 for Bend. Fifth live fire of the Bend experiment track. Week 3 fire 1. Home folder: . Primary live cite: https://bend-lang.com/. Vendor org: https://higherorderco.com/. On-disk hub: .

Sessions 01–04 shipped fail-closed install, Law Own / Cover Bound, Gap Walk, and Friction Log. Today names a different trap: reading vendor parallel claims as if they were Hedronite shipping policy or rust-tops AI-ops laws.

Dualfire seat (SCORE ACK 2026-09-24): Bend2 is AI ops. Agents encode protocol as fail-closed LAWS.bend. That seat fails if an agent “adopts Bend because it is parallel” or files GPU demos as proof that laws are denser. Parallelism is a vendor runtime claim. Laws are the Hedronite reason this lane exists.

Host reminder: Bend CLI work stays on tower or Bot-VM only. No mesh PATH assumptions.

Done-criteria: you can name the parallelism boundary (claims vs host work) without treating Bend as primary-stack or parallel-tourism.

Still experiment lane. Primary stack law stands: Rust + TypeScript for full-stack work; Python + Nix for ops and config. Bend does not join that daily clock.

§II. Claim Surface (named technique)

Yagyu names the cut once. Claim Surface: quote what the vendor page actually asserts about speed and parallelism, then stop. Do not inflate it into fleet policy.

From https://bend-lang.com/ (read today): Bend markets native speed near C on one core; the same binary on many cores or GPU; “no threads, no locks, no kernels to write”; split work and spread calls; AGENTS.md hint “parallelize the code whenever possible.” Those are Claim Surface sentences. They describe a runtime and a vendor teaching tip.

Musashi declarative: a marketing claim is not a measured host result and not a rust-tops axiom.

If-then-thus: if the sentence comes from bend-lang.com parallel / CUDA copy, then it sits on Claim Surface, thus it does not rewrite Cover Bound, Gap Walk, or Friction Log.

§III. Host Work Surface (named technique)

Host Work Surface: what Hedronite actually runs, measures, and authorizes for this experiment.

Host Work Surface includes: which host has the binary (tower or Bot-VM), whether bend PROOF.bend ran, which laws were stated, which gaps remain silent, which friction lines are open, and any wall-clock numbers you measured on that host. It excludes: screenshots from the marketing page treated as your benchmark, and “parallelize whenever possible” treated as standing curriculum law.

§IV. Parallelism Boundary (named technique)

Parallelism Boundary: the named line between Claim Surface and Host Work Surface. Say it once when an agent or spike note starts mixing them.

Template sentence (copy into spike notes when needed):

BOUNDARY: Bend parallel/CUDA claims = Claim Surface.
Hedronite seat = AI-ops LAWS.bend from rust-tops, on tower/Bot-VM host work.
Do not score laws by parallel marketing. Measure performance if claimed (A7). Prefer density over golf (A6).

Two rust-tops touches, then stop:

• A6 — density, not golf: more laws or flashier demos are not automatic progress. A GPU pow2 demo does not densify your LAWS.bend.
• A7: performance measured, not claimed: if a spike note says “faster,” it needs a host, a command, and a number you ran. Vendor “up to a hundred times” is Claim Surface until Host Work Surface records a measurement.

Cite protocol when you mention it: Do not turn this session into a full rust-tops tutorial.

If-then-thus: if a note cites Bend parallelism as evidence that AI-ops laws are done, then it crossed Parallelism Boundary, thus rewrite the note to separate Claim Surface from Host Work Surface before claiming Cover Bound progress.

§V. What this lane is for (and is not)

Bend2 exists so agents can encode rust-tops as fail-closed laws and proofs. Parallel runtime is interesting vendor context. It is not why Asr seats Bend next to Nix and the Python beat.

Refuse parallel-tourism closers:

• “Reseat primary stack to Bend because it is CUDA-native.”
• “Skip Gap Walk; the binary is parallel so coverage is fine.”
• “Factory-adopt Bend for all Hedronite compute.”
• “A7 is satisfied by the marketing chart.”

Replace with:

• “Experiment lane; Rust+TS / Python+Nix clocks stand.”
• “Laws and proofs are the seat; parallel claims stay on Claim Surface.”
• “Measure on Host Work Surface or do not claim speed.”
• “Friction Log and Gap Walk still apply.”

§VI. Worked boundary check

Read each line. Mark Claim or Host.

1. "Same binary runs on GPU, up to 100× one core." → Claim Surface (vendor).
2. "PROOF.bend green on Bot-VM for you_cant_win." → Host Work Surface.
3. "parallelize whenever possible" in AGENTS.md tip → Claim Surface teaching tip.
4. "Wall clock 1.8s for PROOF.bend on tower after pin X." → Host Work Surface (A7-shaped).
5. "We're verified because Bend is parallel." → Boundary violation; rewrite.

Only Host Work Surface advances Cover Bound and ship notes.

§VII. Common mistakes

1. Filing CUDA demos as Cover Bound progress.
2. Treating “parallelize whenever possible” as Evan curriculum law.
3. Skipping Friction Log because a parallel example felt smooth.
4. Expanding rust-tops into a full protocol lecture (A6/A7 as boundary pins are enough).
5. Closing with factory adoption or primary-stack reseat.

§VIII. Boundaries

• Not install tutorial (session 01).
• Not Gap Walk / Friction Log re-teach beyond the separation tables.
• Not Lean tactics training or Lean smackdown.
• Not software-factory adoption for Hedronite shipping.
• Not curriculum clock reseat.
• Not Maghrib quiz×4 (Maghrib stays quiz×3 on the Dhuhr trio).
• Not mesh PATH Bend runs (tower or Bot-VM only).
• Not a CUDA programming course.

§IX. Close

Session 04 banked toolchain weather. Session 05 names Parallelism Boundary so Claim Surface never masquerades as Host Work Surface or rust-tops law density. Next unmarked: session 06, Spike bank review.

Related:

Write the BOUNDARY template into a Bend spike note (or a rehearsal line in FRICTION.md). Mark one recent sentence Claim or Host. Stop.