EncrypiaBrief companion v0.2September 2026Public · Pre-testnet
02 · Investors · Whitepaper
Diligence outline — public surface to gated pack.
Treat this reading as the outline of a diligence memo, not a pitch. Encrypia coordinates Zeqron. Canonical brief: v0.2. Useful date: September 2026. Status: Architecture · Pre-testnet — advanced design and substantial software; no measured public network. This publication does not offer an instrument. ZQN is design vocabulary for the sovereign token model, not a placement.
Step 1 — public surface. Fix author (Encrypia), hierarchy (brief wins if the site drifts), and object: semantic coordination of typed, contextual agreements; post-quantum cryptography from genesis (FIPS 203/204/205); ZAXON and ZNA as protocol concepts. If the product sought is only a token venue, the brief itself points to more mature infrastructure.
Step 2 — code substance without network metrics. Developers can already read four real monorepo excerpts: ContractState, ContractPhase, AgentIdentity, and FinalityLevel. That proves object-in-code. It does not prove throughput, observed finality, or availability of a public network — because there is no measured public network to cite.
Step 3 — NDA index = Appendix B (titles, not payload): B1 narrative/decisions; B2 fine crypto; B3 ops/runtime; B4 ZNA/ZAXON economics; B5 phase evidence if any; B6 core access. This page names the index. It does not leak the master. Asking for the pack is the act; inventing the tables in a deck is not.
Step 4 — evidence rule and red flags. Any future figure must carry a phase label (Simulation / Devnet / Testnet / Mainnet), instrument, and date. Today the correct answer to “what does it yield / how fast is the network?” is: no public metric. Kill a diligence that invents APY, TAM, a TGE calendar, a Zeqron speed column beside observed networks, or that confuses an internal masters board with world readiness.
Software maturity, in the brief’s sense, means RFCs and a monorepo with tests. It does not mean a buyable service or a live token market. Deep core access is not a full OSI clone now: it is discussed under partnership. Disclosure model, not a shameful secret.
NDA index · Appendix B
Public titles · gated payload
- B1
Long-form narrative + decisions
Master narrative; D1–D13 / QRONCORD.
- B2
Fine cryptographic parameters
FRI, Poseidon, bit tables, micro-benchmarks.
- B3
Ops / runtime
WAL, validator ceilings, zone-split, bridges.
- B4
ZNA / ZAXON economics
Bonds, insurance, wire, schemas — no public APY.
- B5
Phase evidence
POC / lab with label, if any. No label → no metric.
- 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.
Claim labels
Brief v0.2 · companion
design
Specified as protocol intent.
E.g. — PoSS = stake + observable service.
code
A type or family exists in the monorepo.
E.g. — ContractState, AgentIdentity, FinalityLevel.
unpublished
Withheld on purpose (NDA / phase).
E.g. — FRI, wire, yield, ports, jurisdiction.
If a citation drops the label, it is no longer this publication. Inventing a metric without a phase is a different class of error.
Diligence path (spine of the memo)
1 · Public
Brief v0.2, these readings, anti-claim checklist. Establish object, phase, author, and deliberate omissions before asking for numbers that cannot exist yet.
2 · Code as substance
Four exhibits on the developer reading (ContractState, ContractPhase, AgentIdentity, FinalityLevel): proof the object is not only prose. No endpoint, no observed-performance row.
3 · NDA index
Chapters aligned to brief Appendix B (titles, not payload): (1) Long-form narrative + D1–D13 / QRONCORD decisions; (2) Fine cryptographic parameters (FRI, Poseidon, bit tables); (3) Ops/runtime (WAL, validator ceilings, zone-split, bridges); (4) Deep ZNA/ZAXON economics (bonds, insurance, wire, schemas); (5) Phase evidence / POC with label, if any; (6) Core access terms. Index visible; tables gated.
4 · Refuse invented metrics
Without phase label + source + date, there is no metric. Lab and observed network are different classes. Conflating them is a red flag.
Red flags — what should kill the diligence
Yield or market size
APY, “expected” yield, TAM, or a quantified “moat” pasted onto this material. Silence beats a blank field filled with “soon.”
Token calendar
An issuance, listing, or TGE date invented from the companion. Naming ZQN here is not an offer and not a calendar.
Invented speed column
Any side-by-side that places Zeqron next to observed Bitcoin/Ethereum without published phase instrumentation.
Masters = readiness
A high internal percentage measures code and spec hygiene. It does not measure that the world can use a network.
Thirty minutes of public diligence (checklist)
0–10 · Surface
Read brief v0.2 §§1–3 and §7. Note author Encrypia, Pre-testnet phase, and “no measured public network.” If a deck contradicts that, red flag.
10–20 · Object in code
Open the Developers reading: ContractState + AgentIdentity + named families. Ask: does this look like a generic token L1? If yes, either the companion failed or the reader wanted something else.
20–25 · Lineage vs network
Research: Mysticeti citation arXiv:2310.14821 with the adaptation disclaimer. Do not paste paper figures onto Zeqron.
25–30 · NDA ask
If interest remains: request the Appendix B index (narrative/decisions; fine crypto; ops/runtime; ZNA/ZAXON economics; phase evidence; core access) — do not invent the tables in the memo.
What this memo refuses to state
- Yield, market size, and any token calendar — deliberately out of publication scope.
- Issuance tables, insurance schedules, and fee tables — under agreement when shared.
- Any speed comparison that would invent a Zeqron column next to observed networks.
- That an internal masters board equals public readiness.