@projectpac/operation-pexe

An operation adapter for the object toolchain: compile what an agent drafted, say what the compiler said, and build the box's program envelope from agreed sources.

It is here rather than in the flow because compiling means running a program on this machine, and the envelope means reading this node's catalog of built dependency archives. Those are outside effects and local configuration, which is the line an operation adapter marks: a principal's policy can allow them, gate them, or refuse them, and the flow only ever asks by name.

• The toolchain contract is DON's own pexe binary. Sources are laid out as src/manifest.toml + src/plugin.rhai with the catalog materialized under src/deps/<plugin>.pexe. A build rewrites manifest.toml with the true module hash -- the only way to learn it -- and --check verifies instead: the sources must compile and the declared hash must match, which is the agreement-time bar.
• The envelope is a cross-repo wire contract. dobjEnvelope.ts builds the box's harness.dobj-action.v1 program bytes, and tests/upstream-parity.spec.ts holds it to jc-tee-vm's own module by replaying shared vectors -- same canonical bytes, same accept/reject verdicts -- whenever a checkout is present. The approval signature covers bytes, so the port must agree in behaviour, not merely in spirit.

The real-toolchain conformance suite runs with PAC_TEST_DON=1 when the digital-objects-network checkout is built.