EncrypiaBrief companion v0.2September 2026Public · Pre-testnet
05 · Enterprise · Whitepaper
Committee brief — fit, map, and when not.
Treat this reading as an architecture-committee brief, not a case study. Encrypia coordinates Zeqron. Canonical brief v0.2. September 2026. Architecture · Pre-testnet: advanced design and substantial software; no measured public network; no SLA. ZQN is design vocabulary, not a commercial offer.
Who talks to whom, in the design fit. The zone application talks to the institution’s domain rules. Coordination talks to the contract lifecycle and, when the zone asks, to a transparent-setup zero-knowledge proof. The consensus anchor talks to commitment order on a DAG. Identity and credentials talk to human parties and, if agents are present, to ZAXON bounds. That is the conversation map. It is not a live connector published on this page.
What leaves the house versus what stays inside — a design conversation, not an API inventory. Leaves: the public brief, these readings, demos Encrypia discloses. Stays gated until agreement or a named phase: wire formats, deep schemas, parameter appendices, economics depth, core access, and integration with identity / existing systems. Inventing a “ready pilot” from this companion would break the honesty rule.
Three fit situations — no customer names — with enough detail to brief a CIO. (A) Typed inter-institution agreement: two organizations close a commitment with type and context; the record orders the anchor without requiring everyone’s balance to be public. (B) Industrial asset with history: a batch or composition retains genealogy and admits only valid recipes (ZNA, concept + software family). (C) Agent with a ceiling: a program acts under quotas, bound to code digest and operator (ZAXON); changing the code changes the identity; it can be stopped.
Brief selectivity — the six “when not” conditions are a product filter, not marketing weakness: (1) a battle-tested public network with a service commitment is required today; (2) the product is only a generic token venue; (3) the full core is required under open license now; (4) the crypto mandate must remain classical in the short term; (5) the team wants accounts and a single contract language only; (6) audited mainnet economics and live bridges are required as present public fact. In those cases: other infrastructure, or wait.
Question for the committee, before opening procurement: can we work on design and code under agreement, or do we need a measured SLA service now? If only the latter advances, the honest answer is wait or another network. If the former is possible, there is material for a partnership conversation — off this page, under NDA.
Architecture · four layers
Public brief v0.2 §3 · design
- AApplicationSemantic Zones, domain modules, oracles
- BCoordinationContracts, STARK proofs, semantic bridges
- CConsensusQronGraph (DAG) + BFT-style committee
- DIdentityPQ DIDs, verifiable credentials, reputation
One job per layer. Conceptual flow: Applications → Coordination → Consensus; Identity authenticates throughout.
Committee fit · three objects
Design · no named customer · no SLA
- A
Typed agreement
Inter-institution commitment with type and context; DAG orders the anchor.
Friction — May reach Disputed. Not automatic ERP settlement.
- B
Industrial asset
Batch / composition with genealogy and valid recipes (ZNA, concept).
Friction — Invalid recipe or invented mass = conservation violation.
- C
Bounded agent
Program under digest + operator + capabilities (ZAXON).
Friction — Code change changes identity. Not “same wallet, new model.”
Committee question
Design + code under agreement, or measured SLA service already? Only the latter → wait or another network.
If the problem is not one of these three, fit is weak. The wait question drives timing.
ZNA Blueprint (fields)
zeqron-assets · Blueprint
code · ZNA concept · no public wire
pub struct Blueprint {
pub id: BlueprintId,
pub name: String,
pub input_requirements: BTreeMap<String, u32>,
pub physical_constraints: Vec<PhysicalConstraint>,
pub version: u32,
// creator / opaque templates omitted here
}A recipe with requirements and physical invariants — not an NFT wrapper. Wire fields and deep economics stay out.
Institutional conversation map
Zone ↔ Coordination
The institution expresses rules in the application zone. Coordination validates the contract and may attach a proof. Status: design and code; no integration endpoint asserted.
Consensus ↔ Identity
The DAG anchors order; identity/credentials bound who acts. Agents: ZAXON ceilings. What leaves the house (hashes, attestations) versus what stays local is a design decision under agreement.
The committee question
Design+code under agreement, or SLA service now. That answer decides timing more than any adjective on this page.
Selectivity
Using the six “when not” conditions in committee saves months of false fit. The brief writes them so you do not have to guess.
Friction the committee should hear
Inter-institution agreement that disputes
Two organizations can reach Disputed after Committed. The conversation map does not promise automatic settlement without process. The object remains the ContractState cycle, not a magic ERP.
Industrial batch with an invalid recipe
ZNA (concept) rejects composition outside a blueprint. Inventing mass or skipping genealogy is not a UI edge case: it violates the design’s conservation rule.
Agent whose code changes mid-process
If the digest changes, the ZAXON identity is no longer the same. A committee that expects “same wallet, different model” confuses the bound. Say that before the NDA, not after.
“Ready pilot” without a published phase
Without Devnet/Testnet with date and scope, an RFP that asks for a measured SLA against public Zeqron is mis-framed. Honest friction is partnership on design/code, or wait.
What is absent by design
- A reference customer, an SLA, or a production integration described as done.
- A path of weeks to a pilot on a public network that is not measured.
- Deep formats and limits — discussed under agreement, not on this page.