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
- 26 September 2026
Terminology
| Term | Definition | State |
|---|---|---|
| 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. | Documented |
| 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 evidence statement attached to a page or model: documented, planned, prototype, in development, or awaiting approval. | 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; provenance audit ongoing |
| 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 |
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. |