Skip to content

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

ByteShares.org

Operations

Readiness & Acceptance

Documented architecture

An interim documentation workspace, not a blockchain launch dashboard. Counts come from the coverage register and readiness gates; nothing here authorises connection, publication or release.

Source / verification
Owner RC1 canon and existing public-site/source records; no new archive source inspected
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.

Private masterplan — documentation provenance only

OWNER PROVIDED / UNVERIFIED

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

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

Review the limited masterplan-derived draft and owner decisions

Current documentation position

Documentation state
Documentation release candidate — October 2026
Publication state
Live public production site on https://byteshares.org. Public pages are indexable; robots.txt allows crawling and lists the sitemap.
ByteShares.org
Technology, architecture and documentation. No accounts, payments or member data.
ByteShares.dk
Live cooperative membership, governance participation, login and payment. Not represented here.
GitHub
Awaiting approval / Not connected. No official ByteShares repository verified through the connected account; no repository created or imported.
Domain
Publicly available at https://byteshares.org; no new domain or DNS action in this pass.
Operational infrastructure
None verified. No node, ledger, endpoint, package or service is presented as running.
Documentation coverage
53 models tracked — 45 covered, 8 partial, 0 missing

Documentation now ready for review

Five Technical Papers review manuscripts now contain executive abstracts, purpose and scope, substantive conceptual narrative, claim-to-documentation traces, explicit boundaries, exact evidence requests and individual review checklists. Full documentation drafts exist in preview; they are not released papers, normative specifications or verified implementation evidence.

Developer guidance now documents proposed identity, authority, mandate, evidence and governance relationships, illustrative request/response shapes and offline-verification intent. Every example remains Proposed / Non-operational, with schema and verification gaps explicit.

All 19 previously Partial rows have an explicit audit rationale. Eleven documentation-only scopes are Covered (ten from the 7 October audit plus the architecture-invariants row after Proposed Canon v0.1 on 8 October); eight remain Partial with exact source/specification or owner-decision requests. All source-verification categories and readiness-gate states remain unchanged. Finalized SDK contracts, legal title, repository acceptance, independent security evidence, DLT implementation and network operation remain open or blocked.

Source-only integration includes a separate masterplan-derived review supplement using owner-provided extracts only. Its fidelity and public-disclosure scope are unverified; adoption and the exact normative decisions remain pending. Further expansion requires new evidence or an owner decision. Publication of these preview changes separately requires Ronny's explicit approval.

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

Documentation consistency · 7 October 2026

PASS means the recorded documentation state meets the requirement; FIXED means reconciled in the current source. OPEN needs evidence or confirmation, not a claim of launch readiness.

  • Site purpose and page structureFIXED

    Overview now leads with the interim technical-information role; deeper technical and control pages remain available.

  • Membership separationFIXED

    ByteShares.dk is identified as the live cooperative site and the only active production cross-link.

  • Ecosystem rolesFIXED

    eIDspot, VPLedger, planned DLT and AI City have distinct explanations and maturity states.

  • Premature operational claimsFIXED

    Planned services retain non-live labels; eDEV maturity and AI City wording were aligned to the interim canon.

  • Language parityPASS

    The existing site has English content only; no Danish counterpart exists to diverge. Danish translation remains a future content decision.

  • Public indexing and private-route exclusionsPASS

    Public pages are indexable with absolute https://byteshares.org canonicals, robots allow and sitemap served. Private conversation threads remain noindex; source and operational approvals stay separate.

  • Source and legal provenanceOPEN

    Candidate roots are inventoried but class C; repository-level intake, licence and complete chain of title remain unresolved.

  • DLT implementation and operationOPEN

    No accepted protocol build, independently verified network, explorer, API or wallet evidence is on file.

  • Unconfirmed ecosystem domainsOPEN

    The four owner-specified domains appear in the shared navigation; operational launch states are not inferred from directory links.

Public documentation and RC1 matrix · October 2026

Records the already-public documentation site and the separate RC1 acceptance state. It does not approve a new deployment or any blockchain claim.

  • Interim role and IAPASS

    Overview, banner and footer state the technical-information role; no signup, login, payment or wallet surface exists.

  • ByteShares.dk vs ByteShares.orgPASS

    The cooperative and technical-information roles remain distinct; the shared ecosystem directory identifies all four destinations without claiming technical operations.

  • Ecosystem rolesPASS

    eIDspot identity/access, VPLedger proof/evidence/audit, DLT planned, AI City planned long-term product family with white-label modules.

  • Maturity labels on unverified areasPASS

    Explorer, Network Status, Developers/API/SDK, Node and GitHub remain labelled placeholders with no fabricated data.

  • Boesing.dk / Boesing.io linksFIXED

    Owner-requested navigation links are visible in the shared footer; operational endorsements remain gated separately.

  • Sitemap, canonical and robots gatingFIXED

    The existing release-flag module enables public robots meta, absolute canonical/og:url and /sitemap.xml at https://byteshares.org. robots.txt allows crawling and lists the sitemap; private threads remain excluded.

  • Ecosystem link gatingFIXED

    The four-domain footer is navigational; operational endorsements in page copy remain separately gated.

  • Accessibility and responsive QAPASS

    Skip link, landmarks, focus styles, labelled nav; checked at 390, 430, 768 and 1280px without overflow.

  • Public indexingPASS

    Site is live: index, follow, canonical https://byteshares.org URLs, robots allow and sitemap served; private conversation threads stay noindex.

  • Documentation RC1 acceptanceOWNER ACTION

    Evidence and owner-approval gates in progress for 0.9 RC1; the documentation site is already public. RC1 is not a DLT/software/network release.

  • Production domain namePASS

    https://byteshares.org is the owner-confirmed public canonical origin. No new domain action in this pass.

  • Boesing.dk / Boesing.io live stateEXTERNAL BLOCKER

    Confirm upstream launches before making operational claims; the footer directory alone makes no such claim.

  • DNS and domain connectionPASS

    The public documentation site is already available at its confirmed origin. DNS is not re-inspected or changed by this source/preview correction.

  • Future blockchain claimsEXTERNAL BLOCKER

    Interim launch does not waive source/rights, specification/security, implementation or network-verification gates.

Public-site preservation and RC1 checklist

The public site is already launched. This checklist records existing SEO behavior and future review boundaries; it does not execute a new cutover.

  1. Record existing public documentation availability at https://byteshares.org; no new launch gate.
  2. Keep release flags, absolute public canonical/og:url, robots allow and sitemap enabled.
  3. Keep browser-local conversation threads noindex and out of the sitemap.
  4. Review documentation RC1 evidence and obtain owner acceptance of the named documentation scope.
  5. Validate local preview links, metadata, not-found behavior, accessibility and mobile/desktop layout.
  6. Confirm operational launch states before service-availability claims; the four-domain directory is navigational only.
  7. Keep blockchain, nodes, wallets, tokens, DLT API/SDK and payment claims non-operational unless independently verified.
  8. No deployment, DNS/domain, GitHub, infrastructure or outbound communication action without explicit new approval.

Operational endorsements in page copy: ByteShares.dk (active) · Boesing.dk (not enabled) · Boesing.io (not enabled). The separate four-domain footer is navigational only.

Future blockchain-launch gates

These are future evidence thresholds, not a schedule or an approval to activate blockchain, wallets, tokens, payments or a public domain. The October documentation RC1 does not pass these gates.

  1. 01 · Source and rights

    Evidence required: Accepted repository-level provenance, sensitive-material exclusion, licence and complete publishable rights.

    Open · not accepted

  2. 02 · Specifications and security

    Evidence required: Reviewed protocol, identity, proof and governance specifications; threat model and independent security evidence.

    Open · not accepted

  3. 03 · Implementation

    Evidence required: Accepted builds, tests, versions, reproducible release artefacts and compatibility evidence; no documentation-only promotion.

    Open · not accepted

  4. 04 · Network operation

    Evidence required: Independently checked nodes, ledger state, explorer/API behaviour, data handling and incident/status sources.

    Open · not accepted

  5. 05 · Owner release decision

    Evidence required: Ronny explicitly approves a named scope after prior gates, repository acceptance and platform review; any new activation needs separate explicit approval. The existing documentation domain and indexing are not gated by this future release.

    Open · not accepted

Dependency chain for future source and operational acceptance

Each link must complete before the next begins, so no step can be assumed from the one before it. Links are also marked by the kind of readiness they establish: documentation readiness means the process and evidence are recorded, operational readiness means something actually exists, builds, imports or runs. Documentation readiness never implies operational readiness.

  1. Link 01G1

    Source inventory

    Every candidate source set located, named and scoped, with the canonical intake scope approved.

    Documentation readiness

  2. Link 02G2, G4

    Integrity and secrets

    Hashes and manifests linked to accepted baselines; sensitive material quarantined and repository-level scans complete.

    Documentation readiness

  3. Link 03G3, G5

    Provenance, IP and licence

    Class A/B/C/D/X assigned against evidence; ownership, chain-of-title gaps and the licence explicitly recorded.

    Documentation readiness

  4. Link 04G6

    Canonical repository mapping

    Each accepted source set has an owner-approved destination repository.

    Documentation readiness

  5. Link 05G7, G8

    Version, build and test baseline

    Build and dependency state recorded, tests classified, version baseline assigned only after provenance.

    Operational readiness

  6. Link 06G10

    Owner approves GitHub connection

    Explicit recorded approval. Nothing is connected before this point.

    Operational readiness

  7. Link 07G11

    Repository import verification

    Imported contents compared against the accepted source sets and their hash baselines.

    Operational readiness

  8. Link 08G11

    Site link validation

    Every repository reference on this platform resolves to an accepted repository; no placeholder link is published.

    Operational readiness

  9. Link 09G12

    Platform acceptance

    Release-evidence checklist reviewed, wording sweep, accessibility and mobile checks recorded as passed.

    Operational readiness

  10. Link 10G12

    Owner accepts future source and operational claims

    A named scope must be explicitly approved on supporting evidence. The public documentation domain, indexing and sitemap are already active and independent of this chain.

    Operational readiness

Gate states today: 1 ready for review, 4 in progress, 3 blocked, 4 not started, 0 approved.

  • G1Inventory completeIn progress
  • G2Integrity capturedIn progress
  • G3Provenance classifiedIn progress
  • G4Sensitive material separatedIn progress
  • G5IP and licensing reviewedBlocked
  • G6Canonical repo mapping approvedNot started
  • G7Build baseline documentedNot started
  • G8Version baseline assignedBlocked
  • G9Documentation baseline presentReady for review
  • G10GitHub connection approvedNot started
  • G11Repository import verifiedNot started
  • G12Future source and operational release acceptanceBlocked
Gate criteria and evidence basis

Source and provenance summary

Core VPLedger candidate roots are inventoried and preserved, and the wider estate has hash and manifest evidence. Canonical repository intake, legal-title and licensing review remain incomplete. Every candidate remains class C, and nothing is eligible for publication.

Source inventory
Five core VPLedger roots evidenced; full canonical intake scope pending
Integrity evidence
52,014 estate hashes and a 10,024-record USB OpenLedger manifest; repository baseline linkage pending
Sensitive handling
Restricted categories identified; quarantine and repository-level scans pending
Ownership and licensing
Four archive IP records support founder/chronology and concept lineage; historical contractor/collaboration title and licence gaps remain
Provenance classes assigned
All candidates class C
VPLedger provenance audit
Open

Documented provenance and concept lineage

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

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

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

Verification summary

Counted directly from the register. Documentation coverage and source verification are tracked separately, and coverage never implies a source was inspected.

Verified
4
Owner-asserted
25
Unverified
11
No source
13
Full coverage register

Documentation RC1 completion path · October 2026

States, not percentages. Each item names what it depends on. Release controls are tracked separately on Release Control.

A · Documentation work we can finish now6 items · No source access or decision needed.
B · Evidence and source verification7 items · Needs authorised intake or supplied documents.
C · Post-GitHub acceptance3 items · Only after connection is approved.
D · Owner decisions4 items · Only Ronny can close these.
E · Public-site records and future approved actions3 items · Existing launch is recorded; no new actions in this pass.

Acceptance evidence model

Five independent evidence levels. Documentation complete never implies source, implementation or operational verification, and no area is owner accepted.

Evidence level reached per technical area
AreaDocumentation completeSource verifiedImplementation verifiedOperationally verifiedOwner acceptedNote
Protocol ArchitectureYesPartialNoNoNoCanon owner-asserted; document not supplied.
Identity / eIDspotYesPartialNoNoNoCredential and revocation formats to be specified.
VPLedgerYesPartialNoNoNoArchive founder/chronology and concept-lineage evidence recorded; historical title and repository provenance remain incomplete.
GovernanceYesPartialNoNoNoGovernance paper pending.
Node ArchitectureYesNoNoNoNoTopology draft not supplied; no node exists.
ExplorerPartialNoNoNoNoPlanned; no ledger to index.
APIYesNoNoNoNoConceptual surfaces, relationships and illustrative shapes documented; no finalized contract, endpoints or implementation evidence.
SDKPartialNoNoNoNoOffline-verification intent and limits documented; no package, language, verifier or test vectors.
Standards / Sig-56, Web4, F.I.P.PartialNoN/AN/ANoSpecifications not supplied; nothing completed.
SecurityPartialNoNoNoNoThreat model incomplete; no audit.
Network StatusPartialNoNoNoNoNo network is running.
GitHub / sourceYesPartialNoN/ANoInventory and integrity evidenced; all candidates class C.

Documentation RC1 completion board

Every item is derived from current evidence and approval records. No percentage, estimate or forecast is given, because none is evidenced. An item moves only when the stated evidence exists.

Documentation complete5 items

  • Protocol system flow, asset function register and architecture principles

    Protocol ArchitectureGate —

    Evidence needed: None to progress documentation; canon document would raise verification only.

  • Governance authority domains and technical flow

    Governance LayerGate —

    Evidence needed: Governance architecture document to move from owner-asserted to verified.

  • Glossary, page meta fields and terminology consistency

    GlossaryGate —

    Evidence needed: Specification documents to confirm contested definitions.

  • Repository architecture, intake checklist, gates, versioning and change control

    Source & RepositoriesGate G9

    Evidence needed: Owner review of the documentation baseline.

  • Existing public indexing, canonical origin and sitemap records

    Public-site recordsGate Existing public site

    Evidence needed: Keep existing public indexing and private-thread exclusions; no new activation required.

Verification pending6 items

  • VPLedger proof, snapshot and storage models

    VPLedgerGate G3

    Evidence needed: Provenance audit outcome; proof and snapshot schemas.

  • Identity credential and revocation lifecycle

    Identity LayerGate —

    Evidence needed: Credential schema and revocation specification.

  • Node topology and staged deployment context

    Node ArchitectureGate —

    Evidence needed: Topology draft; confirmed site and host.

  • Sig-56 and F.I.P. specification structures

    StandardsGate —

    Evidence needed: The specification documents themselves.

  • Security threat model and disclosure route

    SecurityGate —

    Evidence needed: Threat model document; a decided disclosure contact.

  • Repository-level integrity linkage for the five candidate roots

    Source intake sequenceGate G2

    Evidence needed: Authorisation to begin repository-level intake, then hash-baseline linkage.

Owner decision required6 items

  • Canon documents supplied, or owner-asserted labels accepted as final for now

    Coverage RegistryGate —

    Evidence needed: Owner instruction.

  • Authorisation to begin repository-level intake, quarantine and scanning

    Gates G2–G4Gate G2–G4

    Evidence needed: Recorded owner authorisation. Inventory evidence already exists; access to work on it does not.

  • Licence and acceptable chain-of-title gaps for publication

    Gate G5Gate G5

    Evidence needed: Owner decision plus contractor-assignment and transfer evidence where obtainable.

  • Approval of the proposed canonical repository mapping

    Gate G6Gate G6

    Evidence needed: Recorded owner approval of names and targets.

  • Whether any surface may be promoted above documented architecture

    Acceptance matrixGate —

    Evidence needed: Owner instruction with the evidence relied on.

  • Technical paper releases

    Technical PapersGate Paper approval, not DLT launch

    Evidence needed: Claim-traced review manuscripts are present in source/preview; underlying source checks and explicit owner publication approval remain required, with no release inferred.

Post-GitHub acceptance4 items

  • GitHub connection approval and repository import verification

    Gates G10–G11Gate G10–G11

    Evidence needed: Owner approval; import comparison against accepted sources.

  • Build, test and version baselines per accepted source set

    Gates G7–G8Gate G7–G8

    Evidence needed: Build and test runs recorded after intake; versions only after provenance.

  • Repository acceptance records completed per source set

    Acceptance record templateGate G11

    Evidence needed: One completed record per accepted source set.

  • Documentation-to-repository link validation across this platform

    Coverage RegistryGate G11

    Evidence needed: Every reference resolving to an accepted repository.

Launch-gated2 items

  • Explorer and Network Status operational content

    DLT ExplorerGate G12

    Evidence needed: Running infrastructure and a verified telemetry source.

  • Operational API/SDK surfaces, executable examples and versioned contracts (conceptual shapes are already drafted)

    DevelopersGate G12

    Evidence needed: An implemented contract and an accepted SDK repository.

Release-evidence checklist for core surfaces

Values are derived conservatively from the Coverage Registry and the evidence recorded on each page. The disposition states how far a surface can currently be taken — no operational surface is marked accepted, and nothing here records acceptance.

Protocol Architecture

Ready for documentation review

Documentation coverage
Covered; Proposed Canon v0.1 supplies the documentation-level invariant scope
Verification
Owner-asserted
Operational state
Not operational
Release blocker
Proposed Canon v0.1 awaits owner adoption; implementation and conformance evidence absent
Evidence required
Owner canon decision, then conformance vectors and assessed implementation evidence

Identity / eIDspot

Verification pending

Documentation coverage
Covered, credential lifecycle partial
Verification
Owner-asserted
Operational state
Not operational
Release blocker
Credential and revocation formats unspecified
Evidence required
Credential schema and revocation specification

VPLedger

Verification pending

Documentation coverage
Covered conceptual custody boundaries; snapshot specification partial
Verification
Archive provenance recorded; implementation unverified
Operational state
Not operational
Release blocker
Founder/chronology lineage documented; repository provenance and historical title review open
Evidence required
Provenance audit outcome; proof and snapshot schemas

Governance Layer

Ready for documentation review

Documentation coverage
Covered, exceptions partial
Verification
Owner-asserted
Operational state
Not operational
Release blocker
Exception, reversal and dispute procedures undefined
Evidence required
Governance architecture document

Node Architecture

Verification pending

Documentation coverage
Covered, roadmap partial
Verification
Unverified
Operational state
No node exists
Release blocker
Topology draft not supplied; no site verified
Evidence required
Topology draft; site and host confirmation

DLT Explorer

Launch-gated

Documentation coverage
Covered as intent
Verification
Unverified
Operational state
Not operational
Release blocker
No ledger to index
Evidence required
Running ledger and indexing design

Developers / API / SDK

Ready for documentation review

Documentation coverage
Conceptual surfaces, shapes, SDK responsibilities and policy boundaries covered; finalized contracts absent
Verification
No source
Operational state
No endpoint or package
Release blocker
No finalized API contract, SDK codebase, offline verifier or test vectors
Evidence required
API contract; SDK repository acceptance

Standards / Sig-56 / Web4 / F.I.P.

Blocked by evidence

Documentation coverage
Partial — Sig-56 and F.I.P. normative specifications unsupplied
Verification
Owner-asserted
Operational state
Not adopted anywhere
Release blocker
Specifications not supplied
Evidence required
Sig-56 and F.I.P. specification documents

Technical Papers

Ready for documentation review

Documentation coverage
Five full conceptual review manuscripts: narrative, claim traces, boundaries and evidence-linked review checklists
Verification
Unverified
Operational state
No document released
Release blocker
Manuscripts exist in source/preview; underlying specifications, claim verification and owner release approval remain pending
Evidence required
Source review against linked documentation and exact audit blockers, then explicit owner release approval

Security

Blocked by evidence

Documentation coverage
Conceptual threat map covered; disclosure process partial; no completed assessment
Verification
Unverified
Operational state
No control implemented
Release blocker
System/asset classification, attack analysis and residual-risk review absent; no staffed disclosure recipient or response rules
Evidence required
Scoped threat assessment and independent implementation evidence; owner disclosure recipient/process decision

Network Status

Launch-gated

Documentation coverage
Covered as model
Verification
Unverified
Operational state
No network
Release blocker
No telemetry source exists
Evidence required
Running infrastructure and status source

Source / GitHub

Blocked by evidence

Documentation coverage
Covered as specification
Verification
Estate evidence available; repository acceptance pending
Operational state
Not connected
Release blocker
Source/operational gates G1–G12 remain unresolved; historical legal title and licensing incomplete
Evidence required
Repository-level intake links to inventory, hashes, history, title and licence evidence; owner approvals

Glossary

Ready for documentation review

Documentation coverage
Covered
Verification
Owner-asserted
Operational state
Not applicable
Release blocker
Terms follow whichever specifications are supplied
Evidence required
Specification documents to confirm definitions

Future source and operational release runbook

Documentation only. The public information site is already available. This sequence applies to a future accepted source or operational scope, not its domain or indexing. Nothing here authorises execution now.

  1. 01

    Source inventory accepted

    G1

    Every candidate source set located, named and scoped; nothing relevant left unaccounted for.

  2. 02

    Integrity, provenance, secrets, IP and licensing gates cleared

    G2–G5

    Hashes or manifests captured, classes assigned with evidence, sensitive material quarantined, ownership and licence recorded.

  3. 03

    Canonical repository mapping approved

    G6

    Each accepted source set has an approved destination; names confirmed by the owner.

  4. 04

    Build, version and documentation baseline

    G7–G9

    Build and test state recorded, version baseline assigned only after provenance, minimum repository documents drafted.

  5. 05

    Owner approves GitHub connection

    G10

    Explicit, recorded approval. Nothing is connected before this point.

  6. 06

    Import verification

    G11

    Imported repository contents compared against the accepted source sets and hashes.

  7. 07

    Documentation and repository link validation

    G11

    Every repository reference on this platform resolves and matches an accepted repository.

  8. 08

    Full platform acceptance

    G12

    Acceptance matrix reviewed, wording sweep complete, accessibility and mobile checks passed.

  9. 09

    Owner accepts the next named source or operational scope

    G12

    Explicit approval supported by title, licence and implementation evidence; documentation RC1 is not a software release.

  10. 10

    Preserve existing public-site SEO

    Existing public site

    Public documentation already uses absolute canonicals, robots allow and a sitemap. Private threads remain noindex. No new deployment or domain action.

Source-intake worksheet

A blank documentation template. It mirrors the twenty-one provenance fields and adds classification, target, disposition, reviewer and approval. No real source value is recorded, and no field is pre-filled with an assumption.

Worksheet fields — one sheet per candidate source set26 fields
  1. 01Source origin — physical or logical location
  2. 02Original relative path
  3. 03Repository history present (.git) — yes or no
  4. 04Commit history available and readable
  5. 05Remote or origin evidence, where present
  6. 06Author and committer history
  7. 07Earliest and latest verifiable commit
  8. 08Licence file and licensing basis
  9. 09Copyright notices
  10. 10Contributor and developer identity evidence
  11. 11Corporate or project ownership evidence
  12. 12Contractor or IP-assignment evidence, where applicable
  13. 13Submodules and external dependencies
  14. 14Build and package manifests
  15. 15Secrets and credentials scan status
  16. 16Generated, vendor or binary classification
  17. 17SHA-256 or source snapshot reference, where available
  18. 18Comparison status against duplicate or archive copies
  19. 19Chain-of-title status
  20. 20Reviewer, date and evidence reference
  21. 21Acceptance disposition — Accepted / Accepted with gaps / Hold / Rejected / Archive only
  22. 22Provenance class — A / B / C / D / X
  23. 23Proposed repository target
  24. 24Disposition rationale
  25. 25Reviewer name and review date
  26. 26Owner approval — recorded or not recorded

Every sheet is completed as: value, evidence reference, reviewer, date. A field without evidence is recorded as not established — never inferred.

Sensitive material is never transcribed into a sheet. Credentials, private keys and wallet dumps are represented only by safe metadata and quarantined as class X.

Existing public SEO and documentation QA checklist

Public pages are already intended to be indexed at https://byteshares.org. Canonical URLs, robots and sitemap remain enabled; private conversations retain their intentional exclusions. No settings are changed in this pass.

Absolute canonical URLs

Public pages emit self-referencing https://byteshares.org canonicals and og:url; private conversation threads omit them.

Live public configuration

Sitemap

The /sitemap.xml route serves public navigation pages and privacy; private conversation threads are excluded.

Live public configuration

Robots

robots.txt allows crawling and lists the sitemap; public pages emit index, follow.

Live

OpenGraph and Twitter metadata

Title, description, type and card are set per page; no image is claimed.

Present on public pages

Structured data

No structured data is emitted. Whether to add it is an owner decision, not a default.

Decision outstanding

Internal link validation

Every navigation and cross-page link resolves to an existing route.

Recheck on documentation changes

404 behaviour

Unknown paths must return a clear not-found page with no invented content.

Recheck on documentation changes

Mobile 390px

Wide tables collapse to cards or scroll accessibly at 390px.

Validation required for this correction

Keyboard and accessibility

Skip link, semantic headings, table captions and visible focus.

Recheck on documentation changes

Maturity labels

A maturity badge sits beside every claim that could be mistaken for live infrastructure.

Recheck on documentation changes

Final wording sweep

No sentence may read as operational, adopted, audited or released without verified evidence.

Recheck on documentation changes

Decisions that require the owner

Only decisions that genuinely need the owner are listed. Items marked Now block current work; items marked Later gate are deliberate future checkpoints and are not outstanding today.

Outstanding owner decisions, when they are needed and what they block
DecisionWhenWhat it blocks
Supply the canon documents, or accept that derived rows stay labelled owner-asserted.NowVerification state across most technical surfaces
Authorise repository-level intake, quarantine and scanning of the inventoried candidate roots. The inventory evidence already exists; authorisation to work on the source does not.NowGates G2–G4, and G7 by dependency
Licence for published source, and which documented chain-of-title gaps are acceptable for publication.NowGate G5, and G8 by dependency
Approval of the proposed repository names and mapping.NowGate G6
Outcome of the VPLedger source provenance audit, once intake is authorised.NowVPLedger verification; gate G3
Whether any surface may be promoted above documented architecture for a named future scope, and on what evidence.NowMaturity labels platform-wide
Approval to connect GitHub.Later gateGates G10–G11
Approve documentation RC1 after evidence review; any future source/operational release requires separate approval.NowRC1 acceptance and G12 future scope, not existing public indexing

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
Figures on this page are aggregated from current documentation recordsCoverage Registry and readiness gates in this projectVerified source on fileCounts are computed from the same data the register and gate page render.
Any DLT source set or repository has been acceptedIntake and approval evidenceNo source on fileInventory and estate-level integrity evidence exist, but no source set has completed canonical intake or been accepted, connected, imported or approved.
Documentation RC1 is owner acceptedOwner approval and verified sourcesSource claimed, not yet verifiedEvidence and owner-approval gates remain in progress; documentation RC1 does not promote software or infrastructure maturity.