Words have meaning.
The language of Mister Pop: the people, places, creative work, and systems that make a shared world possible.
Capitalized names identify domain concepts. Participant labels describe responsibilities in context, not additional account types.
People
The castPeople, organizations, and responsibilities
| Term | Meaning |
|---|---|
| Principal | The accountable identity of a Person, Organization, or service account. Ownership, permissions, attribution, and commercial participation refer to Principals. |
| Person | A human Principal. Their credentials authenticate them; their responsibilities and permissions determine what they may do. |
| Organization | A Principal representing an organization. Authorized people act for it through the applicable membership and permission checks. |
| Service account | A non-human Principal that acts through granted authority. Automation does not bypass ownership or consent. |
| Creator | A Principal credited with creative work, such as artwork, an Asset, a Drop, or an Experience. Credit alone does not confer ownership or publishing authority. |
| Owner | The Principal responsible for a resource’s stable identity. Ownership and permission to perform a particular action are checked separately. |
| Experience owner | The steward of the reusable creative work and its published versions. This may differ from the Producer of any particular Installation. |
| Publisher | A Principal exercising authority to publish a resource. Qualify the object when needed: Experience publisher, Drop publisher, or Listing publisher. Publishing an offer and producing an Installation are different responsibilities. |
| Producer / Installation owner | The Principal responsible for turning an Experience version into a concrete production: Place, schedule, program, collaborators, Rights, and placement. “Organizer” is also used for this responsibility in commercial workflows. |
| Rights holder | A party that owns or controls relevant intellectual-property or distribution rights. This is distinct from the holder of a particular Platform-issued Right. |
| Partner | A Person or Organization presenting resources or services through a Partner Profile and Listings. Partner is not a separate Principal type. |
| Partner Profile | The public representation of a Partner, including its description, service area, and contact context. Individual published Listings define its offerings and capabilities. |
| Place host / operator | A party responsible for the physical access, safety, and operating context of a Place. Hosting does not automatically make that party the Experience owner or Producer. |
| Component party | A Principal’s recorded participation in a particular Installation Component, in a role such as artist, supplier, sponsor, or operator. A party relationship is not itself payment evidence or consent to commercial terms. |
| Sponsor / funder | A party contributing support to a production. A funding offer, an accepted commitment, and collected money are distinct facts. |
| Acquirer / Right holder | The Principal requesting or holding permission to use an offered resource for a particular Installation. Acquisition scope does not transfer ownership of the source. |
| Billed Principal / payer | The party authorized to bear a payment obligation. It need not be the Right holder: for funding, the offering party supplies the contribution. |
| Beneficiary | The party entitled to compensation under accepted commercial terms. Participation alone does not establish an entitlement to payment. |
| Explorer | A person discovering Places and Installations, interacting with the world and its Drops, and building their Collection. This is the audience role, not a publisher or production role. |
| Reviewer / moderator | An authorized party assessing a specific readiness requirement or reported concern. Review, verification, publication, and moderation enforcement have different meanings. |
One Principal can be Creator, Publisher, Producer, Partner, and Explorer in different contexts. These labels do not grant permissions by themselves. Attribution records who contributed; ownership records responsibility for a resource; authorization determines who may act; consent records acceptance of specific terms. Do not substitute one for another.
Productions
From idea to encounterCreative work and local productions
| Term | Meaning |
|---|---|
| Experience | A reusable creative work: its identity, intent, attribution, portable presentation, Components, Actors, and planned offerings. It can be produced at many Places and times. |
| Experience version | An immutable published form of an Experience. Each Installation selects an exact version; later creative publication does not silently update existing Installations. |
| Installation | One stable, owned, scheduled production of an Experience version at one Place. It carries the local Component graph, Space plan, Rights, and operational context. |
| Installed Experience | The Experience as configured in a particular Installation. This is a combined view of those concepts, not a third independently authored resource. |
| Experience Component / Component template | A portable authored unit or blueprint within an Experience. It provides reusable presentation, behavior, and requirements from which local Components are configured. |
| Installation Component | A local unit in an Installation’s tree: an installed creative element, a Drop-bearing element, or supporting programming such as a vendor or performance. It has a Space and may have placement, an Actor, Rights, and responsible parties. A Component need not render anything. |
| Root Component | A Component without a parent. It can supply shared placement and context for descendants and can have its own visible presentation. “Root” does not mean an invisible container. |
| Child Component | A Component beneath another Component. Its placement and presentation can relate to its parent; its own offerings remain attributable to that child. |
| Required Component | A template requirement that must be satisfied in the Installation. Required does not mean always visible or automatically acquired; rendering and Rights have their own conditions. |
| Actor | A controllable presentation entity with animation and behavior semantics, owned by an Experience Component. An Actor may use a sprite or model; it is not the Drop an Explorer acquires. |
| Sprite | A visual representation, typically animated two-dimensional artwork rendered in the world. The shoe, ticket, and key are sprites; the offers they reveal are Drops. |
| Content Asset / Asset | A reusable creative resource containing versioned material such as artwork, models, animation, or audio. An Asset supplies presentation or recognition material; a Listing supplies the terms for its use. |
| Asset resource, version, and file | A resource identifies material within an Asset; a version pins a particular form of that resource; files carry its bytes. A file upload alone does not create a Listing, acquire a Right, or wire an Installation. |
| Program | The combination of creative and supporting Components offered in a local production. A performance or vendor can be part of the program without being a Drop. |
| Summon | The guided operation that brings an Experience to a Place by creating an Installation, attempting its required acquisitions, and publishing when ready. It uses the same Installation and Rights model as Studio. Unresolved requirements leave a resumable Installation. |
The core relationship is Experience → Installation → Component tree → exposed Drops. Assets and Actors provide the presentation. Listings and acquired Rights authorize resource use. A tree can contain a visible Billboard root, visible shoe/ticket/key children, and their Drop Components another level down. The root can present the aggregate Drop collection while selecting a child presents that child’s offerings; this does not flatten the authored tree.
See Experiences, Installations, Components, and Drops.
What happens nextPublication, participation, and history
| Term | Meaning |
|---|---|
| Draft | Mutable authoring or planning state before the applicable publication requirements are satisfied. A draft Installation provides the context needed to acquire its Rights. |
| Publication | Making validated work available in its intended scope. Creative publication preserves an immutable version; Installation publication records a concrete production and its applicable facts. Publication is not a payment, moderation endorsement, or guarantee of visibility. |
| Amendment | An explicit material change to the same Installation after publication. It preserves the occurrence’s identity and appends history rather than rewriting prior evidence. |
| Upcoming / live / ended | Time-based presentation states of an Installation. These describe its operating window, not the lifecycle of the reusable Experience itself. |
| Withdrawal | Stopping future availability while preserving history. Effects on existing Rights depend on the offer’s governing policy; withdrawal and revocation are not synonyms. |
| Verification | Evidence establishing a specific identity or resource fact. Always qualify what is verified; Person verification, Place verification, and payment verification differ. |
| Moderation flag | A report of a concrete concern. A report does not itself hide a resource; enforcement is a separate authorized action. Resolving a flag does not publish or endorse content. |
| Saved | An Explorer’s bookmark for returning to an Installation. Saving is distinct from visiting, collecting a Drop, or acquiring a production Right. |
| Visit / interaction | Evidence of an Explorer’s participation or action. Use the specific event name rather than treating all engagement as a purchase or collection. |
| Collection | The Explorer’s retained Drops and participation evidence. “In Collection” does not mean they own the Experience, Asset, or copyright. |
| Collection receipt | Signed evidence tied to an Explorer, Drop version, Place, issuer, and proof of an action such as collection, claim, or purchase. It is distinct from a payment-provider receipt and does not imply blockchain issuance. |
| Redemption / consumption | Exercising an acquired allowance or entitlement under its terms. Distinguish obtaining permission from using it. |
See the Experience lifecycle and moderation model.
Rights & Commerce
An offer. A promise. Permission.Drops, offers, and permission to use
| Term | Meaning |
|---|---|
| Drop | A reusable actionable resource with creative meaning, attribution, an offering type, and an Explorer action. Published versions preserve that definition. A Drop is not a sprite, location, inventory pool, or price. |
| Offering type | What a Drop represents: a physical product, access, a digital asset, a collectible, or content. This is distinct from the action offered to the Explorer. |
| Drop action | What the Explorer can do: view, collect, claim, or buy. “Shop” may describe an external purchase destination in the UI; opening it is not proof of purchase. |
| Listing | An immutable published offer for a resource or service, defining availability, eligibility, approval, pricing, and applicable allocation or license terms. It can offer a Drop, Content Asset, Partner service, Space occupancy, or funding. Changed terms require a replacement Listing. |
| Listed / unlisted | Visibility of an offer or Partner Profile. An unlisted offer still participates in the same governed acquisition flow; unlisted does not mean unpublished or exempt from Rights. |
| Marketplace | The discovery surface for Partners and their listed offers. It is not the Explorer’s resolved world or personal Collection. |
| Planned Listing | An offer selected in an Experience blueprint for future production. Planning does not acquire a Right; each Installation acquires its own. |
| Acquisition | The governed request and process for obtaining what an offer permits. Eligibility, approval, documents, payment, and availability may need to be satisfied before a Right becomes active. Specify “Right acquisition” or “Explorer Drop acquisition” when the audience matters. |
| Right | The durable, scoped authorization resulting from a Listing acquisition. Production Rights belong to one Installation and retain the exact offer and accepted terms. A Right acquired for one Installation cannot satisfy another. |
| Right binding | The association that makes an acquired Right available to an Installation Component. The Right authorizes use; the Listing remains its provenance. |
| Allocation | A quantity or portion reserved for a use. Always qualify it: Drop allocation concerns distribution allowance; Space allocation concerns occupancy and time. |
| Inventory / supply | The Listing’s available distribution capacity. A finite supply belongs to the offer, not the Drop. An unlimited allowance does not bypass eligibility, duplicate-receipt rules, or other terms. |
| Entitlement / license | Permission to use material under acquired terms, such as a Content Asset license. It is not ownership of the source material. |
| Partner engagement | The authorized participation of a Partner in a production, derived from the applicable service Right. A directory profile alone does not establish an engagement. |
| Supporting documentation | Evidence required by an offer or Right, such as a permit, insurance certificate, or agreement reference. These records have their own submission and review history; they are not creative Content Assets. |
The production handshake is source → Listing → Installation-scoped Right → authorized use. Ownership can streamline this flow but does not erase it, including when Producers supply their own resources or occupy their own Spaces. Payment satisfies a commercial condition; it does not independently grant a Right.
See Listings and Rights and Marketplace and Economy boundaries.
Making it happenCommercial operations and product surfaces
| Term | Meaning |
|---|---|
| Commercial proposal | A versioned offer of compensation attached to an eligible Right. Acceptance records consent to the exact revision by the required parties. |
| Commercial plan / snapshot | The Installation-wide arrangement of accepted obligations and revenue treatment. It is compiled from the governing agreements and funding evidence; it does not replace Listings or create consent merely by including a party. |
| Funding commitment | An agreed contribution to an Installation. Commitment, verified collection, available funds, and authorization to spend are separate facts. |
| Recoupment | Repayment of qualifying contributed funding under its accepted limits and rate. |
| Expense | A record of an incurred cost. Recording it does not itself move money, create a payable, or change settlement obligations. |
| Settlement / closing | Reconciling financial activity and preparing the resulting participant statements and distributions. An ended presentation does not prove settlement is complete. |
| Payout / disbursement | Money movement to a recipient, requiring its own authorization and execution evidence. A forecast or statement is not proof of bank arrival. |
| Studio | The authoring and operations surface for resources, Installations, offers, Rights, and their commercial coordination. |
| Explorer app | The audience-facing mobile experience for discovery, spatial interaction, Saved Installations, and Collection. |
| Platform | The system responsible for creative publications, Places, Installations, distribution terms, Rights, discovery, and participation evidence. |
| Economy | The system responsible for payment execution, commercial accounting, reconciliation, settlement, and payout evidence. External payment providers do not define Platform identity or Rights. |
See commercial consent and funding and expenses.
Places
Somewhere becomes herePlaces, discovery, and placement
| Term | Meaning |
|---|---|
| Place | The durable physical setting of Installations, with its own identity, governance, and geographic context. A Place can contain multiple Spaces and host multiple Installations. |
| Space | A physical or operational area within a Place, such as a Front Yard, Booth, room, screen, or surface. Spaces may be nested. Each Installation Component occurs in a Space; Space membership does not by itself provide precise AR alignment. |
| Space allocation | An Installation’s planned use of a Space over a setup, live, or teardown window, with shared or exclusive access and applicable occupancy facts. |
| Capacity configuration | The occupancy limits for a particular use or layout of a Space, with their supporting evidence. Not every Space is an occupiable room or needs a capacity. |
| Geographic placement | Content positioned through the Place’s spatial context and authored geographic Anchors. It does not require matching an artwork image before appearing. |
| Image target | Exact reference artwork recognized by the camera to position a Component and its descendants. The target pins an image version, physical dimensions, and calibration. It may be shown on a screen or printed; it does not require an additional QR code. |
| Visual registration | The authored relationship between a Component and its recognition target, including the detector and the transform from the detected target to the Component. |
| Recognition artwork | The image the camera matches. It can differ from the digital replacement artwork rendered after recognition. The billboard’s full poster is the target; its background without the three sprites is the replacement presentation. |
| Discovery | Finding eligible nearby Installations and the resources needed to experience them. Geographic discovery can download image targets before the camera recognizes them. |
| Localization | Determining how authored content aligns with the physical world on a device. Discovering an Installation and recognizing its target are separate steps. |
| Resolved world | The temporary composition of eligible Installation contributions for an Explorer’s location, time, and device capabilities. It is derived runtime output, not another Experience or publication. |
| Contribution | One Installation’s resolved content contributed to that world, retaining its source identity and attribution. |
Booth and Billboard are names used by our example Spaces and creative content, not special placement types. An indoor Booth can use an image target while a separate outdoor Installation of the same Billboard Experience uses geographic placement. Both remain attached to a Place, Space, and schedule. “Portable” does not imply worldwide discovery or unlimited geographic scope.
See Spaces and occupancy and resolved worlds. Technical Anchor and Spatial Reference definitions appear under Spatial computing and assets.
Naming
Say what you meanNaming and usage
| Term | Usage |
|---|---|
| Installation | A concrete production of an Experience at a Place and time. Use “activate” for the lifecycle action that makes a Right active. |
| Experience version; Installation amendment | Version the reusable creative work. Amend the same Installation when its production details change. |
| Drop; sprite; Actor | A Drop is the actionable resource. A sprite or Actor provides its presentation. |
| Listing; Right; ownership | A Listing defines an offer. A Right authorizes scoped use under accepted terms. Ownership identifies the resource’s steward. |
| Place → Space → Space allocation | Distinguish the venue, a region within it, and its reserved occupancy. |
| Image target; geographic placement | Name the recognition or placement mode explicitly. Names such as Billboard or Booth describe the experience, not its technical mode. |
| Background without the sprites | Describes artwork that remains visible when the interactive sprites are excluded. |
| Creator; Publisher; Producer; host | Name the responsibility relevant to the action. One Principal may hold several responsibilities. |
| Published; listed; live; verified | Distinguish publication, discovery visibility, scheduled availability, and verification. |
| Experience; Installation; commercial campaign | Use the domain concept that matches the scope. Advertising is one application of an Experience; a commercial campaign describes its business context. |
Technology
Behind the curtainArchitecture and delivery
| Term | Meaning |
|---|---|
| ADR — Architecture Decision Record | A durable document that explains an important technical decision, its context, its consequences, and the alternatives that were rejected. |
| CI — Continuous Integration | Automated checks that run when code changes, such as formatting, typechecking, tests, and builds. |
| CD — Continuous Delivery or Continuous Deployment | Continuous Delivery keeps validated changes ready for a deliberate release, while Continuous Deployment automatically releases every change that passes the required checks. |
| Contract | A machine-checkable agreement about the shape and meaning of data exchanged between parts of the system. Mister Pop defines runtime transport contracts in @mr/contracts. |
| CRUD — Create, Read, Update, Delete | The four basic operations used to manage stored records. |
| Fixture | Stable example data used by tests, demonstrations, or local development. A fixture is intentionally predictable and is not live production data. |
| Invariant | A rule that must always remain true for a valid domain object or state transition. |
| Monorepo — Monolithic repository | One source repository containing multiple applications and shared packages that can be developed and versioned together. |
| POC — Proof of Concept | A deliberately limited implementation used to test feasibility before committing to a production design. |
| Schema | A formal description of valid data, including its fields, types, constraints, and relationships. |
| Source of truth | The authoritative representation of a fact. Derived indexes, caches, and external representations can be rebuilt or reconciled from it. |
| Versioned or immutable record | A record that is preserved after publication instead of being overwritten. A correction creates a new version so history remains auditable. |
APIs, applications, and runtimes
| Term | Meaning |
|---|---|
| API — Application Programming Interface | A defined way for software components to communicate. In this repository, the mobile app and Studio call versioned HTTP endpoints exposed by the platform. |
| Deep link | A URL that opens a specific screen or resource inside an installed app, such as mrpop://places/:placeId. |
| EAS — Expo Application Services | Expo’s hosted services for building, signing, submitting, and updating React Native applications. |
| Expo | A framework and toolchain around React Native that provides development tooling, application configuration, native modules, and build services. |
| Expo Go | Expo’s general-purpose development client. It can run compatible JavaScript projects without producing a custom native build, but it cannot contain arbitrary project-specific native code. |
| Hermes | The JavaScript engine commonly used by React Native applications. |
| HTTP — Hypertext Transfer Protocol | The request-and-response protocol used by web browsers, mobile clients, and APIs. |
| JSON — JavaScript Object Notation | A text data format used for API messages, configuration, manifests, and structured geometry. |
| Metro | The JavaScript bundler and development server used by React Native. |
| Native module | Swift, Objective-C, Kotlin, Java, C, or C++ functionality exposed to React Native JavaScript through a supported bridge or module interface. |
| React Native | A framework for building native iOS and Android interfaces using React and JavaScript or TypeScript. |
| SSR — Server-Side Rendering | Producing HTML on the server for an incoming request instead of relying entirely on browser-side rendering. |
| UI — User Interface | The screens, controls, content, and interaction states presented to a person. |
Cloudflare and data
| Term | Meaning |
|---|---|
| Cloudflare Email Service | Cloudflare’s transactional email product. Mister Pop sends sign-in codes through its Workers binding, which is an in-process call requiring no API key. |
| D1 | Cloudflare’s managed serverless SQL database with SQLite semantics. Mister Pop stores canonical relational platform data in D1. |
| Durable Object | A Cloudflare compute and storage primitive that provides a single coordination point for one logical object. Mister Pop reserves it for state that needs serialized concurrency, rather than ordinary relational CRUD. Platform enforces scarce allocation in D1. |
| FTS5 — Full-Text Search version 5 | SQLite’s built-in full-text indexing and search module. |
| Migration | An ordered, repeatable change to a database schema or its required data. |
| R2 | Cloudflare’s object storage service. Mister Pop uses it for large binary content such as assets, images, video, and manifests rather than storing those bytes in D1. |
| Service token | A non-human credential used by one application or automated process to access another protected service. |
| SQL — Structured Query Language | The language used to define, query, and update relational databases. |
| UUID — Universally Unique Identifier | A 128-bit opaque identifier designed to be unique without a central sequence. Mister Pop uses database-generated UUID version 4 values for surrogate database IDs and keeps human meaning in separate fields such as slugs and role keys. |
| Worker | A Cloudflare serverless application that handles requests at Cloudflare’s edge runtime. apps/platform is deployed as a Worker. |
| Wrangler | Cloudflare’s command-line development and deployment tool for Workers and related services. |
| Zod | The TypeScript-first validation library used by @mr/contracts to validate data at runtime. |
Mobile and network testing
| Term | Meaning |
|---|---|
| APK — Android Package Kit | An installable Android application package, commonly used for direct preview distribution. |
| Emulator | Software that represents another device environment, such as an Android Virtual Device. It is useful for development but does not replace physical-device performance testing. |
| iOS Simulator | Apple’s Mac-hosted environment for running iOS applications. It shares aspects of the Mac runtime and is not equivalent to physical iPhone hardware. |
| LAN — Local Area Network | The private network connecting nearby devices, usually through the same Wi-Fi router. A physical phone uses the Mac’s LAN address to reach a locally running API. |
| Localhost | The current device itself. localhost in an iOS Simulator can reach the Mac in this setup, while Android Emulator commonly uses 10.0.2.2 to refer to the host Mac and a physical phone needs the Mac’s LAN address. |
| Physical-device testing | Running the application on real phone hardware to measure behavior that simulators cannot faithfully represent, including camera tracking, GPU performance, memory pressure, battery use, and thermal state. |
Spatial computing and assets
| Term | Meaning |
|---|---|
| Anchor | A durable, named AR placement target owned by one Spatial Reference, whose pose and optional surface or feature semantics are authored inside its revisions. Components may bind Anchors by role; the Anchor’s Place, governance, and localization derive through its Spatial Reference rather than independent Place or Principal relationships. |
| AR — Augmented Reality | Digital content rendered in relation to a live view or model of the physical world. |
| ENU — East, North, Up | A local metric coordinate frame tangent to Earth at a chosen origin. Mister Pop projects nearby geographic Anchors into a shared ENU-like frame so their relative geometry remains rigid during one camera session. |
| Fiducial marker | A deliberately designed visual target whose known geometry helps a camera estimate position and orientation. QR-like planar targets and purpose-built three-dimensional markers can provide deterministic alignment at a venue. |
| GNSS — Global Navigation Satellite System | The family of satellite positioning systems that includes GPS. Phone GNSS is useful for discovery and coarse initialization but does not provide shared centimeter-level AR placement by itself. |
| VR — Virtual Reality | A fully simulated environment that replaces the user’s view of the physical world, usually through an immersive headset. |
| XR — Extended Reality | An umbrella term for experiences that combine or replace physical reality with digital content, including AR, VR, and mixed reality. Use the more specific term when the implementation boundary is known. |
| Draw call | One instruction from the CPU to the GPU to render a set of geometry. Many separate primitives or materials can increase draw calls and reduce mobile performance. |
| FPS — Frames Per Second | The number of rendered frames displayed each second. Higher and more stable FPS generally produces smoother motion and tracking. |
| GL — Graphics Library | A historical abbreviation used in graphics APIs such as OpenGL. Khronos formally expands glTF as “GL Transmission Format,” so “Graphics Library Transmission Format” should not be treated as the official glTF name. |
| GLB — Binary glTF | The .glb single-file binary container for a glTF asset. It can package scene JSON, geometry, animation data, and images into one binary blob. |
| glTF — GL Transmission Format | Khronos’s royalty-free format for efficiently transmitting and loading scenes and models. A .gltf asset may reference separate binary and image files, while a .glb file uses the binary container. |
| GPU — Graphics Processing Unit | Hardware specialized for graphics and parallel computation. |
| H3 | A hierarchical geospatial indexing system that divides the world into cells that are usually hexagonal. Mister Pop uses H3 cells to find nearby candidates before performing exact geometry checks. |
| KTX2 — Khronos Texture 2 | A texture container format designed for efficient delivery to graphics hardware, including compressed and GPU-ready texture data. |
| Material | A description of how a surface should appear, including color, texture, metallic, roughness, transparency, and related properties. |
| Mesh | An object represented by vertices and primitives. Its visible surfaces are commonly composed of triangles. |
| Spatial frame | A coordinate system in which poses and transforms are expressed. A shared spatial frame lets every participant and every Component agree on the same relative world geometry. |
| Spatial Reference | A stable identity for an authored physical site with immutable localization captures. Captures retain artifacts, canonical Anchor poses, calibration, quality requirements, and provider references. |
| Space publication snapshot | The applicable Space facts preserved when an Installation publishes or is materially amended. The operational Space remains mutable; its current configuration does not rewrite earlier publication evidence. See Places, discovery, and placement. |
| Spatial frame refinement | Confidence-bearing evidence that corrects the translation or orientation of a running Spatial Frame. A refinement moves the shared world as one unit rather than relocating an individual Component. |
| Spatial frame session | The runtime owner of one camera session’s Spatial Frame Transform and its accumulated localization evidence. It locks the initial frame, fuses refinements, and publishes atomic whole-world corrections. |
| Localization observation | Provider evidence about where a participant device is relative to a Spatial Frame. GNSS, VPS, visual markers, UWB, and platform tracking can all produce observations; none of them becomes durable world identity. |
| Spatial frame transform | The resolved mapping from a canonical Spatial Frame into one device’s local AR coordinate system. Native renderers consume this transform and place all world content beneath it as a unit. |
| Visual landmark | A persistent physical feature with a known pose in the canonical world, such as a facade corner, mural, scoreboard, or purpose-built marker. Recognizing it lets a device refine its shared Spatial Frame without making the landmark itself a new content hierarchy. |
| UWB — Ultra-Wideband | Short-range radio technology that can provide precise ranging between supported devices and surveyed hardware. UWB can refine a shared frame in controlled venues but does not independently solve every aspect of position and orientation. |
| VPS — Visual Positioning System | A system that matches camera observations against a previously mapped physical environment to estimate a device pose more precisely than raw geographic coordinates typically allow. |
| Primitive | A renderable portion of a mesh with one drawing mode and material. In glTF, primitives are useful approximations for draw-call budgeting. |
| Texture | An image or encoded pixel resource applied to a surface. |
| Triangle | The basic surface unit used by most real-time meshes. Higher triangle counts usually require more GPU work. |
Performance
| Term | Meaning |
|---|---|
| Cold load | Loading content without relying on an already initialized application state or cached asset. |
| Memory peak | The highest observed amount of application memory used during a measurement period. |
| Performance budget | A measurable upper or lower limit that content or code must satisfy, such as maximum file size, draw calls, or memory use and minimum sustained FPS. |
| Thermal state | The operating system’s assessment of device heat pressure. Sustained heat can cause CPU or GPU throttling and degraded performance. |
| Warm load | Loading content after the application or asset cache has already been initialized. |
Tokenization
| Term | Meaning |
|---|---|
| NFT — Non-Fungible Token | A uniquely identifiable blockchain token. The token standard alone does not define what legal, commercial, or product rights the token conveys. |
| On-chain | Recorded or executed on a blockchain rather than only in the platform’s private database. |
| RWA — Real-World Asset | A physical asset, entitlement, or legally meaningful interest represented or referenced through a digital record or token. |
| Tokenization | Creating a portable digital or on-chain representation of an asset, receipt, or entitlement. Mister Pop has tokenization contracts and schema, but no implemented issuance provider; Platform remains the canonical database. |