Preview · not officially published. Technical information only; the planned DLT is not live.
Operations
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.
PASS means the current preview already meets the interim requirement; FIXED means corrected in this pass. 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.
Preview indexing and release gatesPASS
Noindex and crawler disallow remain; GitHub, source acceptance, domain and owner approval remain distinct.
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.
Covers launch of the interim documentation platform only. Nothing here approves a domain, indexing 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
One release-flag module drives robots meta, absolute canonical/og:url, the /sitemap.xml route (404 while off) and the prepared robots.txt text. All flags off.
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.
Noindex until releasePASS
Per-page noindex, nofollow and robots disallow remain active.
Final release approvalOWNER ACTION
Ronny's explicit approval of the interim documentation scope and launch date.
Production domain nameOWNER ACTION
Confirm byteshares.org as canonical origin before canonical URLs and sitemap are activated.
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 connectionEXTERNAL BLOCKER
Registrar/DNS access and connection happen only after release approval.
Future blockchain claimsEXTERNAL BLOCKER
Interim launch does not waive source/rights, specification/security, implementation or network-verification gates.
Runs only after Ronny's explicit release 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.
These are future evidence thresholds, not a schedule or an approval to activate blockchain, wallets, tokens, payments or a public domain. Passing the documentation target on 29 September 2026 does not pass these gates.
01 · Source and rights
Evidence required: Accepted repository-level provenance, sensitive-material exclusion, licence and complete publishable rights.
Open · not accepted
02 · Specifications and security
Evidence required: Reviewed protocol, identity, proof and governance specifications; threat model and independent security evidence.
Open · not accepted
03 · Implementation
Evidence required: Accepted builds, tests, versions, reproducible release artefacts and compatibility evidence; no documentation-only promotion.
Open · not accepted
04 · Network operation
Evidence required: Independently checked nodes, ledger state, explorer/API behaviour, data handling and incident/status sources.
Open · not accepted
05 · Owner release decision
Evidence required: Ronny explicitly approves a named scope after prior gates, repository acceptance and platform review; only then consider domain and indexing actions.
Open · not accepted
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.
Source inventory
Every candidate source set located, named and scoped, with the canonical intake scope approved.
Documentation readiness
Integrity and secrets
Hashes and manifests linked to accepted baselines; sensitive material quarantined and repository-level scans complete.
Documentation readiness
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
Canonical repository mapping
Each accepted source set has an owner-approved destination repository.
Documentation readiness
Version, build and test baseline
Build and dependency state recorded, tests classified, version baseline assigned only after provenance.
Operational readiness
Owner approves GitHub connection
Explicit recorded approval. Nothing is connected before this point.
Operational readiness
Repository import verification
Imported contents compared against the accepted source sets and their hash baselines.
Operational readiness
Site link validation
Every repository reference on this platform resolves to an accepted repository; no placeholder link is published.
Operational readiness
Platform acceptance
Release-evidence checklist reviewed, wording sweep, accessibility and mobile checks recorded as passed.
Operational readiness
Owner approves domain and public availability
Explicit recorded approval. Only after this may indexability, canonical URLs and a sitemap be activated.
Operational readiness
Gate states today: 1 ready for review, 4 in progress, 3 blocked, 4 not started, 0 approved.
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.
Counted directly from the register. Documentation coverage and source verification are tracked separately, and coverage never implies a source was inspected.
States, not percentages. Each item names what it depends on. Release controls are tracked separately on Release Control.
Depends on: —
Depends on: —
Depends on: —
Depends on: —
Depends on: —
Depends on: —
Depends on: Owner supplies documents
Depends on: D1 intake authorisation
Depends on: D1 intake authorisation
Depends on: Secrets scan
Depends on: History capture
Depends on: Intake evidence
Depends on: Documents supplied
Depends on: G10 approval
Depends on: G11
Depends on: G11 and link validation
Depends on: —
Depends on: —
Depends on: —
Depends on: Evidence from track B
Depends on: Track B closed and D1–D3
Depends on: Track C and owner approval
Depends on: Domain connected and owner launch approval
Five independent evidence levels. Documentation complete never implies source, implementation or operational verification, and no area is owner accepted.
| Area | Documentation complete | Source verified | Implementation verified | Operationally verified | Owner accepted | Note |
|---|---|---|---|---|---|---|
| Protocol Architecture | Yes | Partial | No | No | No | Canon owner-asserted; document not supplied. |
| Identity / eIDspot | Yes | Partial | No | No | No | Credential and revocation formats to be specified. |
| VPLedger | Yes | Partial | No | No | No | Estate inventoried and hashed; provenance audit open. |
| Governance | Yes | Partial | No | No | No | Governance paper pending. |
| Node Architecture | Yes | No | No | No | No | Topology draft not supplied; no node exists. |
| Explorer | Partial | No | No | No | No | Planned; no ledger to index. |
| API | Partial | No | No | No | No | No contract, no endpoints. |
| SDK | Partial | No | No | No | No | No package or language chosen. |
| Standards / Sig-56, Web4, F.I.P. | Partial | No | N/A | N/A | No | Specifications not supplied; nothing completed. |
| Security | Partial | No | No | No | No | Threat model incomplete; no audit. |
| Network Status | Partial | No | No | No | No | No network is running. |
| GitHub / source | Yes | Partial | No | N/A | No | Inventory and integrity evidenced; all candidates class C. |
Every item is derived from states already recorded in this preview. No percentage, estimate or forecast is given, because none is evidenced. An item moves only when the stated evidence exists.
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.
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.
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.
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.
Explorer and Network Status operational content
DLT ExplorerGate G12
Evidence needed: Running infrastructure and a verified telemetry source.
API and SDK surfaces, examples and versioned contracts
DevelopersGate G12
Evidence needed: An implemented contract and an accepted SDK repository.
Technical paper releases
Technical PapersGate G12
Evidence needed: Documents supplied and explicitly approved for release.
Indexability, canonical URLs and sitemap activation
Launch checklistGate After G12
Evidence needed: Owner approval of domain and public availability.
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.
Ready for documentation review
Verification pending
Verification pending
Ready for documentation review
Verification pending
Launch-gated
Blocked by evidence
Blocked by evidence
Blocked by evidence
Blocked by evidence
Launch-gated
Blocked by evidence
Ready for documentation review
| Surface | Disposition | Documentation coverage | Verification | Operational state | Release blocker | Acceptance evidence required |
|---|---|---|---|---|---|---|
| Protocol Architecture | Ready for documentation review | Covered, invariants partial | Owner-asserted | Not operational | Invariants and canon document unsupplied | Canon document and protocol invariants paper |
| Identity / eIDspot | Verification pending | Covered, credential lifecycle partial | Owner-asserted | Not operational | Credential and revocation formats unspecified | Credential schema and revocation specification |
| VPLedger | Verification pending | Covered, snapshot and storage partial | Unverified | Not operational | Source provenance audit open | Provenance audit outcome; proof and snapshot schemas |
| Governance Layer | Ready for documentation review | Covered, exceptions partial | Owner-asserted | Not operational | Exception, reversal and dispute procedures undefined | Governance architecture document |
| Node Architecture | Verification pending | Covered, roadmap partial | Unverified | No node exists | Topology draft not supplied; no site verified | Topology draft; site and host confirmation |
| DLT Explorer | Launch-gated | Covered as intent | Unverified | Not operational | No ledger to index | Running ledger and indexing design |
| Developers / API / SDK | Blocked by evidence | Covered as intent, surfaces partial | No source | No endpoint or package | No API contract or SDK codebase | API contract; SDK repository acceptance |
| Standards / Sig-56 / Web4 / F.I.P. | Blocked by evidence | Partial | Owner-asserted | Not adopted anywhere | Specifications not supplied | Sig-56 and F.I.P. specification documents |
| Technical Papers | Blocked by evidence | Register covered | Unverified | No document released | No paper supplied or approved for release | Papers plus owner release approval |
| Security | Blocked by evidence | Partial | Unverified | No control implemented | Threat model incomplete; no disclosure contact | Threat model document; disclosure route decision |
| Network Status | Launch-gated | Covered as model | Unverified | No network | No telemetry source exists | Running infrastructure and status source |
| Source / GitHub | Blocked by evidence | Covered as specification | Estate evidence available; repository acceptance pending | Not connected | Gates G1–G12 open; legal title and licensing incomplete | Repository-level intake links to inventory, hashes, history, title and licence evidence; owner approvals |
| Glossary | Ready for documentation review | Covered | Owner-asserted | Not applicable | Terms follow whichever specifications are supplied | Specification documents to confirm definitions |
Documentation only. This is the sequence to follow when the owner decides to proceed — it is not an instruction to execute anything now, and no step has been started beyond the preview documentation itself.
Every candidate source set located, named and scoped; nothing relevant left unaccounted for.
Hashes or manifests captured, classes assigned with evidence, sensitive material quarantined, ownership and licence recorded.
Each accepted source set has an approved destination; names confirmed by the owner.
Build and test state recorded, version baseline assigned only after provenance, minimum repository documents drafted.
Explicit, recorded approval. Nothing is connected before this point.
Imported repository contents compared against the accepted source sets and hashes.
Every repository reference on this platform resolves and matches an accepted repository.
Acceptance matrix reviewed, wording sweep complete, accessibility and mobile checks passed.
Explicit, recorded approval for ByteShares.org availability.
Only now: absolute canonical URLs, robots change, sitemap publication, indexability. Never before step 09.
A blank template held in this preview only. 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.
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.
Nothing in this list has been activated. The preview remains non-indexable and stays that way until the owner approves public availability.
Canonical links are emitted per page as relative paths; switching to absolute requires the confirmed public origin.
Prepared, not activated
Route list is stable and enumerable; no sitemap file is generated or served.
Prepared, not activated
robots.txt disallows everything and every page emits noindex, nofollow.
Intentionally blocking
Title, description, type and card are set per page; no image is claimed.
Prepared, not activated
No structured data is emitted. Whether to add it is an owner decision, not a default.
Decision outstanding
Every navigation and cross-page link resolves to an existing route.
Recheck before release
Unknown paths must return a clear not-found page with no invented content.
Recheck before release
Wide tables collapse to cards or scroll accessibly at 390px.
Checked this pass
Skip link, semantic headings, table captions and visible focus.
Recheck before release
A maturity badge sits beside every claim that could be mistaken for live infrastructure.
Recheck before release
No sentence may read as operational, adopted, audited or released without verified evidence.
Recheck before release
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.
| Decision | When | What it blocks |
|---|---|---|
| Supply the canon documents, or accept that derived rows stay labelled owner-asserted. | Now | Verification 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. | Now | Gates G2–G4, and G7 by dependency |
| Licence for published source, and which documented chain-of-title gaps are acceptable for publication. | Now | Gate G5, and G8 by dependency |
| Approval of the proposed repository names and mapping. | Now | Gate G6 |
| Outcome of the VPLedger source provenance audit, once intake is authorised. | Now | VPLedger verification; gate G3 |
| Whether any surface may be promoted above documented architecture by the target date, and on what evidence. | Now | Maturity labels platform-wide |
| Approval to connect GitHub. | Later gate | Gates G10–G11 |
| Domain and public availability approval, and the structured-data decision. | Later gate | Gate G12 and SEO activation |
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 |
|---|---|---|---|
| Figures on this page are aggregated from existing preview states | Coverage Registry and readiness gates in this project | Verified source on file | Counts are computed from the same data the register and gate page render. |
| Any source set, repository, connection or domain has been accepted | Intake and approval evidence | No source on file | Inventory and estate-level integrity evidence exist, but no source set has completed canonical intake or been accepted, connected, imported or approved. |
| The readiness target will be met | Owner approval and verified sources | Source claimed, not yet verified | The date is conditional; unmet conditions mean pages stay at their current maturity. |