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
FILDEX
Planned
CoveredNo source
Discovery/exchange 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