@network-harness/protocol-objects

Two humans agree on one action over things they own, and the action happens without either of them handing anything to the other.

The negotiation is one phase rather than joint-search's two, because here the terms and the program are the same conversation: which objects each side stakes is what the program acts on. Three files are drafted together -- the terms, and the two sources of the program.

One thing here is unlike any other protocol in the harness: before a draft is sent, it is compiled. A program that does not compile is not a proposal. The compiler's verdict feeds the drafting run itself -- the loop's own correction turn covers an answer that does not fit the output contract, but a program that compiles to nothing fits the contract perfectly and is still unusable, and only this protocol can know that. So the diagnostics are appended to the same run, inside the same turn budget, and it stops there.

What travels is the terms, the sources, and the compiled program: all public between the two parties, all reviewable, all agreed byte for byte. The objects themselves are staked into the box by name, and what comes back goes into the human's own object daemon through an apply. This protocol never holds an object it did not just receive on its human's behalf.

| | | | --------- | ---------------------------------------------------------------------------------------------------------------------------- | | routes | POST /actions, GET /actions, GET /inventory | | payloads | action.request, action.suggestion, action.agreed, action.declined, action.party, action.session, action.failed | | schedules | advance 2s, sweep 30s | | needs | any source, pexe.compile and dobj.import plus the jc.* operations, with jc.submit and dobj.import gated | | intents | action |

It cannot run against anything this repository ships

It needs an external object daemon (dobjd) for the inventory and for importing what a run produced, and the pexe toolchain to compile. Neither is here, so the dev environment does not install this protocol; its vitest suite (services/daemon/tests/objects.spec.ts) is the way to exercise it.

Its box half is also known to diverge from the real box and has only ever run against the non-executing test double: the envelope's schema name, its shape, and the fact that it proposes a locally compiled artifact where the box compiles source in-enclave. A real box refuses it at propose. See docs/v1-plan.md, which records the finding and recommends parking this cluster until a dobjd exists.