Origin: Viability report §4.2 + §9 T4 (ops/analysis/2026-06-10-voidpay-viability/report.md). Owner: Kai (CTO) / Ignat.
Decoupled from: spec 092 distribution trust-gate (Kai ruling 2026年06月10日). Different audience — 092 gates END-USER privacy (Farcaster freelancers); the private design-spec affects DEVELOPERS/PLATFORMS evaluating the standard. NOT a distribution blocker.

Problem

The void-layer design-spec is marked private; README honestly points to it as "private — internal reference". For an open standard this is a disqualifying detail (report §4.2). A third party evaluating the codec today cannot read the spec that defines it.

Fix

Publish the design-spec (move from private reference into the public void-layer/codec repo, or a linked public location). ~one evening.

Sequencing

• Belongs to the void-layer / LOF2 track ("at least one distributor wants the standard before v1.3").
• Do before any LOF2 integration outreach — a private spec kills the first developer conversation.
• No 092 dependency; can proceed independently of the privacy trust-gate (voidpay#320).

Acceptance

• Design-spec published to a public, linkable location
• README pointer updated from "private — internal reference" → public URL
• Cross-check: no secrets / internal-only notes leak in the published version

Related

• voidpay#320 — privacy trust-gate T1–T3 (separate track, end-user privacy)
• Report LOF2 — distributor-interest kill-criterion