> For the complete documentation index, see [llms.txt](https://docs.mymagma.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mymagma.com/reference/glossary.md). # Glossary Quick reference for all terms used across the Magma platform. *** **Activity Feed** * A chronological, permanent log of every event across all your buildings — document uploads, approvals, rejections, stakeholder joins, 3D model changes, and more. Accessible from the left navigation. Unseen items are highlighted and automatically cleared when you visit the feed. **Annotation** * A comment or mark placed directly on a specific area of a document page. Annotations support threaded replies, @mentions, emoji reactions, and file attachments. There are two annotation types: `comment` (collaborative discussion) and `redact` (blacking out sensitive content). **Asset Manager** * A stakeholder role that acts on behalf of the building owner to manage real estate assets. Asset Managers can validate any document, mint the DTT®, and manage rewards — essentially sharing the owner's most critical responsibilities. **BIM (Building Information Modeling)** * A process and data standard for creating structured digital representations of buildings. In Magma, BIM data is stored in IFC files uploaded to the BIM 3D Viewer, and enriched with 12 categories of structured fields per object. **BIM 3D Viewer** * The interactive 3D model environment in Magma, powered by Speckle. Every physical element of the building can be selected and enriched with structured data across 12 sections. **Blockchain** * A distributed, tamper-proof public ledger. In Magma, the VeChain blockchain stores the DTT®s, document hashes, and BIM object records. Once data is recorded on-chain, it cannot be changed or deleted. **Bookmarks** * A personal collection of documents marked for quick access within the Data Room. Bookmarks appear in a dedicated sidebar panel (312px, right side) and are user-specific. **Building Wallet** * A blockchain wallet created for each building during the creation wizard. It owns the building's DTT® and is separate from the owner's personal stakeholder wallet. Required before minting. **Child Token** * A record within the building's DTT® representing a single validated asset — one document version or one BIM object version. All child tokens belong to the same building's DTT®. **Classification Override** * In the Scan Viewer, the ability to manually correct the AI's element classification. Overrides are stored with a note and a full audit trail. **Data Room** * The secure document repository within a building's DTT®. Organized by Magma Index levels and document categories (A–T). Offers tree view, list view, bookmarks, My Vault, and full-text search. **Digital Twin** * A structured digital representation of a physical building, containing all data about its ownership, structure, technical systems, materials, and history. **Digital Twin Fidelity** * The level of detail specified for each 3D model level during building creation (Step 4). Options: Simplified Render, Detailed Render, or Data Tagging (for Wired level). **Document Hash** * A cryptographic fingerprint of a document's content. Visible to users in the document information panel. Stored on-chain after minting. Used to verify that a document has not been altered. **DTT® (Digital Twin Token)** * The blockchain-based record representing a building on VeChain. One DTT® per building. It permanently and verifiably anchors every validated document and BIM object contributed to the building, and grows as new data is minted. **E57** * The industry-standard file format for 3D point cloud data from laser scanners. Used in Magma's Scan Viewer. Also stored as document 2-006 (3D Scan File) in the Architecture level of the Data Room. **Fluid Synoptic** * The feature for tracking utility meters (Water, Electricity, Gas, Heating, Cooling) across a building, assigning them to served areas and tenants. Also includes the Identity Profile for recording on-site visits. **Gallery** * A visual collection of building photos and media. Supports upload (100MB max), lightbox viewing, public sharing via access code link, and setting the building cover image. **Genesis** * The first and foundational level of the Magma Index, covering all ownership, legal, financial, insurance, and diagnostic documents that establish the building's identity and legal standing. **Hash (cryptographic)** * A fixed-length string that uniquely identifies the content of a file. If the file changes by even one character, the hash changes completely — which makes hashes ideal for proving a document has not been altered. In Magma, each document version's hash is visible in the document information panel, recorded on the blockchain after minting, and permanently preserved. **IFC (Industry Foundation Class)** * The open standard file format for BIM data. Accepted by Magma's BIM 3D Viewer. IFC files contain structured information about building elements (walls, doors, equipment, etc.) including their geometry and properties. **Identity Profile** * A sub-feature within the Fluid Synoptic tab that records on-site visits to the building — tracking which Property Manager, Energy Manager, Facility Manager, and tenants were present on a given date. **Initialization Wizard** * The form that opens in the BIM 3D Viewer when you click on an uninitiated 3D object. It guides you through filling in the object's data fields and includes an "Original BIM Data" assistant for referencing raw IFC properties. **Intrinsic Value** * The base score assigned to a document type for a specific building type and index level. Used in Magma Index calculations and reward distribution. Varies by building type — the same document has different intrinsic value for a Hotel vs. a Warehouse. **Lot Division** * The feature for documenting how a building is divided into individual lots and parking spaces, including tenant assignments, lease terms, surface areas, and rent amounts. **Magma Index** * A score (0–100%) measuring how digitally complete a building is. Evaluates five levels, considering document quantity, quality, provenance, validator completeness, stakeholder reputation, and data expiry. Affected by building type. **Micro Index (µI)** * A document's percentage contribution to its level's Magma Index score. Visible in the Value Contributions tab and (in developer mode) the Building Index Details accordion. **Minting** * The process of recording validated building data permanently on the blockchain. It anchors each validated document and BIM object to the building's DTT® and distributes MRT rewards to contributors. A 13-step process. **MRT (Magma Reward Token)** * The reward token distributed to stakeholders whose data contributions are validated and minted. Paid to your stakeholder wallet after minting. **My Vault** * A filter in the Data Room that shows only documents you have personally uploaded. **On-chain record** * Data stored on the blockchain. Once recorded, it is immutable — it cannot be changed, deleted, or tampered with. In Magma, on-chain records for a building include all minted document hashes and BIM object versions. **Pay-as-you-go** * A billing option for specific resources (API operations) that charges per use rather than a fixed monthly amount. Available on Premium and Infinity subscription plans. **Redaction** * An annotation type that blacks out a rectangular area of a PDF document. Drawing one or more redaction boxes and saving creates a new document version with those areas permanently blacked out. **Reputation** * An integer score (1–5, default 3) reflecting a stakeholder's history of quality, validated contributions. Global across all buildings. Increases by +1 for every 5 minted validations (capped at 5). Affects the Magma Index contribution and MRT reward amount for that stakeholder's contributions. **Scan Viewer** * The point cloud visualization environment. Displays E57 laser scan files of the building. Powered by an external SDK embedded as an iframe. Features AI-based element segmentation and BIM comparison. **Stakeholder Agreement** * The relationship between a stakeholder and a building, created when an invitation is accepted. Defines the stakeholder's role, minting rights, and reward eligibility. Can be PENDING, ACTIVE, or REVOKED. **Stakeholder Wallet** * A personal blockchain wallet linked to a Magma user's profile. Receives MRT token rewards after minting. Connected via Venly on VeChain. Separate from the building wallet. **Task** * An action assigned to a specific stakeholder that requires their attention — validating a document, correcting a rejected document, updating an expired document, validating a BIM field change, reviewing a lot division or energy meter, or initiating minting. Tasks are auto-created from platform events and auto-completed when acted upon. **Uploader** * The stakeholder designated to upload a specific document type. Each document type has a designated uploader role — only stakeholders with that role see the upload button for that document type. **Validator** * A stakeholder designated to approve or reject a specific document or BIM field change. Each document type has up to three validator roles (primary, secondary, tertiary). All configured validators must approve for the document to reach Validated status. **Value Contribution** * The index points a specific document or BIM object contributes to the Magma Index. Visible in the Value Contributions tab of the building profile. **Venly** * The custodial wallet provider integrated into Magma. Manages VeChain private keys for users — no seed phrase required. Used for both stakeholder wallets and building wallets. **VeChain** * The primary blockchain network used by Magma. A public, enterprise-focused blockchain with low fees and high throughput. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mymagma.com/reference/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.