Readiness is not connection
Awaiting approvalGitHub readiness means the process is defined. It does not mean GitHub is connected.
Live technical information site. The planned DLT is not live; membership is on ByteShares.dk.
Operations
A specification for how source will be taken in, classified, versioned and published — written before any candidate repository is accepted, so the process can be audited rather than reconstructed afterwards. GitHub is Awaiting approval / Not connected for this project; no official ByteShares repository was verified through the connected account, and no repository has been created or imported, and no repository name here is final.
Not live
Source publication is not operating. Nothing on this page reports real activity, and no operational figures are shown, because no verified operational data source exists yet.
Awaiting GitHub connection. No repository URL, name or link is published. Anything elsewhere presenting itself as an official ByteShares repository is unverified as far as this platform is concerned.
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.
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.
Safe metadata only. These records support readiness work; they do not establish complete legal title, repository acceptance or production readiness.
The five root names and file counts below are bounded to the historical recovery report dated 17 September 2026. The estate-level 52,014-file / 54.27 GiB hash record and 10,024-record USB manifest are recorded integrity evidence, not a current repository scan or a claim that those records are the same accepted baseline. No new archive inspection occurred in this documentation pass.
The four October archive records support founder/originator chronology and concept lineage. Component-linked assignments, collaboration agreements and applicable transfer records are still needed for title review; no historical software ownership or licence is inferred.
GitHub readiness means the process is defined. It does not mean GitHub is connected.
A connected account does not mean any repository or its source has been accepted.
Accepted repositories do not mean infrastructure exists or runs.
ByteShares.org is already publicly available at https://byteshares.org. Source acceptance and future operational releases remain gated; they do not disable the existing documentation domain or indexing.
Twelve gates, each stated with the evidence its current state rests on. States are deliberately conservative: anything unproven is not started or blocked.
Every candidate source set is mapped and named.
Basis: The five core VPLedger roots and broader OpenLedger roots are inventoried; full canonical intake scope is not approved.
Manifests and hashes recorded where practical.
Basis: Estate-level evidence records 52,014 SHA-256 hashes without missing entries and a 10,024-record USB OpenLedger manifest; accepted repository baselines are not yet linked.
Class A/B/C/D/X assigned with evidence.
Basis: Core candidate roots remain class C while commit history, legal title, licensing and canonical intake are reviewed; nothing is class A or B.
No secrets, private keys or wallet dumps destined for Git.
Basis: Restricted wallet, key and credential-related categories are identified for index-only handling; quarantine and repository-level secrets scans remain pending.
Ownership and licence gaps explicitly recorded.
Basis: The IP Provenance Dossier, IP Concept Evolution Register, Chain-of-Title Matrix and 2026 IP Foundation Clean Title Record support founder/originator chronology and concept lineage. Historical contractor/collaboration assignments, transfers, complete legal title and licensing remain incomplete.
Each accepted source set has an approved target.
Basis: Mapping is proposed only; no approval recorded.
Build, dependency and test state recorded per source set.
Basis: No candidate DLT source build baseline has been verified; this does not refer to the documentation site build.
Versions assigned after source verification.
Basis: Blocked by G3; no version may be assigned before provenance.
Readme, security, contribution and provenance expectations defined.
Basis: Documentation RC1 expectations are specified and await owner review.
Explicit owner approval to connect GitHub.
Basis: Awaiting approval / Not connected. No official ByteShares repository verified through the connected account.
Imported contents match the accepted source sets.
Basis: Nothing connected, so nothing imported.
Accepted source or operational claims require evidence and explicit approval; this does not gate the already-public documentation site.
Basis: Future source/operational scope depends on G1 through G11, independent operational evidence and owner approval. Existing public domain and indexing are already recorded.
Proposed repository architecture — awaiting source and provenance acceptance.
Separation follows responsibility and provenance rather than a monorepo assumption, so a source set with unclear origin cannot contaminate verified material. Names are working labels, not final, and no URL is implied by any of them.
Canonical DLT and protocol implementation; where verified protocol source ultimately belongs.
Proposed; no source accepted
VPLedger core and ledger implementation.
Proposed; candidate source pending classification
Client and frontend application.
Proposed; candidate source pending classification
Backend and supporting services.
Proposed; candidate source pending classification
Regression, smoke and integration test assets.
Proposed; candidate source pending classification
Testnet and node configuration and infrastructure assets.
Proposed; candidate source pending classification
Protocol architecture, invariants, Sig-56, F.I.P., Web4 and governance technical specifications.
Proposed; documents not supplied
API, SDK and developer documentation and examples.
Proposed; content drafted only on this platform
Client libraries, if a distinct codebase exists.
Proposed; awaiting source verification
Explorer application, if a distinct codebase exists.
Proposed; awaiting source verification
Threat model, security policy and responsible disclosure. Never secrets.
Proposed; threat model incomplete
Index mapping legacy OpenLedger and VPLedger assets to eventual canonical destinations. Documentation, not necessarily a repository.
Proposed; index not compiled
| Class | Meaning | Consequence |
|---|---|---|
| A — Verified canonical | Bytes, history and provenance verified sufficiently for canonical intake. | Eligible for a canonical repository. |
| B — Verified with gaps | Source appears authentic and usable, but legal or history gaps remain. | Intake only with gaps recorded and owner acceptance. |
| C — Candidate | Technically relevant; identity, version or provenance not established. | Hold. No publication. |
| D — Archive / reference | Historical or supporting material, not suitable as active source. | Index only; never a build input. |
| X — Excluded sensitive | Secrets, private keys, credentials, wallet dumps, personal or confidential material. | Quarantined. Never enters Git; represented only by safe metadata. |
No material is currently classified A or B. Assigning a class requires evidence, not familiarity.
Every candidate source set is recorded against the same fields before any disposition is reached. Secret contents are never recorded — a sensitive file is represented by safe metadata only, and its contents are quarantined.
| Intake field | Current state for vpledger, vpledger_client_app, vpledger-backend, vpledger-tests and testnets |
|---|---|
| Source origin | Recorded in the recovery inventory as preserved estate roots |
| Original relative path | Recorded in the recovery inventory; not restated here |
| .git present and commit history | Not established — requires repository-level intake |
| Remote or origin evidence | Not established |
| Authors and committers | Not established |
| Earliest and latest verifiable commit | Not established |
| Licence file and copyright notices | Not established; no licence decided |
| Contributor and IP evidence | Owner declaration, four archive IP records and historical support; founder/chronology and concept lineage supported, contractor/collaboration assignments incomplete |
| Submodules and dependencies | Not established |
| Build and package manifests | Not established |
| Secrets scan status | Restricted categories identified; repository-level scan not performed |
| Binary, vendor and generated classification | Not established |
| SHA-256 reference | Estate-level hash evidence exists; per-root baseline linkage not established |
| Duplicate and archive comparison | Not established |
| Chain of title | Incomplete — historical title documentation missing in part |
| Reviewer and evidence reference | Not recorded |
| Acceptance disposition | Hold pending intake — no set has reached a disposition |
"Not established" means no evidence has been produced, not that evidence is absent from the estate. Nothing has been accessed, scanned or built for this platform.
Candidate source sets inventoried and preserved in the recovery report, presented pending canonical repository intake and provenance acceptance — not as imported repositories.
| Candidate source set | Inventory evidence | Proposed target | Class | Verification gaps | Disposition |
|---|---|---|---|---|---|
| vpledger | 499 files | vpledger-core | C — Candidate | Commit history, licence and legal title intake pending | Hold pending intake |
| vpledger_client_app | 164 files | vpledger-client | C — Candidate | Commit history, dependencies and repository-level secrets scan pending | Hold pending intake |
| vpledger-backend | 60 files | vpledger-backend | C — Candidate | Commit history, sensitive-content quarantine and build state pending | Hold pending intake |
| vpledger-tests | 112 files | vpledger-tests | C — Candidate | Commit history, test runnability and coverage pending | Hold pending intake |
| testnets | 125 files | network-testnets | C — Candidate | Commit history, configuration quarantine and repository-level secrets scan pending | Hold pending intake |
| Other legacy OpenLedger roots, including libevm and ol4 | Inventoried; count not stated here | archive / legacy mapping | C — Pending classification | Canonical scope, relevance, licensing and legal title pending | Archive-only unless accepted by evidence |
The order in which the five evidenced candidate roots will be worked, once repository-level intake is authorised. Nothing in this sequence has been started: no source has been accessed, scanned, built or classified beyond the existing inventory evidence.
| Candidate root | Inventory evidence | Proposed target |
|---|---|---|
| vpledger | 499 files | vpledger-core |
| vpledger_client_app | 164 files | vpledger-client |
| vpledger-backend | 60 files | vpledger-backend |
| vpledger-tests | 112 files | vpledger-tests |
| testnets | 125 files | network-testnets |
Restricted wallet, key, credential and personal categories are separated as class X before anything else is touched. Contents are never transcribed; only safe metadata is recorded.
Each candidate root is scanned in place for credentials and key material. Findings are quarantined, not fixed in passing.
Presence of .git, readable commit history, remote or origin evidence, author and committer records, and earliest and latest verifiable commit.
Package manifests, lockfiles, submodules, vendored and generated material, third-party licences and copyright notices.
Whether the set builds, what it needs, and whether tests pass, fail, are not runnable or were not verified. Failures are recorded, not hidden.
The candidate root is linked to the preserved estate hash evidence so the accepted bytes are identifiable later.
A, B, C, D or X assigned against recorded evidence. Candidates stay class C until evidence justifies otherwise.
The classified set is mapped to a proposed repository, with the mapping itself still requiring owner approval.
A repository acceptance record is completed and reviewed. Acceptance means honestly described and safe to publish — never production-ready.
Sensitive material is handled first and never leaves quarantine. A step is only recorded as done when its evidence exists.
One record per source set, completed during authorised intake. Sensitive content is recorded as metadata only or excluded as class X — never credentials, keys, wallet dumps or secrets. No record has been completed.
| Field | Guidance | Value |
|---|---|---|
| Source set | Root name as inventoried, e.g. vpledger. | Not yet recorded |
| Origin | Where the preserved copy came from; no personal data. | Not yet recorded |
| Relative path | Path within the preserved estate. | Not yet recorded |
| .git / history state | Present, partial or absent. | Not yet recorded |
| Commit evidence | Earliest and latest verifiable commit reference. | Not yet recorded |
| Remote / origin evidence | Recorded remote, stated as metadata; never published as a link. | Not yet recorded |
| Contributors | Count and role categories; names only if already on the legal record. | Not yet recorded |
| Licence / copyright | As found in the source. Never fabricated. | Not yet recorded |
| IP / assignment evidence | Reference to assignment documents, or stated as missing. | Not yet recorded |
| Dependencies / submodules | Manifest reference and third-party licence summary. | Not yet recorded |
| Build manifests | Lockfiles and build files present. | Not yet recorded |
| Secrets-scan state | Not run / run with findings / clean. Findings as category only. | Not yet recorded |
| Binary / vendor classification | Own code, vendored, generated or binary. | Not yet recorded |
| SHA-256 evidence | Reference to estate hash record; per-repository linkage. | Not yet recorded |
| Duplicate / archive comparison | Relationship to other copies; candidate for class D. | Not yet recorded |
| Chain-of-title state | Complete, gaps documented, or unresolved. | Not yet recorded |
| Reviewer / evidence date | Reviewer role and date of review. | Not yet recorded |
| Target repository | Proposed canonical target; never an existing URL. | Not yet recorded |
| Disposition | A / B / C / D / X class and acceptance disposition. | Not yet recorded |
The record feeds the gates: intake fields close G1–G5, target and version baseline close G6–G8, and a completed, owner-approved record is the evidence for G11. Acceptance is not production readiness — operation still needs implementation and operational verification.
One record per candidate source set, held in this preview only. Values shown are the current honest state — the template is not pre-filled with assumptions, and no set has reached a disposition.
| Field | Current state |
|---|---|
| Candidate source set | Not yet recorded — one record per accepted set |
| Accepted scope | Not yet recorded |
| Provenance class | C — Candidate (no set has been reclassified) |
| Source and hash references | Preserved estate hash evidence exists; per-repository linkage not yet recorded |
| Commit baseline | Not yet recorded |
| Build and test state | Not yet recorded |
| Licence and IP status | Licence undecided; chain of title incomplete |
| Excluded sensitive paths | Safe metadata only — category and handling decision, never contents or locations that reveal secrets |
| Target repository | Proposed only; mapping not approved |
| Version baseline | Not yet assigned |
| Reviewer | Not yet recorded |
| Owner approval | Not recorded |
| Acceptance disposition | Accepted / Accepted with gaps / Hold / Rejected / Archive only — none reached |
| Date | Not yet recorded |
Excluded sensitive paths are represented by safe metadata only — category and handling decision. Contents, credentials, keys and wallet data are never recorded here.
Specifications carry an explicit specification version and a status of Draft, Review or Approved. They never borrow software release numbers to look more finished than they are.
| Component | Versioning basis | Version | Status | Compatible spec version |
|---|---|---|---|---|
| protocol-core | SemVer, prospective only | Not yet assigned | Not yet assigned | Not yet assigned |
| VPLedger | SemVer, prospective only | Not yet assigned | Not yet assigned | Not yet assigned |
| API / SDK | SemVer, prospective only | Not yet assigned | Not yet assigned | Not yet assigned |
| Explorer | SemVer, prospective only | Not yet assigned | Not yet assigned | Not yet assigned |
| Specifications | Specification version plus Draft / Review / Approved status | Not yet assigned | Not yet assigned | Not applicable |
Architecture pages on this platform expose version, maturity, source and verification, and last reviewed, using "not yet assigned" wherever a value is unknown.
Proposed governance. These are not currently active GitHub settings, because there is no GitHub connection to configure.
| File or artefact | Expectation |
|---|---|
| README.md | What the repository is, what it is not, and its maturity — matching the labels used here. |
| LICENSE | A licence, or an explicit "Awaiting approval / verification" status. No placeholder licence is ever added. |
| SECURITY.md | Responsible disclosure route and response expectation. |
| CONTRIBUTING.md | Contribution terms, review expectations and attribution. |
| CHANGELOG.md | Required for releasable components. |
| CODEOWNERS | Where ownership review applies. |
| Architecture and docs link | Pointer to the corresponding ByteShares.org documentation. |
| Build and test instructions | How to build and test, including known failures. |
| Dependency manifest and lockfile | Reproducible dependency state. |
| .gitignore | Excludes build output and anything sensitive. |
| Environment example | Variable names only. No secret values, ever. |
| Provenance note | Source set, class and evidence reference. |
| Maturity note | Current maturity, consistent with this platform. |
Proposed / Non-operational — review record structure only; no repository URL is assigned or activated.
| Record element | Review requirement | Current boundary |
|---|---|---|
| Source identity | Record source-set reference, accepted scope, class, branch/commit and reviewer evidence. | The five roots remain class C and on hold; no accepted branch/commit exists here. |
| Documentation intent | Map each accepted responsibility to its existing architecture/developer page and compare maturity labels. | Candidate targets are listed above; a conceptual page must not imply the mapped implementation is live. |
| Link and reverse reference | Once authorized source exists, check the repository pointer to the intended ByteShares.org page and any approved reverse link against the same source scope. | No external repository URL, published link or validation result is invented. |
| Version and evidence boundary | Keep source/specification version, documentation review date, and implementation/operational evidence distinct. | 0.9 RC1 describes documentation only; owner approval and actual accepted-baseline checks remain pending. |
A repository counts as accepted only when all of the following hold.
Acceptance does not mean production-ready. It means the repository is honestly described and safe to publish.
Credentials, private keys, wallet dumps and personal or confidential material are class X: quarantined, excluded from anything destined for Git, and never reproduced in documentation. Where their existence must be recorded, only safe metadata is kept — location reference, type and handling decision, never contents.
Proposed / Non-operational — review questions, not decisions or implementation contracts.
Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.
| Claim | Source type | Verification | Note |
|---|---|---|---|
| Repository architecture, intake checklist, gates and policies | Owner instruction | Verified source on file | Specified directly by the project owner in this preview; names and policies remain proposals. |
| Core VPLedger candidate roots are inventoried and preserved | VPLedger_E_Drive_Recovery_Report_2026-09-17.xlsx | Verified source on file | The report records the five named core roots and file counts. Canonical repository intake and acceptance remain pending. |
| Preserved source and archive estate has integrity evidence | Project portfolio hash and manifest records | Verified source on file | 52,014 files / 54.27 GiB were SHA-256 hashed without missing entries; the USB OpenLedger manifest contains 10,024 records. Repository-level accepted-baseline linkage remains pending. |
| VPLedger ownership and sole complete-code custody | Owner declaration in Boesing_Corporation_IP_Ownership_Schedule_2026.docx | Source claimed, not yet verified | Owner-declared evidence for readiness review; it is not independent proof of complete legal title. |
| Founder/origin and OpenLedger project-rights history | Historical documentary support summarized in the IP ownership schedule | Verified source on file | Supports originator status and records project ownership, contractual SaaS rights and an external contractor; scope and legal effect require title review. |
| Complete legal chain of title for every historical component | Chain-of-Title Matrix and 2026 IP Foundation Clean Title Record; assignments and transfers still incomplete | Source claimed, not yet verified | Archive provenance and concept lineage are documented, but historical contractor/collaboration gaps remain. Neither possession nor the record titles establish exclusive ownership of every historical software component. |
| Restricted and sensitive categories identified | Recovery inventory restricted-category index | Verified source on file | Safe category metadata exists. Secret contents are not shown; quarantine and repository-level secrets scans remain incomplete. |
| Repository names, URLs, imports or connections | GitHub | No source on file | Awaiting approval / Not connected for this project. No official ByteShares repository verified through the connected account; no repository created, imported or linked. |