Skip to content

Live technical information site. The planned DLT is not live; membership is on ByteShares.dk.

ByteShares.org

Operations

Coverage Registry

Documented architecture

A documentation RC1 completeness control for the canonical technical model. It records where each model is documented, how it is represented, and — kept deliberately separate — whether its source has actually been verified. It is not marketing and not an operational status dashboard.

Source / verification
Register maintained against owner instruction and supplied provenance-readiness evidence
Document version
0.9 RC1
Last reviewed
7 October 2026

Documentation release candidate — October 2026

Version
0.9 RC1
Last reviewed
7 October 2026
Status
Evidence and owner-approval gates in progress
Scope
Documentation only — not a DLT, software or network release. The public site remains available at https://byteshares.org; this correction is source/preview only.

Documented provenance and concept lineage

Archive evidence recorded by the owner in the 7 October 2026 canon. A later owner-reported inspection of two historical VPLedger texts is summarized separately on Technical Papers; neither record establishes legal title, source acceptance or current implementation.

  • Ronny_Boesing_IP_Provenance_Dossier_2026.docx
  • Ronny_Boesing_IP_Concept_Evolution_Register_2026.docx
  • Ronny_Boesing_Chain_of_Title_Matrix_2026.docx
  • Ronny_Boesing_2026_IP_Foundation_Clean_Title_Record.docx

The archive records support founder/originator and chronology evidence for VPLedger and a coherent conceptual lineage into the 2026 modular trust architecture. Documented provenance and concept lineage are not proof of exclusive ownership of all historical software. Complete legal chain of title remains unresolved for some contractor and collaboration elements, including missing assignments, transfers or agreements. Repository acceptance and licensing remain separate and incomplete.

Private masterplan — documentation provenance only

OWNER PROVIDED / UNVERIFIED

Based only on owner-supplied extracted rules from printed Chapters 6, 7, 26 and 27 (PDF pages 36–45 and 127–133), not an independent inspection of the 149-page private document. Full text is not public. Source accuracy and authorized public-disclosure scope require review. The source edition label is not protocol ratification or implementation evidence.

A source-backed documentation improvement, not independent source acceptance, canon adoption, technical/legal closure or operational readiness. Current register: 45 Covered / 8 Partial / 0 Missing; all verification categories and remaining precise blockers are unchanged.

Review the limited masterplan-derived draft and owner decisions
Aggregated readiness and acceptance view

How to read the register

Coverage and verification are two different questions. A model can be fully documented and still rest on a source nobody has inspected.

  • Covered — the conceptual scope is substantively represented on its destination page.
  • Partial — represented, but the stated scope cannot be completed without a specified source, format, procedure or decision. Covered conceptual models can still have open evidence and implementation gaps.
  • Missing — no substantive destination coverage.
  • Verified — a source was inspected and supports the claim.
  • Owner-asserted — stated by the owner; the claim is not independently verified. A source may be privately held, owner-summarized or outside the approved inspection scope.
  • Unverified — a source is named but has not been produced or concluded.
  • No source — no supporting source is on file for this specific claim; this is not proof that none exists elsewhere.

Coverage never means built, live, certified, externally validated or approved for publication.

October RC1 Partial-row audit: every one of the 19 previous Partial rows has a documented reason and resolution below. Eleven documentation scopes are now Covered: the architecture-invariants row (Proposed Canon v0.1, owner adoption pending), storage/custody boundaries, conceptual threat mapping, proposed SDK responsibilities and error/versioning policy, recorded inventory, classification rules, integrity evidence limits, sensitive handling rules, candidate mapping and proposed documentation-link checks. This closes no security assessment, source acceptance, legal-title or operational gate.

53 models tracked — 45 covered, 8 partial, 0 missing.

Verification unchanged — 4 Verified / 25 Owner-asserted / 11 Unverified / 13 No source.

Audit of all 19 previously Partial rows

Reviewed 7 October 2026 against existing project documentation and already-recorded archive provenance only. Later owner-reported inspection of two historical VPLedger texts is recorded separately on Technical Papers and does not upgrade this registry. Covered below refers solely to the documented conceptual scope; actual scans, accepted baselines, security findings and repository links remain unperformed or unverified.

Architecture principles / protocol invariants

Why Partial: No current 2026 normative invariant set existed; Proposed Canon v0.1 now supplies a complete proposed scope pending owner adoption.

Covered — documentation only: 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.

Supporting documentation

Merkle snapshot model

Why Partial: The primitive has no defined construction or acceptance semantics.

Remains Partial: Requires a snapshot specification defining record-set selection, ordering/canonicalisation, hashing, inclusion encoding, epoch closure and trusted-root establishment; no verifier or vectors supplied.

Supporting documentation

Storage & data sovereignty

Why Partial: Anchor/evidence separation lacked explicit limits on what a commitment establishes.

Covered — documentation only: Custody, disclosure and historical-proof limits are documented and linked to security classification. Retention policy, retrieval guarantees and any storage rail remain unspecified.

Supporting documentation

Exceptions, reversals & disputes

Why Partial: Requirements exist but no reviewable procedure or responsible authority is defined.

Remains Partial: Requires an owner-approved procedure naming exception authority, stay/review powers, dispute forum, response/appeal timetable and authorization of compensating decisions.

Supporting documentation

Node deployment roadmap

Why Partial: The referred-to staged sequence has no supplied plan or site evidence.

Remains Partial: Requires the dated topology/deployment plan, owner-approved operator/site scope, host or site confirmations, and stage entry/exit criteria; no locations or dates can be assigned from existing material.

Supporting documentation

Security / threat model

Why Partial: Threat categories were not connected to documented dependencies or assessment limits.

Covered — documentation only: Conceptual threat-to-layer trace is documented. Asset classification, attack analysis, implementation controls, residual-risk assessment and independent testing remain unverified; this is not a completed security assessment.

Supporting documentation

Security disclosure process

Why Partial: Intent alone cannot establish an accountable reporting process.

Remains Partial: Requires Ronny's decision naming a staffed recipient/contact route, covered systems, handling owner, response commitment and disclosure/escalation rules; no address or timetable is invented.

Supporting documentation

SDK structure

Why Partial: Responsibilities were listed without dependency and implementation-contract boundaries.

Covered — documentation only: Proposed responsibility-to-document mapping now defines proof, authority and inclusion roles and exclusions. Languages, packages, schemas, verifier code and test vectors remain unassigned.

Supporting documentation

Error & versioning policy

Why Partial: The policy framework lacked a distinction between conceptual refusal, contract change and historical verification.

Covered — documentation only: A proposed decision boundary ties refusal to rule context and separates contract/specification/software versions from documentation RC1. Codes, version scheme and support periods remain owner/specification decisions.

Supporting documentation

Source inventory

Why Partial: Inventory coverage was conflated with canonical-source acceptance.

Covered — documentation only: The five recorded roots and counts are mapped to proposed targets, bounded to the historical 17 September 2026 recovery report. Canonical scope and repository intake remain pending.

Supporting documentation

Provenance classification

Why Partial: The classification legend was treated as incomplete because no candidate had been accepted.

Covered — documentation only: A/B/C/D/X meanings, consequences and intake criteria are documented. All candidates remain C; classification decisions require repository-level history, title/licence and review evidence.

Supporting documentation

Integrity / hash evidence

Why Partial: Estate integrity evidence lacked an explicit distinction from accepted repository baselines.

Covered — documentation only: Recorded estate hashes and manifest scope are documented; a hash does not prove authorship, title, safety or runnability. Per-root-to-baseline linkage and reviewer evidence remain pending.

Supporting documentation

IP & licensing

Why Partial: Founder/chronology records do not resolve component-level title or licence rights.

Remains Partial: Requires component-linked contractor assignments, collaboration agreements, applicable bankruptcy/project-rights transfers, third-party licence/dependency review and a reviewed title/licence disposition. The four archive records alone do not close this gap.

Supporting documentation

Secrets exclusion

Why Partial: Handling-policy coverage was conflated with proof that quarantine and scans were performed.

Covered — documentation only: Class X, metadata-only recording, quarantine and never-publish rules are documented. Authorized per-root scans, exclusion records and reviewer sign-off remain pending; no clean-source claim.

Supporting documentation

Legacy source mapping

Why Partial: Proposed mappings were treated as incomplete because acceptance had not happened.

Covered — documentation only: Each of the five inventoried roots has a proposed target, class C, specific gaps and hold disposition. Other OpenLedger roots remain archive/reference candidates until scope and evidence are reviewed.

Supporting documentation

GitHub to ByteShares.org link validation

Why Partial: An acceptance criterion existed without a concrete documentation-link review boundary.

Covered — documentation only: A proposed mapping record and checks now separate documentation intent, accepted source and operational claims. Actual URL/commit/branch checks require authorized repository acceptance; no external links are activated.

Supporting documentation

Sig-56

Why Partial: Purpose and lifecycle exist, but normative action-binding content cannot be derived from them.

Remains Partial: Requires the source specification defining signature profile, signed content, serialization/canonicalisation, verification and version rules, plus conformance criteria and test vectors.

Supporting documentation

FAWN Identity Protocol (F.I.P.)

Why Partial: Concept blocks do not define an implementable agent/curator authority model.

Remains Partial: Requires the source specification defining agent identifiers, curation/authority records, permitted-memory enforcement, lifecycle/revocation semantics and conformance criteria.

Supporting documentation

eIDspot credential & revocation

Why Partial: Lifecycle intent has no issuer, format, status or time semantics.

Remains Partial: Requires issuer trust/acceptance rules, credential and presentation formats, validity/renewal policy, revocation publication and freshness rules, historical verification semantics and key-custody/recovery decisions.

Supporting documentation

No further existing-source edit can supply the eight remaining normative/specification, procedure, deployment, disclosure or title gaps. Five full claim-traced review manuscripts now exist in source/preview on the Technical Papers page; their narrative does not change any coverage or verification state. Material source-only writing for this review scope is complete.

Update 8 October 2026: Proposed Canon & Protocol Invariants v0.1 has been prepared and moves the architecture-invariants row to Covered at documentation level only (45 Covered / 8 Partial / 0 Missing; verification unchanged). The next explicit owner gate is: Adopt, amend or reject Proposed Canon & Protocol Invariants v0.1. This is not publication approval, source acceptance, GitHub approval or operational launch approval. The eight remaining gaps — Merkle snapshot spec, exceptions/reversals/disputes procedure, node deployment roadmap, security disclosure process, IP/licensing/title, Sig-56 and F.I.P. normative specs, eIDspot credential/revocation spec — stay open, and operational consensus/finality and implementation evidence remain required before any network claim.

Canonical model coverage

Release-control register

Documented architecture

CoveredOwner-asserted

Ten independent control states

Owner-confirmed public documentation site; source/operational and RC1 acceptance remain separate

Release Control

Public-site SEO verification runbook

Planned

CoveredOwner-asserted

Twelve preservation and validation checks

Existing canonical origin https://byteshares.org; no new domain action

Release Control

October 2026 documentation RC1 completion path

Documented architecture

CoveredOwner-asserted

Tracks A–E with dependencies

Derived from existing gates and decisions

Readiness & Acceptance

Acceptance evidence model

Documented architecture

CoveredOwner-asserted

Twelve areas across five evidence levels

No area beyond documentation or partial source evidence

Readiness & Acceptance

Source-intake record template

Planned

CoveredOwner-asserted

Nineteen-field reusable record

Template only; no record completed

Source & Repositories

Protocol system flow

Documented architecture

CoveredOwner-asserted

Seven-stage responsibility flow

Existing conceptual flow; Proposed Canon v0.1 exists, owner adoption pending; no operational flow evidence

Protocol Architecture

Architecture principles / protocol invariants

Documented architecture

CoveredOwner-asserted

Invariant list

Proposed Canon v0.1 prepared 8 Oct 2026; owner adoption pending. Separate private July 2026 masterplan-derived summary: OWNER PROVIDED / UNVERIFIED extracts; full-source and public-disclosure review pending. No implementation or conformance evidence.

Protocol Architecture

VPLedger proof + execution

Documented architecture

CoveredUnverified

Invariants and proof objects

Provenance audit open

VPLedger

Proof-object lifecycle examples

Documented architecture

CoveredOwner-asserted

Four worked lifecycles

Schemas to be specified

VPLedger

Merkle snapshot model

Documented architecture

PartialOwner-asserted

Epoch proof primitive

Requires a snapshot specification defining record-set selection, ordering/canonicalisation, hashing, inclusion encoding, epoch closure and trusted-root establishment; no verifier or vectors supplied.

VPLedger

Storage & data sovereignty

Documented architecture

CoveredOwner-asserted

Anchor vs evidence table

Custody, disclosure and historical-proof limits are documented and linked to security classification. Retention policy, retrieval guarantees and any storage rail remain unspecified.

VPLedger

Filecoin positioning

Planned

CoveredNo source

Conditional storage option

No rail contracted or in use

Protocol Architecture

Governance architecture

Documented architecture

CoveredOwner-asserted

Authority domains and epoch sequence

Governance paper pending

Governance Layer

Governance technical flow

Documented architecture

CoveredOwner-asserted

Proposal to closure steps

No implementation

Governance Layer

Exceptions, reversals & disputes

Planned

PartialUnverified

Pathway requirements

Requires an owner-approved procedure naming exception authority, stay/review powers, dispute forum, response/appeal timetable and authorization of compensating decisions.

Governance Layer

Node architecture

Documented architecture

CoveredUnverified

Roles, diagram, boundaries, lifecycle

Topology draft not supplied

Node Architecture

Node deployment roadmap

Planned

PartialUnverified

Staged sequence, unnamed sites

Requires the dated topology/deployment plan, owner-approved operator/site scope, host or site confirmations, and stage entry/exit criteria; no locations or dates can be assigned from existing material.

Node Architecture

Security / threat model

Documented architecture

CoveredUnverified

Objectives, boundaries, threats, invariants

Conceptual threat-to-layer trace is documented. Asset classification, attack analysis, implementation controls, residual-risk assessment and independent testing remain unverified; this is not a completed security assessment.

Security

Security disclosure process

Planned

PartialNo source

Stated intent, no contact

Requires Ronny's decision naming a staffed recipient/contact route, covered systems, handling owner, response commitment and disclosure/escalation rules; no address or timetable is invented.

Security

Developer overview & lifecycle

Planned

CoveredUnverified

Quick-start and integration steps

No implementation

Developers

API surfaces

Planned

CoveredNo source

Conceptual surfaces, object relationships and illustrative request/response shapes

Review-draft conceptual shapes only; no final contract, schema or endpoints

Developers

SDK structure

Planned

CoveredNo source

Responsibilities, exclusions and offline-verification intent with open trust requirements

Proposed responsibility-to-document mapping now defines proof, authority and inclusion roles and exclusions. Languages, packages, schemas, verifier code and test vectors remain unassigned.

Developers

Error & versioning policy

Planned

CoveredNo source

Policy framework table

A proposed decision boundary ties refusal to rule context and separates contract/specification/software versions from documentation RC1. Codes, version scheme and support periods remain owner/specification decisions.

Developers

Explorer

Planned

CoveredUnverified

Query categories and privacy limits

No ledger to index

DLT Explorer

Network status

Planned

CoveredUnverified

Status, incident and version model

No telemetry source

Network Status

Repository architecture

Awaiting approval

CoveredOwner-asserted

Twelve proposed repositories

Names proposed; no repo exists

Source & Repositories

Source inventory

Planned

CoveredVerified

Candidate source set list

The five recorded roots and counts are mapped to proposed targets, bounded to the historical 17 September 2026 recovery report. Canonical scope and repository intake remain pending.

Source & Repositories

Provenance classification

Documented architecture

CoveredUnverified

A/B/C/D/X legend

A/B/C/D/X meanings, consequences and intake criteria are documented. All candidates remain C; classification decisions require repository-level history, title/licence and review evidence.

Source & Repositories

Integrity / hash evidence

Planned

CoveredVerified

Estate hashes and manifest evidence

Recorded estate hashes and manifest scope are documented; a hash does not prove authorship, title, safety or runnability. Per-root-to-baseline linkage and reviewer evidence remain pending.

Source & Repositories

IP & licensing

Awaiting approval

PartialOwner-asserted

Ownership and licensing evidence record

Requires component-linked contractor assignments, collaboration agreements, applicable bankruptcy/project-rights transfers, third-party licence/dependency review and a reviewed title/licence disposition. The four archive records alone do not close this gap.

Source & Repositories

Secrets exclusion

Documented architecture

CoveredVerified

Restricted index and Class X handling rules

Class X, metadata-only recording, quarantine and never-publish rules are documented. Authorized per-root scans, exclusion records and reviewer sign-off remain pending; no clean-source claim.

Source & Repositories

Versioning policy

Planned

CoveredOwner-asserted

SemVer, spec status, release bindings, matrix

DLT software/contract versions unassigned; documentation candidate is 0.9 RC1

Source & Repositories

Branch & change control

Planned

CoveredOwner-asserted

Proposed governance baseline

No GitHub settings active

Source & Repositories

Repository minimum docs

Planned

CoveredOwner-asserted

Expected-file table

No repository to hold them

Source & Repositories

Legacy source mapping

Planned

CoveredVerified

Inventoried candidate roots to proposed targets

Each of the five inventoried roots has a proposed target, class C, specific gaps and hold disposition. Other OpenLedger roots remain archive/reference candidates until scope and evidence are reviewed.

Source & Repositories

Source intake sequence

Planned

CoveredOwner-asserted

Nine-step safe working order for the five candidate roots

Sequence documented; intake not authorised or started

Source & Repositories

Repository acceptance record

Planned

CoveredOwner-asserted

Per-source-set record template

Template only; no record completed

Source & Repositories

GitHub connection

Awaiting approval

CoveredNo source

Gate G10

Awaiting approval / Not connected; no official ByteShares repository verified through the connected account

Source & Repositories

Repository import acceptance

Awaiting approval

CoveredNo source

Gates G11 and acceptance criteria

Nothing imported

Source & Repositories

GitHub to ByteShares.org link validation

Awaiting approval

CoveredNo source

Documentation mapping criterion

A proposed mapping record and checks now separate documentation intent, accepted source and operational claims. Actual URL/commit/branch checks require authorized repository acceptance; no external links are activated.

Source & Repositories

Future source and operational release acceptance

Awaiting approval

CoveredNo source

Gate G12, independent of public documentation launch

Future scope blocked pending source and operational evidence; existing public domain/indexing unaffected

Source & Repositories

Sig-56

Documented architecture

PartialOwner-asserted

Canonical specification structure

Requires the source specification defining signature profile, signed content, serialization/canonicalisation, verification and version rules, plus conformance criteria and test vectors.

Standards

Web4

Documented architecture

CoveredUnverified

Positioning term entry

No ratified definition

Standards

FAWN Identity Protocol (F.I.P.)

Documented architecture

PartialOwner-asserted

Concept blocks and spec structure

Requires the source specification defining agent identifiers, curation/authority records, permitted-memory enforcement, lifecycle/revocation semantics and conformance criteria.

Standards

eIDspot identity model

Documented architecture

CoveredOwner-asserted

Subject classes and mandate chain

Canon document not supplied

Identity Layer

eIDspot credential & revocation

Planned

PartialNo source

Lifecycle table

Requires issuer trust/acceptance rules, credential and presentation formats, validity/renewal policy, revocation publication and freshness rules, historical verification semantics and key-custody/recovery decisions.

Identity Layer

VPL, TIB, PIB, JOYY, CTZ, GROW

Documented architecture

CoveredOwner-asserted

Canonical function register

Canon document not supplied

Protocol Architecture

FIL/ETH/BTC/RWA bridges

Planned

CoveredNo source

Conditional bridge concepts

No implementation or approval

Protocol Architecture

eDEV / UCityX

Planned

CoveredNo source

Function and product concept

No operational evidence

Protocol Architecture

AI City end-product family

Planned

CoveredOwner-asserted

Extensible modular and white-label concept

Owner interim-platform canon; no deployment verified

Protocol Architecture

Technical paper register

Awaiting approval

CoveredUnverified

Five Draft / Awaiting approval review manuscripts: narrative, claim traces, boundaries, evidence requests and review checklists

Full conceptual review manuscripts exist in source/preview, synthesized from existing documentation; underlying source verification unchanged, no paper released

Technical Papers

Glossary & versioning fields

Documented architecture

CoveredOwner-asserted

Term table plus page meta fields

Software and specification versions remain unassigned; documentation RC1 is separate

Glossary

Evidence register

Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.

Claims on this page and the verification state of their sources
ClaimSource typeVerificationNote
Coverage rows reflect the canonical content requested for the documentation platformOwner instructionVerified source on fileDestinations and coverage states reviewed against the supplied completeness list.
Underlying specifications and implementations are completeReleased specifications and operational evidenceNo source on fileCoverage tracks documentation only; the verification column records what remains unproven.