Skip to content

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

ByteShares.org

Builders

Technical Papers

Awaiting approval

Five full conceptual review manuscripts, claim-traced to existing ByteShares.org documentation. Draft / Awaiting approval. These source/preview drafts are not released papers or independently verified technical sources.

Documentation drafts only

Every manuscript is Draft / Awaiting approval: not a standards ratification, software release, security assessment, operational specification or legal opinion. No individual paper version, author assignment, publication date, PDF, download, DOI or endorsement is assigned. The public documentation site remains live; these manuscript changes are preview only.

Source / verification
Existing project documentation and owner-recorded archive boundaries; manuscript synthesis only, underlying verification unchanged
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.

Architecture to evidence — reading path

Proposed / Non-operational: identity → scoped authority and rule context → decision outcome → evidence → bounded closure.

eIDspot describes identity/access; governance defines bounded mandates; VPLedger describes proof/evidence/audit relationships; nodes and DLT remain planned. AI City applications are intended consumers of this architecture, not deployed services. Cooperative membership and one-member-one-vote belong to ByteShares.dk; a ProductCo or application does not inherit cooperative authority.

Claim trace
Connects a specific conceptual statement to its source reference and stated limits; it is not an independent verification result.
Document review date
Records a documentation review, not a source acceptance date, legal approval or software release.
Historical documented design
A source- and edition-bounded earlier proposal; not a current parameter, delivered capability or adopted 2026 rule.
Operational evidence
Assessed implementation, test and operating records supporting a specific claim; prose and document versions are not substitutes.

Historical source editions describe earlier designs. Proposed models remain unadopted; the live documentation site is not evidence of a running DLT. Documentation 0.9 RC1, Proposed Canon v0.1 and historical paper editions are separate version contexts. “Last reviewed” records documentation review, not implementation acceptance.

Five RC1 review manuscripts

Claim traces establish where a concept is documented, not whether its underlying source has been independently verified. All eight Partial rows and all verification states remain unchanged. Each evidence dependency below repeats the current partial-audit wording; it is not resolved by manuscript length.

Separate masterplan-derived review draft — Proposed / Not adopted

VPLedger 2019 foundation and 2026 lineage — historical source comparison

Review manuscript 01

ByteShares Architecture

Awaiting approvalDraft / Awaiting approval

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.

ByteShares Architecture: conceptual claims, source sections and evidence limits
Material conceptual claimExisting documentationClaim 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.

Exact partial-audit registerAffected source scope

Review checklist — pending review

  1. Confirm that the manuscript reflects the linked documentation without widening any claim.
  2. Confirm that Proposed, Planned, Draft and Non-operational labels remain attached to conceptual material.
  3. Resolve or retain each cited partial-audit blocker; do not infer an answer from this manuscript.
  4. Check every material claim against its linked section before any release decision.
  5. Record explicit owner approval separately; review completion is not publication approval.

Review manuscript 02

eIDspot Identity Layer

Awaiting approvalDraft / Awaiting approval

Documentation draft — not a standards ratification, software release, security assessment, operational specification or legal opinion. Core model: Proposed / Non-operational.

Title
eIDspot Identity Layer
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
Consolidate the documented subject, credential, mandate, privacy and lifecycle model into a reviewable identity-layer narrative.

Executive abstract

eIDspot is documented as an identity and scoped-authority concept. Credentials describe a subject or eligibility; mandates and policy determine what an action may do. The model separates identification, authority, validity and evidence so a key, wallet address or session does not become entitlement by itself. No identity service, credential rail or regulatory conformance is claimed.

Purpose and scope

Purpose. Consolidate the documented subject, credential, mandate, privacy and lifecycle model into a reviewable identity-layer narrative.

Scope. Subject classes; identity-to-evidence relationships; credentials, presentations, mandates and policy; minimum-disclosure intent; issuance, renewal, revocation, recovery and historical-verification questions.

Core documented model — Proposed / Non-operational

Identity and authority are separate questions

The model distinguishes an identifier, a credential and a presentation. A credential may describe a subject or eligibility, while a presentation is intended to disclose only what a decision requires. A mandate then binds authority, scope and rule context to a proposed action.

The documented subject classes include humans, institutions and contributors, with AI-adjacent agents treated as a planned F.I.P. concept whose specification is unavailable. Listing a subject class does not establish an issuer, entitlement or identity service.

The documented chain is Identity → Mandate → Policy → Action → Evidence. This ordering prevents proof of identity from being read as permission and prevents a later evidence record from retroactively creating authority.

Lifecycle and privacy intent

Verification, issuance, presentation, renewal and revocation are recognized lifecycle stages. Minimum disclosure and source custody are documented goals, while issuer acceptance, formats, status publication, freshness, recovery and offline time semantics remain undecided.

Historical proof and current eligibility must remain separate: an earlier inclusion or valid credential cannot, by itself, establish present authority after expiry, revocation or mandate change.

Boundaries / what is NOT claimed

  • No credential, issuer, presentation or revocation format is specified.
  • No sign-in or identity service runs on ByteShares.org; cooperative member access belongs to ByteShares.dk.
  • No compliance with national, EU or other identity frameworks is claimed.
  • No key-custody, recovery, correlation-resistance or offline-verification result is claimed.

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.

eIDspot Identity Layer: conceptual claims, source sections and evidence limits
Material conceptual claimExisting documentationClaim limit
Identifiers, credentials and presentations have distinct conceptual roles.No format or issuer trust model is defined.
Human, institutional and contributor subjects are documented; AI-adjacent agents remain a planned concept.No class establishes an issuer trust rule or entitlement by itself.
Historical evidence cannot by itself establish current authority after expiry, revocation or mandate change.Validity, revocation freshness and historical time semantics remain unsupplied.
Identity, mandate, policy, action and evidence form a responsibility chain.A conceptual relationship, not an executable authorization contract.
The lifecycle includes issuance, presentation, renewal and revocation questions.Mechanisms and time semantics are TBD / Requires source.
Privacy intent favors minimum disclosure and source custody.No selective-disclosure implementation or assessment is claimed.

Open questions / evidence required

  • Who may issue and verify each credential class, under which acceptance rules? TBD / Requires source
  • How are validity, renewal, revocation freshness and historical verification represented? TBD / Requires source
  • Who controls key rotation and recovery, and how is administrative authority bounded? TBD / Requires source

eIDspot credential & revocation — remains Partial

TBD / Requires source. 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.

Exact partial-audit registerAffected source scope

Review checklist — pending review

  1. Confirm that the manuscript reflects the linked documentation without widening any claim.
  2. Confirm that Proposed, Planned, Draft and Non-operational labels remain attached to conceptual material.
  3. Resolve or retain each cited partial-audit blocker; do not infer an answer from this manuscript.
  4. Check every material claim against its linked section before any release decision.
  5. Record explicit owner approval separately; review completion is not publication approval.

Review manuscript 03

VPLedger Evidence Layer

Awaiting approvalDraft / Awaiting approval

Documentation draft — not a standards ratification, software release, security assessment, operational specification or legal opinion. Core model: Proposed / Non-operational.

Title
VPLedger Evidence Layer
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
Present the documented evidence-layer model and its provenance limits as one claim-traced review draft.

Executive abstract

VPLedger is documented as an append-only proof, evidence and audit concept. Proof objects relate an input, authority, rule context and outcome; epoch snapshots are intended to support selective inclusion checks; full evidence remains distinct from compact commitments. Archive records support chronology and conceptual lineage, not complete legal title to historical software.

Purpose and scope

Purpose. Present the documented evidence-layer model and its provenance limits as one claim-traced review draft.

Scope. Append-only records, proof-object lifecycles, epoch closure and snapshot intent, anchors and retained evidence, custody limits, archive provenance, source acceptance and title/licensing gaps.

Core documented model — Proposed / Non-operational

Proof context and lifecycle

The evidence model separates execution from proof. A proof object is intended to retain enough context to relate an input, the authority and rule under which it was considered, the resulting outcome and a durable evidence reference. Contract, governance, eligibility and audit-extract examples illustrate that relationship without fixing a schema.

These examples are documentation shapes only. They do not demonstrate deterministic execution, an accepted verifier, an accounting system or a deployed ledger.

Snapshots, custody and provenance

A Merkle snapshot is described as a compact commitment to a defined record set at an epoch boundary, intended to permit selective inclusion checks. Construction, ordering, canonicalisation, hashing, trusted-root establishment and verification vectors are not supplied and therefore remain non-normative.

A matching commitment may support content matching; it does not prove the evidence true, establish ownership, preserve retrievability or confer current authority. The four 2026 archive records support founder/originator chronology and conceptual lineage into the modular architecture. Contractor assignments, collaboration agreements, transfers and component-level licence review remain open.

Boundaries / what is NOT claimed

  • No proof schema, snapshot format, hashing profile, trusted-root rule or verifier is specified.
  • No storage availability, retention, retrieval or evidence-truth guarantee is claimed.
  • Archive possession, chronology and hashes do not establish authorship, safety, runnability, licence or legal ownership of every component.
  • No historical candidate source set is accepted as canonical; candidates remain class C.

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.

VPLedger Evidence Layer: conceptual claims, source sections and evidence limits
Material conceptual claimExisting documentationClaim limit
VPLedger separates append-only evidence relationships from execution claims.Documented invariants are not an operating engine.
Proof objects retain authority, rule and outcome context across several conceptual lifecycles.Examples do not assign wire fields, encodings or executable behavior.
Snapshots are intended to support compact commitments and selective inclusion checks.Construction and acceptance semantics are TBD / Requires source.
Matching a commitment or checking inclusion does not prove truth, legal title, current authority or continued retrievability.Retention policy, disclosure obligations and retrieval guarantees remain unspecified.
Provenance evidence and legal ownership are separate review questions.The four archive records do not close component-level title or licensing gaps.

Open questions / evidence required

  • What record set, ordering, canonicalisation and hashing rules define a snapshot? TBD / Requires source
  • Who establishes a trusted root, and what verifier and vectors test inclusion? TBD / Requires source
  • Who retains underlying evidence, for how long and under which retrieval obligations? TBD / Requires source
  • Which component-linked assignments, transfers and licences support historical source acceptance? TBD / Requires source

Merkle snapshot model — remains Partial

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

Exact partial-audit registerAffected source scope

IP & licensing — remains Partial

TBD / Requires source. 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.

Exact partial-audit registerAffected source scope

Review checklist — pending review

  1. Confirm that the manuscript reflects the linked documentation without widening any claim.
  2. Confirm that Proposed, Planned, Draft and Non-operational labels remain attached to conceptual material.
  3. Resolve or retain each cited partial-audit blocker; do not infer an answer from this manuscript.
  4. Check every material claim against its linked section before any release decision.
  5. Record explicit owner approval separately; review completion is not publication approval.

Review manuscript 04

Sig-56 / Web4 / F.I.P. Position Paper

Awaiting approvalDraft / Awaiting approval

Documentation draft — not a standards ratification, software release, security assessment, operational specification or legal opinion. Core model: Proposed / Non-operational.

Title
Sig-56 / Web4 / F.I.P. Position Paper
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
Clarify how the three terms are currently used in ByteShares documentation and prevent conceptual association from being mistaken for standards status or implementation.

Executive abstract

Sig-56, Web4 and F.I.P. are documented as concepts and positioning terms, not ratified standards. Sig-56 concerns binding identity, authority, rule context and intent to an action; Web4 frames verified identity and accountable participation; F.I.P. considers agent identity, curation, memory and authority boundaries. No formal specification, conformance result, adoption or endorsement is claimed.

Purpose and scope

Purpose. Clarify how the three terms are currently used in ByteShares documentation and prevent conceptual association from being mistaken for standards status or implementation.

Scope. Conceptual lifecycle and dependencies for Sig-56; bounded use of Web4; agent identity, curation, memory and authority concepts for F.I.P.; relationships to eIDspot, governance and evidence.

Core documented model — Proposed / Non-operational

Sig-56 and Web4 positioning

Sig-56 describes an intended sequence from intent and authority checking through binding, acceptance, anchoring and later verification. The sequence indicates the questions a future specification must answer; it does not define signed content, canonical encoding, signature profile or conformance.

Web4 is used only as a positioning term for verified identity and accountable participation. It carries no normative requirements in this documentation and should not be read as external standards recognition.

F.I.P. authority boundaries

F.I.P. treats an AI agent as a governed participant whose identifier, curator, source and memory boundaries, lifecycle and permitted actions would need explicit control. Memory does not create authority, and behavioral constraints are not interchangeable with a signed mandate.

This model is conceptual and non-operational. No agent registry, certification, enforcement service, record format or revocation mechanism exists in the documented platform.

Boundaries / what is NOT claimed

  • No term is represented as a ratified, adopted or certified external standard.
  • No signature algorithm, serialization, identifier format, conformance profile or test vector is selected.
  • Owner-supplied naming and association do not verify technical content or confer external endorsement.
  • No AI identity registry, agent certification or enforcement service is claimed.

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.

Sig-56 / Web4 / F.I.P. Position Paper: conceptual claims, source sections and evidence limits
Material conceptual claimExisting documentationClaim limit
Sig-56 concerns identity, authority, rule context and intent bound to an action.Purpose and lifecycle are documented; normative binding rules are absent.
Web4 is a positioning term rather than a specification.Its public definition and continued use remain an owner terminology decision.
F.I.P. separates agent identity, curation, memory and consequential authority.No implementable agent/curator authority model is defined.
Identity and evidence layers are conceptual dependencies for these models.Cross-document relationships do not establish a built integration.

Open questions / evidence required

  • What signed content, canonicalisation, verification and version rules define Sig-56? TBD / Requires source
  • What identifiers, curator records, memory controls and revocation semantics define F.I.P.? TBD / Requires source
  • Should Web4 remain a public positioning term, and under what owner-approved definition? TBD / Requires source

Sig-56 — remains Partial

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

Exact partial-audit registerAffected source scope

FAWN Identity Protocol (F.I.P.) — remains Partial

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

Exact partial-audit registerAffected source scope

Review checklist — pending review

  1. Confirm that the manuscript reflects the linked documentation without widening any claim.
  2. Confirm that Proposed, Planned, Draft and Non-operational labels remain attached to conceptual material.
  3. Resolve or retain each cited partial-audit blocker; do not infer an answer from this manuscript.
  4. Check every material claim against its linked section before any release decision.
  5. Record explicit owner approval separately; review completion is not publication approval.

Review manuscript 05

Governance & Node Architecture

Awaiting approvalDraft / Awaiting approval

Documentation draft — not a standards ratification, software release, security assessment, operational specification or legal opinion. Core model: Proposed / Non-operational.

Title
Governance & Node 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
Present governance authority and node responsibility as one reviewable model while preserving the boundary between ByteShares.dk participation and ByteShares.org technical documentation.

Executive abstract

The documented model separates legal or cooperative authority from protocol execution. Proposals, eligibility and thresholds lead to recorded decisions and evidence; planned node roles separate admission, execution, retention, read and observation responsibilities. The model is a staged architectural intent, not a live topology, governance system or operating network.

Purpose and scope

Purpose. Present governance authority and node responsibility as one reviewable model while preserving the boundary between ByteShares.dk participation and ByteShares.org technical documentation.

Scope. Governance objects and authority domains; proposal-to-evidence flow; exception and dispute needs; node roles, topology, lifecycle and trust boundaries; resilience, deployment and security-disclosure dependencies.

Core documented model — Proposed / Non-operational

Authority precedes execution

The governance model distinguishes constitutional, board or committee, and protocol authority. Proposal, role, threshold and record objects describe how a decision could be represented. A technical flow carries a proposal through decision, authorization, execution, evidence and closure without allowing protocol data to create legal authority by itself.

Cooperative membership and formal participation remain on ByteShares.dk. The technical layer neither conducts nor mirrors those activities and has not been reviewed against complete governing documents.

Node responsibility and staged intent

Validating, archive, read and observer roles are documented with explicit limits. Planned topology zones separate acceptance, retention, read and observation concerns; lifecycle and resilience sections describe eligibility, admission, synchronization, operation, review and exit as intended responsibilities.

No node software, consensus mechanism, operator set, peer protocol, site, host or deployment date is established. Divergence handling, operator compromise, exceptions, dispute review and a staffed disclosure route require procedures or decisions that existing prose cannot supply.

Boundaries / what is NOT claimed

  • No governance vote, authority registry, exception body or dispute forum is operating here.
  • No node, topology, operator, site, host, consensus mechanism, uptime or network metric is claimed.
  • Node execution cannot create legal or cooperative authority.
  • This manuscript is not a security assessment, deployment plan or operator acceptance record.

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.

Governance & Node Architecture: conceptual claims, source sections and evidence limits
Material conceptual claimExisting documentationClaim limit
Governance authority and cooperative participation remain distinct from protocol execution.No statutes-alignment or implementation review is implied.
A conceptual flow links proposal, decision, authorization, execution and evidence.No stage is operating or binding.
Node roles and zones have distinct responsibilities and prohibited powers.The underlying topology draft has not been supplied for verification.
Lifecycle and resilience are staged intentions, not operational results.No test, deployment evidence or accountable disclosure process exists.

Open questions / evidence required

  • Who may stay, review or authorize a compensating decision, and under which procedure? TBD / Requires source
  • Which operators, sites and stage-entry criteria belong in a dated deployment plan? TBD / Requires source
  • What consensus, divergence, halt, reconciliation and operator-removal rules are intended? TBD / Requires source
  • Who receives security reports, for which systems and under which response and escalation rules? TBD / Requires source

Exceptions, reversals & disputes — remains Partial

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

Exact partial-audit registerAffected source scope

Node deployment roadmap — remains Partial

TBD / Requires source. 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.

Exact partial-audit registerAffected source scope

Security disclosure process — remains Partial

TBD / Requires source. 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.

Exact partial-audit registerAffected source scope

Review checklist — pending review

  1. Confirm that the manuscript reflects the linked documentation without widening any claim.
  2. Confirm that Proposed, Planned, Draft and Non-operational labels remain attached to conceptual material.
  3. Resolve or retain each cited partial-audit blocker; do not infer an answer from this manuscript.
  4. Check every material claim against its linked section before any release decision.
  5. Record explicit owner approval separately; review completion is not publication approval.

Proposed Canon & Protocol Invariants v0.1 — Masterplan-derived review draft

PROPOSED / DRAFT / NOT ADOPTED / NON-OPERATIONAL

A separate owner-review supplement, dated 8 October 2026. It does not alter or adopt the existing Proposed Canon v0.1, ratify a protocol, establish a bylaw, release software, constitute a legal opinion or demonstrate implementation.

Private source
ByteShares Cooperative & AI City Infrastructure Master Business Plan | v2.1 | July 2026 | Final Canonical Edition - Institutional Use
Provenance classification
OWNER PROVIDED / UNVERIFIED
Disclosure scope
Owner-supplied doctrine summary and chapter references only. No full text, investor examples, financial allocations, equity terms or commercially confidential specifics.
Owner gate
Confirm source fidelity and authorized public-summary scope; adopt, amend or reject the proposed supplement and its normative candidates separately.

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.

Claim-source trace — extracted doctrine and candidates

“Directly supported doctrine” means supported by the owner-provided extracted rule, not independently checked against the full masterplan or adopted into the protocol. Other classifications identify derivation, a normative decision or independent evidence needed.

Masterplan-derived review claims with chapter references, classification and limits
Review claimSource referenceReview classificationBoundary / unresolved requirement
One identity-valid, verified cooperative member has one vote; decision authority is bounded and auditable. Constitutional/bylaw, board/executive and proposed protocol layers remain distinct.Ch6.1–6.2; Ch27.4directly supported doctrineProtocol enforcement is future intent. Identity uniqueness, membership eligibility and compliance are not demonstrated.
Strategic decisions may be triggered by a module launch, capital tranche request or governance rule change. A board or properly mandated committee reviews a memo, constraint checks and prior epoch closure references before approval.Ch6.3directly supported doctrineRejection permits no unauthorized spending or deployment. Decision record, hash, ledger anchor and Filecoin snapshot reference are desired artifacts, not artifacts claimed to exist.
Constitutional decisions require member vote; strategic decisions use member-guided board approval; operational decisions stay within executive mandate. ProductCo decisions cannot change cooperative constitutional rights.Ch6.4; Ch7directly supported doctrineFormal precedence, delegation and voting thresholds need normative owner decisions. No equity or financial terms are reproduced.
PreDAO → Memo → Epoch describes conceptual maturity. An epoch carries objectives, budget, milestones, closure criteria and proof.Ch6.5directly supported doctrineNot an operational DAO. Epoch timing, closure and proof requirements remain proposed and unresolved.
Anti-capture, network neutrality and non-dominance exclude cooperative constitutional privilege or hidden discretionary control based on capital, tokens, founder proximity, operators, municipalities or ProductCos.Ch6.6; Ch6.6.1directly supported doctrineNo implemented anti-capture mechanism or tested enforcement is claimed.
Exception, correction, reversal, emergency and dispute handling must be bounded and auditable, with named authority, escalation, standards, timelines and remedies.Ch6.8.1requires normative owner decisionTBD: actual authority, procedure, timelines, remedies and SLAs. This does not close the exceptions/reversals/disputes blocker.
Cooperative and ProductCo separation and IP/title truthfulness constrain review. Commercial ownership allocations are historical July 2026 references subject to final legal documentation, not immutable invariants.Ch7directly supported doctrineNo commercial allocations, equity terms or investor examples disclosed. Provenance is not complete legal title.
A staged ten-year founder-to-cooperative VPLedger stewardship intention depends on contracts and legal documentation; founder authority remains constitutionally bounded and subject to succession.Ch26requires independent technical/legal evidenceNo completed transfer or settled chain of title asserted. Historical intent is not current ownership proof.
Verified person and active cooperative membership determine voting eligibility; deduplication and membership-state rules need precise definition and implementation/compliance evidence.Ch27.4requires independent technical/legal evidenceNo implemented identity uniqueness, membership-state or credential/revocation specification accepted.
Regulated settlement/payment rails depend on licensing and partners. VPL, TIB, PIB, JOYY, CTZ and GROW are proposed architectural categories subject to legal review.Ch27.5–27.6requires independent technical/legal evidenceNot live instruments or rails, accepted invariant parameters, authorization to issue, or payment activation.
Participation and economic rights are distinct from cooperative governance and conditional on legal and accounting rules.Ch27.7directly supported doctrineNo economic entitlement, return, allocation or accounting conclusion is asserted.
Entity-specific contracting, retention, disputes and SLAs need owner-approved legal and operational policies.Ch27.8requires normative owner decisionTBD: responsible entity, jurisdiction, retention policy, dispute route and service commitments; independent legal review remains required.
The fail-closed decision sequence below and linked additive correction events are illustrative candidates for canon review.Derived from Ch6.3, Ch6.5, Ch6.8.1; existing Proposed Canon v0.1derived candidateThe precise state sequence is not asserted to be specified by the masterplan. No new invariant identifiers, adopted state machine or executable schema are introduced.

Illustrative fail-closed decision-state model — proposed only

Derived candidate for owner review, not a precise sequence asserted to exist in the masterplan. All state names, transitions, input categories, preconditions and tests below are PROPOSED / NOT ADOPTED / NON-OPERATIONAL; no executable state machine is supplied.

DRAFT → SUBMITTED → ELIGIBILITY_CHECK → AUTHORITY_CHECK → CONSTRAINT_CHECK → APPROVED / REJECTED

APPROVED → EXECUTION_PENDING → EVIDENCE_RECORDED → EPOCH_CLOSED

REJECTED never proceeds to execution. A refusal record remains required as a proposed auditable outcome, not as proof that recording infrastructure exists. Missing, failed or unresolved required inputs/checks block approval and execution; exact error/hold semantics are TBD. EXECUTION_PENDING is not completed execution. EVIDENCE_RECORDED and EPOCH_CLOSED require the as-yet-unapproved evidence and closure rules.

Correction or reversal is a new linked auditable event identifying the prior decision, named authority, reason and applicable context; never silent history rewriting. Emergency, escalation, dispute, timing and remedy procedures remain TBD / Requires source and owner decision.

Decision input categories and preconditions — proposed

Proposed conceptual decision inputs, not a final schema
Input categoryRequired review context
Subject and eligibilityVerified-person evidence, identity-uniqueness basis, active membership and decision-specific eligibility.
Authority and mandateDecision class, named board/committee/executive authority, delegation scope, expiry and revocation context.
Intent and scopeMemo, triggering request, module/resource/entity domain, objectives and requested action; no confidential financial values reproduced.
Binding contextApplicable constitutional/bylaw and proposed rule version, prior state, time/validity context and replay/idempotency reference.
Constraints and epochRequired checks, prior epoch closure references, milestones, proposed closure criteria and proof obligations.
Evidence and custodyInput commitments, decision/refusal record, proposed hash/anchor/snapshot references, custody and retention context. Schemas and trust rules TBD.

Proposed preconditions: classify the decision and responsible entity; establish eligible subject and scoped current authority; bind the applicable rules and prior state; provide the memo and required epoch references; satisfy all applicable constraints before approval. No inferred mandate or constitutional privilege may replace a missing check. Evidence must support an outcome without implying that a commitment proves truth or legal title.

Invariant review tests — proposed, not executed

  • Eligibility: a cooperative vote cannot pass on missing, inactive or unresolved membership/identity evidence; deduplication semantics remain TBD.
  • Authority: identity alone confers no mandate; out-of-scope, expired or revoked delegation cannot authorize action.
  • Constitutional separation: ProductCo, capital, token, founder, operator or municipal influence cannot confer cooperative constitutional privilege.
  • Fail-closed checks: required memo, constraint result, binding context or prior epoch reference missing or unresolved means no approval or execution.
  • Decision/execution separation: rejection does not reach execution; approval alone does not prove authorized execution, settlement or deployment occurred.
  • History: correction/reversal creates a new linked auditable event with named authority and reason, never a silent rewrite; procedures remain TBD.
  • Evidence limits: record/hash/ledger/Filecoin references do not alone prove underlying truth, availability, title or current authority; independent trust/schema evidence is required.
  • Epoch closure: closure requires the approved criteria and required evidence, not an assumed timeout or operational DAO claim.

No test vectors, pass results, cryptographic parameters or conformance certification are claimed.

Unresolved owner decisions and independent evidence

Exact unresolved owner decisions for the masterplan-derived canon review
Decision areaExact approval / evidence question
Formal bylaw precedenceWhich approved constitutional/bylaw instruments prevail, and how are conflicts with board mandates or proposed protocol rules resolved?
Voting identity and membershipWhat deduplication, active membership, eligibility, suspension and revocation rules govern each vote, and what evidence demonstrates compliance?
Board/committee delegated mandatesWho may delegate to which body, for what scope and duration, with which revocation and non-amplification limits?
Voting thresholdsWhat quorum, threshold and voting procedure applies to each decision class?
Exception/reversal authority and SLAsWho may authorize exceptions, corrections, reversals or emergency action; what escalation, deadlines, standards and remedies apply?
Epoch timing and closureWho opens/closes an epoch, on which timing rules, objectives, milestones, proof and failure/rollover criteria?
Evidence schema and trustWhat schema, hash canonicalization, ledger anchoring, Filecoin reference trust, custody, availability and historical verification rules are accepted?
Legal chain of titleWhich assignments, contracts, licenses, stewardship and succession instruments establish each entity's rights, without assuming any transfer has occurred?
Release governanceWho adopts, amends, versions and releases the canon or future implementation, with which prospective migration and historical-proof obligations?
Jurisdictional complianceWhich entity, licensing/partner, contracting, retention, accounting, dispute and SLA policies apply in each jurisdiction?

All unresolved operational specifics remain TBD / Requires source. Doctrine does not close snapshot construction, exception/dispute procedure, deployment, security disclosure, IP/licensing/title, Sig-56, F.I.P. or eIDspot credential/revocation blockers. Independent implementation, consensus/finality and legal/compliance evidence remain required.

Owner-review checklist — pending

  1. Confirm that each chapter reference and limited summary faithfully represents the private source and is within the authorized public-disclosure scope.
  2. Confirm the separation of extracted doctrine, derived candidates, normative decisions and independent technical/legal evidence.
  3. Adopt, amend or reject the separate supplement, including the proposed decision sequence, input categories, preconditions and invariant review tests; no adoption is inferred.
  4. Answer or explicitly defer the ten decision areas above, retaining the precise independent blockers until specifications, policies or evidence are accepted.
  5. Keep canon adoption, source acceptance, legal review, implementation/conformance and publication approval as separate decisions.

VPLedger 2019 foundation and 2026 lineage

Historical source trace · Review summary · 8 October 2026

Original source directly inspected for whitepaper and PDF memo — inspection reported by the owner. Copyright/title unresolved; current implementation unverified. This update uses the owner's inspection report and concise paraphrases, not a new independent retrieval. No full copyrighted texts, verbatim passages or confidential financial specifics are reproduced.

Historic proposals are not adopted 2026 rules, ByteShares bylaws, verified performance or deployment evidence. The Proposed Canon remains Draft / Not adopted / Non-operational. Source inspection status applies only to the two historical texts in this comparison; coverage and registry-wide verification are unchanged.

Edition, date and source-inspection trace

Actual Eng WhitePaper ver. 2.1

VPLedger White Paper v2.1 — July 2019; Google Doc, approximately 95,000 characters.

Source identifier: 1590DqZ6IWkObq15eeQsH_taqCsgk-bC6OX5rfAq9VVY

Original source directly inspected — as reported by the owner; not independently retrieved in this source/preview update.

Copyright header: © 2019 OpenLedger ApS. Copyright/title unresolved; no assignment of OpenLedger IP to the owner established. Technical proposals and historic performance claims are not current implementation evidence.

The Vision of VPLedger Memorandum 1.80_06112020 (2).pdf

Visible 15-page VPLedger Memorandum; internal content states 2019. Filename includes 06112020: discrepancy unresolved; neither date silently supersedes the other.

Source identifier: 18NuCpHXZJ1gjQojowB8Fr9jx23sC6KKk

Original source directly inspected — as reported by the owner; not independently retrieved in this source/preview update.

Copyright header: © 2019 Danish Blockchain Services ApS. Constitutional/governance vision is a historical proposal, not adopted ByteShares bylaws or protocol rules; copyright/title unresolved.

ByteShares Cooperative & AI City Infrastructure Master Business Plan v2.1 — July 2026

Final Canonical Edition / Institutional Use; limited owner-supplied chapter summaries only.

Source identifier: Private institutional source — no document identifier supplied for this comparison.

OWNER PROVIDED / UNVERIFIED summary; current strategic reference, not technical implementation proof.

No full institutional text, confidential financial specifics or commercial allocations disclosed. Source fidelity and authorized public-disclosure scope remain review gates.

Four-source comparison — retained principles and unresolved deltas

Each topic separates historic proposals, current strategic doctrine and proposed protocol candidates. “Retained” describes conceptual lineage, not normative adoption. Historic token/commercial assumptions and performance figures are excluded as current parameters; any claim of a completed technical replacement or formal supersession requires owner review.

Identity / eligibility

2019 technical Whitepaper
Verification/KYC and hierarchical dynamic account permissions form part of the historic protective/regulated blockchain proposal.
2019 Memorandum
User identification, legal-entity accountability and verified access to financial assets; KYC proposed for institutional interactions.
2026 masterplan
Verified person and active cooperative membership underpin cooperative voting. Uniqueness and eligibility require implementation/compliance evidence (Ch6.1–6.2; Ch27.4).
2026 Proposed Canon (draft)
Retained principle: identity is distinct from explicit scoped authority; delegation cannot amplify authority. Credential/issuer-trust/revocation mechanics remain unresolved (INV-001–003).

Voting / governance

2019 technical Whitepaper
Historic network voting and Veritas Persona by Governance (VPG) framing; not a statement of ByteShares cooperative constitutional voting.
2019 Memorandum
Protective democracy and non-oligarchic voting; proposed off-chain constitutional/legal governance through SHA and constitution, with member veto/referendum and rights.
2026 masterplan
One verified cooperative member = one vote; constitutional, board/executive and proposed protocol layers; PreDAO → Memo → Epoch and non-dominance (Ch6).
2026 Proposed Canon (draft)
Governance and execution remain distinct; cooperative governance is not automatically technical protocol governance. No merger of historic network voting and cooperative voting without a normative owner decision (INV-005, INV-020–024).

Validator / consensus

2019 technical Whitepaper
Historic VPG proposal: modified proof of authority based on Graphene 3.0, validator requirements and centralization discussion. Not adopted 2026 consensus.
2019 Memorandum
Contrasts PoW, PoS and DPoS within a political/governance vision. That comparison is not a current consensus specification.
2026 masterplan
Current strategic governance and network-neutrality reference; does not supply accepted consensus/finality or deployment evidence.
2026 Proposed Canon (draft)
Nodes execute accepted rules without privately redefining them; bounded operator authority and defined divergence handling required. Historic engine/consensus assumptions are not imported (INV-025–028).

Protections / exception paths

2019 technical Whitepaper
Historic user-protection and regulated-operation intent; hierarchical permissions, limits and scheduled-payment concepts do not establish current exception procedures.
2019 Memorandum
Protective democracy, legal accountability and proposed rights/veto/referendum paths. Not adopted dispute rules or remedies.
2026 masterplan
Exceptions, corrections, reversals and emergency/dispute action must have bounded, auditable named authority, escalation, timelines and remedies; specifics TBD (Ch6.8.1).
2026 Proposed Canon (draft)
Fail closed on missing authority/inputs; refusals are evidence; corrections are additive and reversals are not deletion. Exact exception/dispute procedure remains independently open (INV-006, INV-012–015, INV-021–023, INV-029).

Assets / payments / regulated rails

2019 technical Whitepaper
Historic token, smartcoin/stablecoin, fee-backed asset, fee/remuneration and payment models. Supply, fee and performance assumptions are historical only, not 2026 tokenomics or verified results.
2019 Memorandum
Verified access to financial assets and regulated institutional interaction proposed; no evidence of currently licensed or operating rails.
2026 masterplan
Regulated rails depend on partners/licensing; instrument categories require legal review. Economic participation is distinct from governance (Ch27.5–27.7). No confidential financial terms reproduced.
2026 Proposed Canon (draft)
Historic commercial/token parameters are excluded from adopted-rule claims; no accepted instrument parameters, live token, payment contract or settlement evidence. Unresolved design must not be presented as operational.

Evidence / audit

2019 technical Whitepaper
Data storage, identifiers, transaction/block model and permission/account concepts are historic technical discussion, not the current evidence schema or snapshot specification.
2019 Memorandum
Legal/constitutional accountability and network principles provide lineage, not a current evidence-format or anchoring specification.
2026 masterplan
Desired decision record, hash, ledger anchor, Filecoin snapshot reference and epoch closure proof; not claimed to be generated (Ch6.3–6.5).
2026 Proposed Canon (draft)
Evidence differs from commitments; explicit custody, minimization and historical-context verification are proposed. Snapshot construction/canonicalization and reference trust remain separate specifications (INV-015–019, INV-035).

Legal entities / IP

2019 technical Whitepaper
OpenLedger ApS copyright header is source metadata, not evidence of a completed assignment or present ownership by Ronny or ByteShares.
2019 Memorandum
Danish Blockchain Services ApS copyright header and legal-entity accountability require authorship/title reconciliation; no legal conclusion inferred.
2026 masterplan
Cooperative/ProductCo separation and staged founder-to-cooperative stewardship intent have contractual, succession and title dependencies (Ch7; Ch26). No transfer asserted to have occurred.
2026 Proposed Canon (draft)
Design lineage and provenance are retained as such, never exclusive ownership or complete chain of title. Current licensing, entity rights and legal/security conclusions need independent evidence.

Version-collation backlog — not read

  • VPLedger Memorandum Eng 1.8.docx — Drive ID 1Jv45xgSpOe-vZcspd0JO6IgsRkp3auDN; file exists, connector text extraction returned empty. NOT READ; collate against the PDF before any version-equivalence claim.
  • Technical WP for MVP ver. 1.0.docx — exists, NOT READ in this pass. Earlier dossier references remain indirect provenance, not direct inspection of this file.
  • Actual WhitePaper(2).docx — exists, NOT READ in this pass. No equivalence to the inspected Google Doc established.

Release and evidence gates — unresolved

  1. Version reconciliation: collate unread variants with the inspected editions; resolve memorandum filename/internal-date discrepancy through source evidence, not assumption.
  2. Authorship/IP chain of title: review copyright holders, assignments, contractor/collaboration records, licenses and entity succession; no OpenLedger assignment or completed stewardship transfer presumed.
  3. Historical-to-2026 delta analysis: owner-approved mapping of retained doctrine, excluded/superseded token/commercial/technical assumptions and unresolved normative decisions; do not conflate network consensus voting and cooperative constitutional voting.
  4. Owner-approved disclosure scope: approve the limited metadata/paraphrase comparison for any public release; source/preview preparation does not authorize publication or full-text reproduction.
  5. Security/legal review: independently assess actual implementation and applicable entity, compliance, licensing and dispute policies; original text inspection is not assessment.
  6. Actual code/test/operations evidence: accepted source, conformance tests, consensus/finality, deployment and accountable operational evidence before implementation, performance or network claims.

Review position and owner gates

The five manuscripts are complete as conceptual documentation review drafts. Material source-only integration now also includes a separate owner-extract masterplan summary. Further normative changes require owner decisions or evidence. Coverage is 45 Covered / 8 Partial / 0 Missing; verification and source/operational gates are unchanged.

Proposed Canon & Protocol Invariants v0.1 was prepared on 8 October 2026 for review traceability; it is a draft, not an approved standard. Next owner gate: adopt, amend or reject it. Review the proposed canon. Publication requires separate explicit approval.

The masterplan-derived supplement is separate from the unchanged proposed canon. Its private source is OWNER PROVIDED / UNVERIFIED: confirm fidelity and authorized public-summary scope, then adopt, amend or reject its derived candidates. No doctrine summary closes an independent technical/legal blocker or approves publication.

Release conditions — not performed

  1. Review each material conceptual claim against its linked documentation and retain source-status limits.
  2. Supply and review evidence before any stronger normative, legal, security or operational statement.
  3. Obtain Ronny's explicit approval for the named publication scope.
  4. Assign any paper citation details only through an approved release process; none is assigned here.

Open questions / evidence required

Proposed / Non-operational — review questions, not decisions or implementation contracts.

Which claims can the review drafts substantiate?
TBD / Requires source: Linked project documentation supports conceptual narrative only; each stronger claim needs the specifications, title/intake dispositions or independent evidence requested on its supporting page.
What must happen before a paper is released?
TBD / Requires source: Claim-traced documentation manuscripts now exist in source/preview; underlying source review and Ronny's explicit release approval remain required. No PDF, author, paper version, DOI or publication date is assigned.
Documentation-gap audit and evidence boundaries

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
A limited masterplan-derived canon review supplement exists in source/previewPrivate July 2026 institutional masterplan — OWNER PROVIDED / UNVERIFIED extractsSource claimed, not yet verifiedOnly owner-supplied doctrine summaries and chapter references are represented. Full source not independently inspected; authorized disclosure scope and normative owner acceptance pending. No registry verification upgrade.
Five claim-traced conceptual review manuscripts exist in source/previewOwner-directed titles and existing project documentationSource claimed, not yet verifiedNarrative, traces, boundaries, exact audit dependencies and review checklists are present. Underlying verification is unchanged; manuscript synthesis is not independent source acceptance. Site RC1 is not an individual paper version.
Any published, citable paper or downloadReleased documentNo source on fileNo paper released or download provided. No authorship, individual paper version or publication date assigned.