Builders
Glossary
Documented architecture
Canonical terms used across this documentation, each with the state it is actually in. A term appearing here means it is defined in project material — not that a component bearing that name exists or runs.
- Source / verification
- Owner interim-platform canon; technical definitions not independently verified
- Document version
- Not yet assigned
- Last reviewed
- 7 October 2026
Terminology
| Term | Definition | State |
|---|---|---|
| Proposed Canon v0.1 | Owner-authorized design draft (8 October 2026) listing 35 proposed protocol invariants (INV-001–INV-035) and conformance profile C-01–C-14. A normative-design candidate awaiting owner acceptance, not adopted canon or an operational specification. | Proposed / Awaiting owner acceptance |
| Invariant | A rule that must hold for every accepted or refused state transition. In ByteShares.org documentation every invariant is proposed until the canon is adopted; none is evidenced by implementation. | Proposed / Non-operational |
| Coverage | Documentation completeness within a row's stated conceptual scope. Covered does not mean verified, implemented, approved, secure or operational. | Documentation control |
| Verification | The supporting source state for a specific claim, independent of documentation coverage. Better prose never upgrades source verification. | Evidence control |
| Provenance | Recorded origin, chronology and concept lineage. The four archive IP records support founder/originator evidence, not complete legal title to every historical component. | Recorded archive context; title gaps remain |
| Ownership / legal title | Component-specific rights requiring the applicable assignments, collaboration agreements, transfers and licensing review. Custody, hashes and founder chronology alone do not establish exclusive ownership. | Historical contractor/collaboration title gaps unresolved |
| Documentation release candidate | Documentation release candidate — October 2026; 0.9 RC1; reviewed 7 October 2026. Evidence and owner-approval gates remain in progress; not a DLT, software or network release. | Documentation only |
| Software / network release | A separate acceptance and operational event requiring source, implementation and test/operational evidence; it cannot be inferred from a documentation version or the live public site. | No DLT/software/network release claimed |
| Proposed / Non-operational | A reviewable conceptual relationship, shape or requirement, not a finalized schema, executable contract or running service. | Review boundary |
| Draft / Awaiting approval | A documentation candidate whose scope and source boundaries remain reviewable; not an approved paper, specification or release. | Paper review status |
| Mandate | Authority granted to a subject or agent with an explicit issuer, scope and validity period; delegation must not exceed the principal's scope. | Documented concept; format unspecified |
| Rule version | The explicitly referenced rule context under which an action would be evaluated, retained for historical interpretation rather than silently replaced. | Documented concept; encoding unassigned |
| Admission | The proposed boundary where an intent and identity/authority proofs are presented for rule evaluation. | Proposed / Non-operational |
| Validating node | Proposed role applying authorized rules and accepting entries; operating a node does not grant governance authority. | Documented role; no deployed node |
| Archive node | Proposed role retaining history and evidence references for audit and reconstruction, without acceptance or mutation powers. | Documented role; no deployed node |
| Read node | Proposed replaceable query surface over accepted state, with no submission or acceptance authority. | Documented role; no deployed node |
| Observer | Proposed monitoring role with no influence over acceptance. | Documented role; no deployed node |
| Anchor | A compact on-chain commitment — hash, timestamp, rule reference — that binds a record or document to the protocol history without storing the material itself. | Documented |
| AI City | ByteShares' intended long-term end-product family: an extensible modular environment with expandable white-label modules for organisations, sectors and markets. Not Boesing Consult. | Planned; not deployed |
| CTZ | Citizenship or community-eligibility function used to express scoped participation. | Documented |
| eDEV | Development and delivery function for governed digital services and institutional workflows. | Planned; not operational |
| eIDspot | Working name for the identity, credential and eligibility-proof layer. | Documented; not operational |
| Epoch | A bounded period whose closure fixes state, governance outcomes and a proof snapshot. | Documented |
| Epoch Closure | The governance step that closes an epoch and commits its snapshot. | Documented |
| Evidence register | The per-page table recording each claim, its source type and verification state. | In use on this platform |
| FILDEX | Proposed discovery and exchange interface for eligible storage-related records and services. | Planned |
| F.I.P. (FAWN Identity Protocol) | Conceptual model for accountable AI identity: agent identity, curation, memory and authority boundaries. | Concept; specification unavailable |
| Genesis Memo | The initial authorized statement of rules, roles, boundaries and starting state. | Documented |
| GROW | Growth and contribution-allocation function in the documented value model. | Documented |
| JOYY | Recognition and participation function within the canonical value model. | Documented |
| Maturity label | The development/documentation status attached to a page or model: documented, planned, prototype, in development, or awaiting approval. It is not a source-verification verdict. | In use on this platform |
| Memo Anchoring | Binding an approved memo to the protocol record via hash, timestamp and reference. | Documented |
| Merkle snapshot | A root commitment over a defined record set at an epoch boundary, allowing inclusion proofs for single records. | Documented; format to be specified |
| PIB / Petabyte | Higher-order storage-capacity accounting function related to the TIB unit. | Documented |
| PreDAO | Preparatory governance state in which scope, authority and eligible participants are defined. | Documented |
| Proof object | A verifiable record binding inputs, authority, rule version and outcome for a specific lifecycle stage. | Documented |
| Sig-56 | Signature and signalling concept binding identity, authority, rule context and intent to a verifiable action. | Concept; specification unavailable |
| TIB / Terabyte | Unit function for accounting a defined quantity of digital storage capacity. | Documented |
| UCityX | Proposed application concept related to eDEV; not an operating city platform or a synonym for AI City. | Planned |
| VPL / Vimple | Participation and value-accounting function within the VPLedger model. | Documented |
| VPLedger | Working name for the value and participation ledger; append-only, with value and participation entries kept distinct. | Documented concept; archive lineage recorded, historical title and repository acceptance open |
| Wallet-as-account | Design intention in which authority attaches to wallet-held proofs rather than a platform account. A wallet address alone establishes nothing. | Documented |
| Web4 | Positioning term for an internet layer built around verified identity and accountable participation. Not a ratified standard. | Positioning term |
Source-to-claim reading glossary
| Term | Meaning and limit |
|---|---|
| Source reference | Identifies a document or existing documentation section; a citation does not prove its claim or authorize disclosure. |
| Claim trace | Connects a specific conceptual statement to its source reference and stated limits; it is not an independent verification result. |
| Owner-reported inspection | The owner reports reading historical material. This does not mean this site independently inspected or accepted it. |
| 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. |
How terms are used
Working names are marked as such. Where a name refers to a function in the documented model rather than a product, the function is described and no product behaviour is implied.
No term here should be read as an investment product, a market, a service offering or a live system.
Evidence register
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 |
|---|---|---|---|
| Term definitions match project material | Owner-supplied canon | Source claimed, not yet verified | Definitions were drafted from owner instruction; the underlying documents have not been inspected. |
| Any term corresponds to a running component | Operational evidence | No source on file | Nothing named here is deployed. |