Review manuscript 01
ByteShares Architecture
Documentation draft — not a standards ratification, software release, security assessment, operational specification or legal opinion. Core model: Proposed / Non-operational.
- Title
- ByteShares Architecture
- Publication date
- Not assigned — unpublished review manuscript
- Individual paper version
- Not assigned; documentation collection is 0.9 RC1
- Provenance / source class
- Existing public project documentation synthesis; source verification remains as recorded in each claim trace
- Current status
- Draft / Awaiting approval — Proposed / Non-operational
- Last reviewed
- 7 October 2026
- Relation to present architecture
- Provide one reviewable account of the documented layer model, responsibility boundaries and conceptual system flow while keeping the public documentation platform distinct from ByteShares.dk cooperative participation.
Executive abstract
ByteShares is documented as a modular trust architecture in which identity establishes a subject, governance scopes authority, VPLedger records proof and evidence relationships, and planned nodes execute authorized rules. Interfaces remain replaceable and must not become protocol truth. This is a synthesis of documented intent, not evidence of a running DLT, accepted source tree or deployed network.
Purpose and scope
Purpose. Provide one reviewable account of the documented layer model, responsibility boundaries and conceptual system flow while keeping the public documentation platform distinct from ByteShares.dk cooperative participation.
Scope. Identity, governance, evidence, node and interface responsibilities; conceptual flow from identity and intent to evidence and epoch closure; storage and value-function boundaries; documentation maturity and unresolved protocol invariants.
Core documented model — Proposed / Non-operational
Layered responsibility model
The architecture assigns different responsibilities to identity, governance, VPLedger, nodes and interfaces. Identity establishes the subject; governance supplies mandate and rule context; VPLedger describes append-only outcomes and evidence references; planned nodes apply authorized rules; interfaces present or submit information without creating authority.
The separation is intended to prevent a wallet, client session or frontend from becoming protocol truth. It is a conceptual responsibility boundary only: no accepted implementation or operating pipeline has been demonstrated.
Flow, storage and value boundaries
The documented flow moves from identity and intent through authority and rule evaluation to an outcome, evidence record and later closure. Compact anchors are distinguished from retained source evidence: a commitment may support later matching or inclusion checks, but cannot establish the truth, ownership or continued availability of the underlying material.
Named value functions and bridges are documentation concepts rather than live assets, markets or integrations. Filecoin and other rails remain conditional options. AI City is a planned end-product family, not an operational deployment of the architecture.
Boundaries / what is NOT claimed
- No consensus, finality, canonical state-transition or conformance rule is asserted.
- No throughput, availability, deployment, bridge, asset, node or implementation result is claimed.
- Documentation release candidate 0.9 RC1 is not a software, DLT, protocol or network release.
- The 2026 archive records support founder/originator chronology and concept lineage, not exclusive ownership of all historical software.
Claim-to-documentation trace
Conceptual claims only. Linked sections retain their own source and maturity labels; this table does not convert documentation into implementation evidence.
| Material conceptual claim | Existing documentation | Claim limit |
|---|---|---|
| The conceptual system flow runs from identity and intent through outcomes, evidence and closure. | No operating pipeline is demonstrated; the normative invariant set exists only as Proposed Canon v0.1, owner adoption pending. | |
| Recorded archive provenance supports concept lineage into the 2026 modular architecture, not complete historical ownership. | Owner-recorded chronology; component-level legal title remains unresolved. | |
| The platform is described through identity, ledger, governance, node and interface layers. | Documented model; no accepted implementation is inferred. | |
| Authority, proof, execution and presentation have separate responsibilities. | Conceptual separation; the invariant set exists only as Proposed Canon v0.1, owner adoption pending. | |
| Anchors and retained evidence serve different purposes. | No retention guarantee, storage rail or legal conclusion follows. | |
| Named value functions, bridges and modules are bounded conceptual entries. | No product, asset, bridge or module is represented as operating. |
Open questions / evidence required
- Which documented principles are intended to become binding invariants? TBD / Requires source
- What source defines accepted state, rule-version handling and conformance? TBD / Requires source
- Which layer boundaries are architectural intent only, and which are intended to constrain implementations? TBD / Requires source
Architecture principles / protocol invariants — remains Partial
TBD / Requires source. The owner-authorized archive draft Proposed Canon & Protocol Invariants v0.1 (8 Oct 2026; INV-001–INV-035, C-01–C-14) supplies a complete proposed scope at documentation level. Canon adoption now depends on owner acceptance, superseding the earlier canon-source request; verification unchanged; no implementation or conformance evidence.
Review checklist — pending review
- Confirm that the manuscript reflects the linked documentation without widening any claim.
- Confirm that Proposed, Planned, Draft and Non-operational labels remain attached to conceptual material.
- Resolve or retain each cited partial-audit blocker; do not infer an answer from this manuscript.
- Check every material claim against its linked section before any release decision.
- Record explicit owner approval separately; review completion is not publication approval.