Platform
Documentation & Evidence Roadmap
A state-based roadmap for the documentation and its evidence gates. It contains no delivery dates, completion percentages, fundraising claims or promise of an operational network.
- Source / verification
- Current Coverage Registry, Readiness gates and owner-directed documentation boundaries
- Document version
- 0.9 RC1
- Last reviewed
- 7 October 2026
Current state
- Documentation
- 0.9 RC1 — evidence and owner-approval gates in progress
- Coverage
- 45 Covered / 8 Partial / 0 Missing — documentation scope only
- Operation
- No DLT, node, wallet, token, payment rail, API or SDK verified
- Next owner gate
- Adopt, amend or reject Proposed Canon & Protocol Invariants v0.1
What is available — and what is not
These are claim categories, not a single readiness score. Availability of documentation does not demonstrate an operating protocol.
- Verified available
The public ByteShares.org documentation site and its public indexing configuration. Cooperative membership belongs to the separate ByteShares.dk site.
Public-site controls- Documented historical
Owner-reported historical VPLedger text inspection and recorded concept lineage. Earlier proposals are not evidence of delivered functionality, current code or legal title.
Historical source comparison- Proposed / not adopted
Proposed Canon v0.1 and conceptual architecture models; review manuscripts remain Draft / Awaiting approval. No DLT operation is asserted.
Review proposed canon- Awaiting evidence
Independent specifications, source acceptance, implementation, consensus/finality and operating evidence remain unresolved. Documentation coverage is not verification.
Independent evidence blockers- Requires owner/legal/security approval
Canon acceptance, permitted disclosure, IP/licensing disposition and legal/security review are separate gates. No approval follows from this preview update.
Review acceptance gates
Documentation: 45 Covered / 8 Partial / 0 Missing. Source verification: 4 Verified / 25 Owner-asserted / 11 Unverified / 13 No source. These independent registry totals have not been upgraded.
Documentation change notes — source/preview only
This is a concise editorial change record, not a software release log or proof that these changes have been published.
8 October 2026 — documentation work date
Public trust and review orientation — preview changes
Added a five-category status summary, consistent manuscript metadata, source-to-claim guidance and a non-audit security review overview. No evidence or maturity upgrades; not a production release.
8 October 2026 — documentation work date
Reader accessibility — earlier preview work
Added FAQ and roadmap guidance, caption-linked diagrams, keyboard access and review reading paths. These are documentation improvements, not implemented protocol controls.
8 October 2026 — documentation work date
Proposed canon and historical lineage — documentation context
Prepared the unadopted canon review and a source-bounded historical comparison. Historical document dates and proposed design versions remain separate from the documentation RC.
State-based roadmap
01
Available now
- Public technical information, architecture pages, glossary and evidence register.
- Five claim-traced review manuscripts, each Draft / Awaiting approval.
- Proposed Canon & Protocol Invariants v0.1 for owner review; not adopted.
Documentation availability does not demonstrate software, a network or legal acceptance.
02
Owner review
- Adopt, amend or reject Proposed Canon & Protocol Invariants v0.1.
- Confirm the permitted public summary of private institutional material.
- Decide the named exception, disclosure, credential, governance and release responsibilities.
No decision is inferred from preparation or review readiness.
03
Evidence required
- Merkle snapshot and eIDspot credential/revocation specifications.
- Exception/dispute, node deployment and security-disclosure procedures.
- IP/licensing disposition, Sig-56 and F.I.P. specifications, accepted source and assessed implementation evidence.
Dates and completion percentages are omitted because none are evidenced.
04
Operational future
- Consensus/finality, implementation, conformance, security and accountable operating evidence.
- Only then may network, node, API, SDK, wallet, token, payment or performance claims be reviewed.
No operational launch is scheduled or implied.
What this roadmap does not promise
It does not schedule source intake, repository creation, software delivery, a testnet or mainnet, token issuance, payments, investment activity, partner participation or regulatory approval.
Detailed blockers and evidence requests remain in the Coverage Registry and Readiness & Acceptance pages.
Evidence register
Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.
| Claim | Source type | Verification | Note |
|---|---|---|---|
| Roadmap stages reflect current documentation and evidence gates | Existing project registries | Verified source on file | The stages summarize recorded states without adding dates or operational claims. |
| Any future delivery date or operational milestone | Approved delivery plan and operational evidence | No source on file | No date or completion forecast is published. |