EncrypiaBrief companion v0.2September 2026Public · Pre-testnet

06 · Legal · Whitepaper

Counsel scope note — who speaks, what governs.

Treat this reading as a counsel scope / intake note, not an opinion. Author of the public voice: Encrypia, coordinating the Zeqron protocol. Useful date: September 2026. Status: Architecture · Pre-testnet — advanced design and substantial software; no measured public network. This material describes protocol design and software maturity. It is not legal advice. It is not an offering document. It is not a classification opinion under any statute.

Three bodies of text — do not mix them. (1) This site — companion readings by role. (2) Public Technical Brief v0.2 in Markdown — canonical: if a page and the brief diverge, the brief wins. (3) Internal master — economics, parameters, operations; not a public source and not inferred from marketing. Role readings explain; they do not silently widen the brief’s claims.

Four counsel questions, and which public material answers each — without answering them as an opinion. Object: brief + this note (semantic coordination protocol; PQ in the design; ZAXON/ZNA as concepts). Phase: brief + honest status (code and spec; Architecture · Pre-testnet; no measured network; mainnet with no date in the public material). Omissions: the brief’s omission appendix (detailed economics, parameters, runbooks — under agreement). Who advises: the reader’s counsel with facts under whatever agreement applies — not this site.

ZQN is design vocabulary only for the sovereign token model’s economic anchor. This publication does not offer the instrument, does not fix terms, does not name an addressee, does not choose an issuance jurisdiction, and does not conclude or dismiss any classification. Naming ZQN avoids a design void; it does not classify.

Citation rule. Counsel may quote: Encrypia authorship; hierarchy (brief wins); Architecture · Pre-testnet phase; absence of a measured public network; ZQN as design vocabulary; the brief’s deliberate omissions. Counsel must not paste this companion as legal opinion, prospectus, classification conclusion, or as evidence of network performance.

Document control from brief v0.2 (public): Owner = Encrypia / Zeqron protocol coordination; Classification = Public (short); Master WP = Internal. This note does not assert jurisdiction of incorporation or applicable forum: counsel settles that with facts under the relevant agreement — not this site.

NDA index · Appendix B

Public titles · gated payload

  1. B1

    Long-form narrative + decisions

    Master narrative; D1–D13 / QRONCORD.

  2. B2

    Fine cryptographic parameters

    FRI, Poseidon, bit tables, micro-benchmarks.

  3. B3

    Ops / runtime

    WAL, validator ceilings, zone-split, bridges.

  4. B4

    ZNA / ZAXON economics

    Bonds, insurance, wire, schemas — no public APY.

  5. B5

    Phase evidence

    POC / lab with label, if any. No label → no metric.

  6. B6

    Core access

    Partnership terms. No full OSI core dump now.

Requesting the pack is the diligence act. Inventing the tables in a deck is a red flag.

Document hierarchy

Three bodies · do not mix them

  1. 01

    Companion site

    Role readings. Explain; do not silently expand the brief’s claims.

  2. 02

    Brief Markdown v0.1

    Public canonical. Anti-claim, status, Appendix B (titles).

  3. 03

    Internal master

    Economics, parameters, ops, wire. Under agreement — not inferred from marketing.

If site and brief diverge, the brief wins. The master is not a public source.

Four questions → public material

Object

What the thing is: semantic coordination of typed agreements; PQ cryptography in the design; agents and industrial assets as concepts. Material: brief + this note. It is not, in the public text, an offer.

Phase

What is underway: software and specifications; no measured public network; Architecture · Pre-testnet; September 2026. Material: brief (honest status) + anti-claim. Mainnet is a future phase with no date invented here.

Omissions

What is said and what is withheld on purpose: detailed economics, proof parameters, runbooks, deep RFC inventories. Material: the brief’s omission appendix. Phrasing: deliberate scope / under agreement — not a silent gap.

Who advises

The reader’s counsel, with documents delivered under whatever agreement applies. This site sets scope. It does not replace that work and does not choose a statute under which to classify anything.

What counsel may quote / must not paste

Quotable

Encrypia as author of the public voice; brief v0.2 governs the site; Pre-testnet phase; no public network metric; ZQN = design vocabulary; companions do not widen claims.

Do not paste as opinion

This note as a legal opinion; the companion as a prospectus; any classification conclusion; APY/TAM/TGE invented from other readings; endpoints or network figures.

This note does not determine

  • The classification of an instrument under any statute.
  • An exemption, a registration, or an issuance jurisdiction.
  • An offering date, terms, or addressee.
  • Personal-data handling or forum for a real deployment — analyzed with the system in front, elsewhere.
Public brief v0.2ZEQRON-WHITEPAPER-PUBLIC-v0.2.md

See also

Companion reading to Public Technical Brief v0.2. If this page and the brief diverge, the brief wins. The long master stays internal. Not an instrument offering and not legal advice.