Canonical glossary

Every professionally designed project deserves to be remembered. Design is one of the few professions where years of thought, collaboration and craftsmanship often disappear the moment a project is complete. The sketches are forgotten. The decisions live inside email threads. Specifications are scattered across spreadsheets. Product information is buried in folders. Warranties are lost. The reasoning behind thousands of design decisions slowly disappears. We believe that shouldn't happen. We believe every professionally designed project deserves a permanent place where its story can live. Not just while the work is happening. For everything that comes after. That belief became The Design Registry. We believe beautiful work deserves beautiful records. Designers don't simply decorate spaces. They solve problems. Balance budgets. Coordinate dozens of professionals. Guide clients through hundreds of decisions. They leave behind craftsmanship that often lasts for generations. The work deserves to be respected. That means respecting the process that created it. Every concept. Every specification. Every product. Every revision. Every installation. Every conversation. Every milestone. Every decision. Preserved. Beautifully organized. Connected forever. The project ends. The Registry doesn't. Projects are temporary. The Registry is permanent. While a project is active, it becomes the place where Designers, Clients and Providers work together. As decisions are made, products are specified, drawings are approved and installations are completed, the Registry quietly grows. When the project is finished, nothing is archived away and forgotten. Instead, it becomes a living record of everything that made the project possible. Years later, the Registry still remembers. The paint colour. The lighting specification. The millwork drawings. The installation photographs. The warranties. The manuals. The decisions. The story. Software should respect the craft. We aren't interested in building software that simply manages tasks. We want to build software that respects the people who create exceptional spaces. That means reducing complexity instead of adding it. Choosing clarity over noise. Designing interfaces that feel calm. Giving every piece of information a meaningful place. Making technology disappear so the work can take centre stage. The software should never become the story. The work should. We build for professionals. The Design Registry — The permanent record of every professionally designed project.

A reason-bound, time-limited and visibly disclosed Registry support or operational session inside another Workspace. It requires explicit authority, recent authentication and immutable audit and must never be labeled as ordinary login impersonation.

An explicit, scoped and revocable authorization relationship allowing a User, Workspace or Project Participant to reach defined records or actions. It supplements but never bypasses Membership and Access Role evaluation.

A Calendar Event that represents a committed meeting, visit, delivery, installation or other attendance-based engagement with named participants and location or connection details.

A versioned request for an authorized person to approve, reject or request changes to a defined Project artifact, selection, cost, scope or milestone.

Participant-readable chronological history of authorized operational events, communications and work. Activity is optimized for understanding what happened; it is not the immutable security and change record.

The immutable, access-controlled record of consequential creation, change, authorization and system events, including actor, time, source and safe before/after evidence where appropriate.

A typed relationship linking a File to a Note, Task, Conversation, approval or other canonical record. It is not a duplicate File.

A governed Pipeline Record submitted by a prospective Designer or Provider and evaluated using category-specific questions, evidence and approval work.

The restricted account state allowing an authenticated applicant to view and complete only their pending Application experience until approval, rejection, withdrawal or expiry.

A Workspace-configurable bundle of capabilities, record scopes and field-visibility rules stored as a governed published version. It determines permitted actions but never expands authority beyond protected platform boundaries.

An approved external platform connected for a defined capability and governed through documented data boundaries, authorization, events, monitoring and ownership.

A permission-aware capability that extracts, drafts, summarizes, classifies or recommends while keeping consequential authority with an authorized person.

A proposed value, action or text generated by AI that remains distinguishable from approved canonical data until an authorized person accepts or edits it.

The company-wide Version 2.0 source of reasoning for Brand, Marketing, Website, Product, Engineering, AI, Design, Sales, investor communication and future documentation. It explains why decisions exist, how they should feel and what evidence makes them ready.

A governed Project cost grouping with planned, approved, committed, actual and forecast values. Items and commercial records roll into categories instead of maintaining unrelated totals.

A governed administrative editor for drafting, validating, previewing, publishing and versioning configuration such as Pipelines, Forms, Project Templates, Access Roles or Notification Templates.

The architecture principle requiring shared services and components for common capabilities across Admin, Designer, Provider and Client experiences.

An experience principle requiring clear hierarchy, progressive disclosure, meaningful empty states and restrained visual noise so complexity feels considered rather than overwhelming.

The canonical Provider Category for general contractors and specialized construction trades delivering defined Project scope, milestones, site work and completion evidence.

The person or organization receiving design services and participating in a permission-scoped Client Portal.

The canonical Client Entity profile connecting contact preferences, addresses, matching information, Project Opportunities, Projects, decisions, Files, Tasks and Communications.

A structured qualification, licence, insurance or compliance record with issuer, identifier, verification state, dates and a relationship to one or more versioned Files.

A time-bound, source-aware measure of available workload or resource capability. A typed percentage alone is not sufficient for reliable Matchmaking or scheduling.

The current planned date for completing the Project. It is distinct from an individual phase target, milestone date, delivery date or installation appointment.

A scheduled occurrence linked to authorized Project or Workspace context, with start, end, timezone, participants, resources and optional external calendar synchronization.

A contextual response attached to a supported record, deliverable or conversation thread. A Comment inherits an explicit visibility policy and does not replace a durable Decision or Internal Note.

A versioned, approved change to awarded scope, amount, schedule or terms that preserves the original Work Order and its acceptance history.

A contractually defined amount or percentage earned for a transaction or service. The basis, rate, recipient, recognition rule and disclosure requirements must be explicit.

A material, fixture or component associated with construction scope, categories, quantities, specifications, budgets and field coordination.

A time-stamped assessment of an Item’s physical condition at receiving, storage, release, delivery or installation, supported by quantity, notes and evidence.

A durable communication thread with participants, channel messages, assignment, tags, visibility and links to Projects or other canonical records.

A governed exchange or touchpoint through email, SMS, calling or in-app messaging. Communication is the general concept; channel records preserve their channel-specific delivery and consent states.

A governed record of a call attempt or completed call, including participants, number, timing, disposition and permitted links to recording, transcript or follow-up.

The permission-scoped, Designer-led Project experience through which a Client sees approved information, communicates and completes permitted decisions, approvals, documents and payments. It is a view of canonical records, not a separate Project.

A deliberate non-interactive availability state for an announced but unavailable capability. It must not navigate, imply completion or appear as an unexplained disabled control.

The authoritative platform record for a business fact. Other screens and integrations reference or project it instead of creating conflicting editable copies.

A reverse-built, evidence-based description of how the live product behaves today, including routes, screens, fields, states, data behavior and known gaps.

A permissioned relationship between a Workspace or User and an external service, with environment, scopes, health, last synchronization, revocation and accountable owner.

The machine-readable record of a reusable component’s stable key, version, maturity, package, owner, variants, events, consumers, accessibility standard and replacement state.

The governed readiness state Proposed, Concept Designed, Beta, Approved, Deprecated or Removed. A visual concept is not implementation-ready until its contract and required evidence exist.

A bounded indicator of model or extraction certainty used to prioritize review. Confidence is not correctness and never replaces validation or required human approval.

A design professional who may work independently or as a member of a Designer Studio Workspace. Capitalized when referring to a governed platform role.

An independent design business operating under its own brand within a Design Registry Workspace.

The canonical business profile for a Designer Studio, including identity, matching criteria, service areas, capacity, credentials, team relationships, Assignments and network standing.

A person-level professional extension for an individual Designer. It belongs to a User and Membership and must not duplicate the Designer Studio Profile.

A durable Project record of what was decided, by whom, when, against which version and with what downstream effect.

A File or generated artifact with governed business meaning, such as a plan, contract, Proposal, Invoice, brief or specification. Document identity and version remain distinct from the underlying binary.

A versioned Project or Work Order output with an owner, due state, review requirements, approval status and related Files or Documents.

A furnishing, accessory, textile, art or other selection associated with rooms, shopping lists, approvals, purchasing and installation.

The authorized list of Items, quantities, origin, destination, crew, vehicle and handling requirements released for one delivery movement.

A documented incomplete, damaged, incorrect or unacceptable condition requiring assignment, evidence, resolution and closure.

A schema-driven form rendered from a published version of stable Field Definitions, layout, conditions and validation rather than feature-local hard-coded controls.

A durable fact that something meaningful occurred, used to drive activity, notifications, automation, integrations and AI monitoring.

A named semantic design decision for colour, typography, spacing, radius, elevation, motion, layout or layer consumed consistently instead of introducing local visual constants.

A calendar date with no time or timezone, used for concepts such as due dates or anniversaries when an instant is not intended.

A durable person or organization record such as a Designer Studio, Client or Provider. An Entity may remain passive or be connected to an authenticated Workspace.

The canonical, permission-aware profile of one Entity. Shared identity and relationship modules are reused while Designer Studio, Client and Provider Category sections add the information their work requires.

The current source-attributed expected date or window for a Shipment or purchased Item to reach its receiving destination. It is an estimate and remains distinct from actual receipt.

A sent or received email record with participants, headers, delivery state, authorized body and attachments, classified to relevant Projects or records where possible.

The shared permission-aware collection interface for searching, filtering, sorting, selecting, acting on, exporting and navigating canonical records at operational scale.

The final server-evaluated result after account and Membership state, protected boundaries, Access Roles, Teams, Access Grants, record relationships and field rules are combined.

An isolated application and service configuration such as development, preview, staging or production with its own data, domains, credentials and callbacks.

A permission-scoped projection of authorized records in a defined format, with source, filters, fields, generated time and audit where required.

The canonical international phone-number representation used for dialing and communications integrations, stored alongside the user’s raw input and optional extension.

A stored binary object with immutable identity, version, metadata, visibility and links to canonical records.

An immutable published snapshot of a Dynamic Form’s fields, layout, rules and mappings. Existing submissions retain the version used at capture.

An approved definition of intended product behavior used to guide design, engineering, QA, migration and acceptance.

The explicit result determining whether a field is hidden, redacted, visible read-only or visible editable for the current audience and record context.

A versioned contract containing a stable field key, type, label, validation, normalization, privacy, visibility, edit and formatting rules used by forms and downstream projections.

The canonical configurable Provider Category for approved services that do not yet warrant a dedicated Category workflow. Repeated patterns may later graduate into a governed Category.

The traceability section that maps every recorded current-product limitation to an owning future specification, required correction and release evidence. A finding remains open until implementation, migration, permissions, states and regression tests are accepted.

The explicit authorized confirmation, correction or rejection required before AI output creates consequential communication, commercial, payment, access, approval or assignment effects.

The canonical Provider Category for installation planning, readiness checks, placement, assembly, completion evidence and deficiencies.

Durable commentary visible only to its authorized internal audience, with author, timestamps, mentions, links, attachments and revision evidence. It is not a Client message or an Audit History event.

A versioned request for payment tied to an approved Client engagement, Work Order, purchase, milestone, time entry or other supported commercial basis.

A canonical Project object representing a product, material, furnishing, fixture or tracked physical component with pricing, sourcing and operational status.

A governed classification for Project Items used for organization, field behavior, budget roll-ups, reporting and workflow. Construction and Decorating category sets may differ.

A Project Item included in an installation plan with destination Space, placement requirements, readiness, delivery status, condition and completion evidence.

A message delivered within an authorized Registry Conversation. It is distinct from an Internal Note and respects participant visibility.

A traceable ingestion process that preserves source, mapping, proposed values, validation, user confirmation, errors and final created or updated record identities.

The guarantee that safely retrying the same command or external event does not create duplicate business effects.

The visual and product principle that premium quality comes from editing, spacing, precision, materiality and confidence—not ornamental excess, hidden obligations or unnecessary features.

A maintained source file rendered into the internal business hub and designed to be safely updated by people or AI without duplicating content.

The canonical Provider Category for businesses that price, detail, fabricate, revise, deliver or install custom cabinetry, architectural woodwork and related made-to-order elements.

The canonical Provider Category for site measurement, surveys, existing-condition documentation, floor plans, drafting and related technical deliverables.

The governed relationship connecting one User to one Workspace, including lifecycle state, Teams, Role Labels and sources of effective access.

A signed, expiring invitation for a person to create or connect a User and accept a proposed Workspace Membership without granting access before authorization completes.

A zero-duration governed Project or Work Order checkpoint representing a consequential target, handoff, decision or completion event.

The structured, permission-controlled facts used to determine eligibility and compatibility between Clients, Designers, Projects and Providers.

The governed decision-support process that checks eligibility, evaluates structured compatibility and produces explainable recommendations without automatically awarding work.

A Designer Studio or qualified Provider evaluated within one identified Match Run. Use category-specific labels such as Compatible Designers or Compatible Providers in the interface instead of the ambiguous generic label Partner.

An amount or percentage added to a cost to determine a selling price. Markup is calculated on cost and is not interchangeable with margin.

The portion of revenue remaining after defined costs, expressed as an amount or percentage of revenue. Its calculation must name the included cost basis.

A field allowing multiple stable option relationships with defined ordering, limits, search, clear and select-all semantics; values are never stored as comma-joined text.

The governed participation status of a Designer Studio or Provider, such as Onboarding, Active, Paused, Suspended, Offboarding or Inactive. It is distinct from application, Workspace and credential states.

A user- or Workspace-facing alert generated from a governed Domain Event and delivered through one or more configured channels.

A versioned, editable presentation of one governed notification event, defining audience, channel, variables, sender identity, conditions, fallback and preview while preserving protected trigger meaning.

The administrative system for configuring and testing Notification Templates against the versioned cross-product Domain Event catalogue.

A template-aware roll-up across enabled Project Phases. The calculation method and included requirements must remain explainable.

A controlled invitation asking a Designer or Provider to review an opportunity and accept, decline or counter within defined visibility and timing rules.

A governed set of stable option keys with editable labels, descriptions, ordering, colour and lifecycle metadata reused by selectors, grids, filters, exports and reports.

A qualified external business that supplies products or specialized services to Projects. This is the canonical term for network participants outside Designer Studios and Clients.

The governed classification that determines a Provider’s application, matching questions, portal, operating workflow, evidence requirements and capabilities.

The approved, versioned relationship confirming that a Provider may operate in one Provider Category, with its status, service areas, capabilities, credentials and review dates.

The canonical Provider Category for photographers delivering scheduled shoots, shot requirements, usage rights, selections and final media.

An Entity stored and managed in the platform without its own authenticated Workspace. It may be provisioned later.

An explainable percentage of applicable profile requirements that are complete, valid and sufficiently current. It is not the same as qualification, readiness or Matchmaking eligibility.

The operational centre of the platform. Projects connect Clients, Designers, Providers, tasks, schedules, items, budgets, files, communications and commercial records.

The canonical, durable record for one Project. Every Admin, Designer, Client and Provider view is a permission-scoped projection of this record rather than a separate copy. A Project Record is permanent for that Project: the Project may complete, but the Registry record remains a connected story.

An experience label for the organized collection of a Project’s permitted phases, decisions, documents and outputs. It is not a separate data entity and should not replace Project or Project Record in technical labels.

A qualified potential Project that has not yet been converted into the canonical operational Project record.

A reusable configuration that creates the phases, tasks, milestones, forms, deliverables, schedules and Provider work expected for a type of Project.

One of the seven canonical organizational phases: Concept, Design, Design Package, Construction Administration, Decorating, Procurement and Installation. Project work uses phases; Pipeline Records use stages.

The single phase used for high-level communication and portfolio reporting while detailed work may continue across overlapping phases.

A calculated measure of completion within one Project Phase based on governed tasks, milestones, approvals, deliverables and exceptions. It is not a freely typed percentage.

A calculated or explicitly overridden operational signal such as On Track, Needs Attention or At Risk, supported by visible reasons and freshness.

A person, Workspace or qualified Provider connected to a Project through an explicit role, assignment or access grant.

The governed relationship assigning a Designer, Provider, team or user to defined Project scope. It may create permission-scoped access but is not itself a Work Order.

A Project Template or Project-level declaration that a qualified Provider Category is expected for defined scope, timing, evidence and handoff conditions.

The Provider-facing operational projection of accepted Project scope, usually created from a Project Assignment and Work Order. It contains only the work, records and actions the Provider is authorized to operate.

A configurable sequence used to qualify and progress records such as leads, applications or opportunities. Pipelines create or qualify durable records; they do not replace Projects.

One instance moving through a Pipeline version, with its field values, stage, owner, activity, tasks, communications and outcome.

A versioned commercial document presenting scope, pricing, terms and acceptance requirements to a Client or in response to a Provider opportunity.

A purchasing commitment for products or materials, with line items, Vendor details, expected arrival dates, acknowledgements and receiving relationships.

The governed set of planned payment obligations, amounts, due rules and milestones associated with a Proposal, Work Order, Invoice or Project.

A recorded transfer against a commercial obligation, with method, processor or manual reference, amount, currency, status, timestamps and reconciliation evidence.

A transfer of payable funds from the Registry or payment platform to an eligible Designer or Provider after required conditions, adjustments and controls are satisfied.

The controlled process from approved selection through quote, purchase, acknowledgement, shipment, receiving, storage, delivery, installation and issue resolution.

Evidence that an authorized delivery reached its destination, including time, recipient or sign-off, photographs, exceptions and delivered quantities as permitted.

A versioned, branded Client-facing webpage assembled from authorized Project content and optionally exported to PDF. It never exposes internal notes, hidden financials or Provider-private information by default.

The audience-specific authenticated experience through which a Provider receives Offers and operates authorized Jobs using modules configured for its Provider Category. The underlying organization remains a Workspace.

An immutable approved configuration snapshot used by new records or workflows. Later edits create a new Draft rather than silently changing the published behavior.

The records, relationships and fields to which an allowed action applies. Permission to perform an action does not imply access to every record.

The live environment used for real company, customer and Provider operations. Production data and secrets must not be copied into non-production environments.

An isolated, commit-identified deployment used to review a proposed change without affecting Production. It uses non-production data, credentials, callbacks and access rules.

The qualified network and transaction layer through which Projects discover, engage and operate with specialized Providers.

The traceable origin of a value or output, including source record or file, source location where possible, extraction time, model or process and subsequent human correction.

A priced response to a defined request before award. A Provider Quote may become an accepted Proposal or commercial source, but it is not a Work Order or Invoice.

Short-form reference to The Design Registry. Use this as the operating system identity after initial formal mention.

The belief that every professionally designed Project deserves a permanent record, and that software should respect the craft by reducing complexity, choosing clarity and keeping the work—not the technology—at the centre.

A meaningful moment in a Registry lifecycle—Beginning, Building, Delivering or Remembering—where context, owner, date and evidence should be preserved.

A coherent part of a Project story that groups related decisions, products, documents, conversations, milestones or outcomes without replacing the underlying canonical records.

Permission-aware assistance that helps people find, understand and preserve Project knowledge through extraction, summaries, recommendations and exception signals while leaving consequential authority with an authorized person.

The decision question used across the company: does this make excellent design easier to trust, understand and deliver?

The canonical Provider Category for expected-receipt planning, receiving, condition evidence, storage locations, inventory movements and release readiness.

An authorized internal administrator who manages network governance, applications, matchmaking, operations or market-level work.

The accountable Teammate responsible for maintaining a Client, Designer Studio, Provider or other network relationship. It is descriptive ownership, not Workspace ownership or permission authority.

The Registry is the permanent record that grows from first conversation through installation evidence and beyond. It is the product-level expression of memory, accountability and provenance.

A time-bounded reservation of a Resource against Project or operational work, including availability, conflicts, capacity and release state.

A governed reversal of all or part of a collected Payment, retaining reason, authority, processor state and reconciliation history.

The evidence-backed record of an item arriving at a facility, including quantity, condition, photographs, discrepancies and storage location.

A permission-scoped, source-aware projection of authorized canonical records with defined metrics, dimensions, time zone, filters and as-of time.

A schedulable person, team, crew, vehicle, room, receiving dock, equipment asset or capacity unit.

A reusable capability such as Overview, Activity, Notes, Files, Tasks, Communication, Matchmaking, Proposals or History projected onto supported record types through configuration and permission.

A customer-facing name describing a teammate’s function. It does not independently grant authority; permissions do.

A time-bounded proof that the current User recently completed an approved sign-in or step-up challenge before a sensitive action.

Database policies that enforce which rows an authenticated request may access, providing a non-optional boundary beneath the interface.

The controlled comparison of Registry records with an external system to identify, explain and resolve missing, duplicate or conflicting states without silently overwriting canonical data.

The governed library of shared tokens, fields, selectors, patterns, formatters and accessibility contracts reused across every Registry, Designer, Provider, Client and public experience.

The canonical profile composition used by Client, Designer Studio, Provider, User and Workspace Profiles: Profile Header, permission-aware Record Tabs, configurable Overview Cards and shared Activity, Projects, Files, Tasks, Communication and History modules. Settings may link to profile editing but does not create a separate profile design.

A governed geographic area in which a Designer Studio or Provider is willing and qualified to work, optionally constrained by service, travel, distance, market or capacity rules.

A canonical location within a Project property, organized in an optional floor, area, room or zone hierarchy and referenced by plans, Items, tasks, decisions and installation work.

A named position within a Pipeline version. It may have a colour, requirements, service level, automations and a stable system or reporting mapping.

A protected internal status used for security, provisioning, analytics and cross-workspace consistency even when display labels are customized.

The confirmed financial result after payment processing, fees, refunds, adjustments and payouts are reconciled to the platform’s commercial records and accounting ledger.

A Designer-facing view of Decorating Items grouped for sourcing, comparison, Client presentation and approval. It is a view of canonical Items, not a separate spreadsheet-like data store.

A tracked movement of one or more purchased Items from an origin toward a receiving facility or destination, with carrier, tracking, expected timing, events and exceptions.

The current facility, zone, aisle, rack, bay, shelf, pallet or other Provider-defined position of a received Item, preserved through location history.

A sent or received text message with phone participants, consent purpose, delivery status and linked Conversation context.

A named, owner-scoped configuration of an authorized collection’s filters, sort, columns, grouping and density. It stores presentation settings, not a separate copy of the records.

The designated authoritative source for a decision, record or specification. A source of truth has an owner, version and defined consumers.

The production-like environment used to rehearse migrations, permissions, integrations and complete workflows before Production promotion.

A traceable attempt to exchange authorized data with an external system, including direction, cursor or scope, result, retries, errors and reconciliation state.

A physical Design Registry presence supporting Designer work, Client meetings, product discovery, Provider activity, events and local network density.

A field allowing exactly one stable option key, rendered as a native select, searchable combobox or radio group according to list size and decision importance.

A stable machine-readable identity for a state, priority or condition that remains unchanged when its display label or colour is customized.

A durable link from an AI-derived statement or value to the permitted source evidence supporting it, with enough context for a reviewer to verify the claim.

A Designer-first operating network and permanent record for independent design work, built so professionally designed Projects are preserved long after delivery as a connected story of decisions, products, revisions, installations, conversations and outcomes. The Registry is governed by the Brand Philosophy, Marketing & Experience Guide as the shared reasoning standard for the company.

The small full-stop mark in The Design Registry identity. It represents confidence, completion, precision and the permanent record created when the work is made clear.

The product-facing term for a User participating in a Workspace through a current or invited Membership. Teammate does not describe an external Project participant unless that person also belongs to the Workspace.

A Workspace-defined group of Teammates used for organization, assignment, scheduling and optional Access Role inheritance. A Team is not a separate Workspace.

A discrete unit of work with an owner, collaborators, state, priority, due timing, linked record and optional completion evidence.

The one accountable User or eligible operational assignee responsible for completing a Task. Collaborators may assist but do not replace accountability.

A permitted User who contributes to or follows a Task without becoming its accountable Owner.

A typed relationship connecting a Task to its governing Project, Project Phase, Pipeline Record, Client, Provider Job, Work Order, Item or other supported canonical record.

A text representation of recorded or live communication with source, timestamps, speaker attribution, confidence, correction and access controls. It does not replace the original recording when that recording is retained.

A user-attributed duration recorded against a Project, phase, task or Work Order for capacity, cost, billing and performance analysis.

The portion of transaction value retained by The Design Registry for a defined marketplace or service flow, calculated only on the contractually approved base.

A scheduled occurrence stored as an absolute instant plus its IANA timezone and original local representation.

One authenticated person with a stable global identity. A User may hold Memberships in several Workspaces and must not be duplicated for each organization.

The person-owned profile that follows one global User across Workspaces, containing personal identity, accessibility, regional, Calendar and notification preferences while excluding Workspace-specific Membership data.

The Workspace communication surface that projects authorized email, SMS, calling and in-app Conversations into one triage and collaboration experience without replacing channel-specific records.

A Provider category that supplies furniture, fixtures, materials or other purchasable products. Vendor is not a synonym for every Provider.

The canonical Provider Category for businesses that source, sell or supply furniture, fixtures, equipment, finishes, materials or other purchasable products.

The canonical Provider Category for scheduled pickup, route and crew coordination, careful delivery, placement, proof and day-of exception handling. Use title case for the Category; use white-glove delivery for the general service.

The secure operating environment belonging to one organization or Registry team. It owns its users, settings, branding, records, templates and operational data.

The accountable user with authority to manage a Workspace profile, membership, core settings and other owner-reserved controls.

The Workspace-owned organization profile containing identity, operations, qualification, branding, integrations and visibility, extended by Workspace type and Provider Category.

An Entity with its own authenticated Workspace, users, profile, workflows and permission-scoped operating experience.

A defined portion of Project scope prepared for Provider pricing, assignment and execution, including relevant items, dates, locations, requirements and documents.

The awarded and authorized record that converts accepted Provider scope into operational work, evidence, invoicing and completion obligations.

A Provider workflow for scheduled handling, route or crew visibility, delivery, placement, proof, exceptions and installation-day coordination.

A signed external event delivered to a controlled endpoint and stored or deduplicated before domain processing.