Basis · a MaterialGraph consumer product
Basis is a standalone specification product for architects, powered by MaterialGraph. Give it a brief, a zone, a selected product, or a substitution problem; it returns eligible product sets, readiness status, system gaps, review tasks, and project-ready exports.
MaterialGraph provides the canonical product record. Basis turns that record into workflow.
The Warehouse Hotel
A 45-room adaptive reuse hotel becomes searchable zones, eligible product sets, readiness checks, system gaps, review tasks, and sample-ready outputs. The product truth still comes from MaterialGraph.
45
rooms
7
zones
$180
FF&E / sqft
Basis project workspace
hotel-austin-warehouse · hospitality profile
Zones
Search generated from project context
Eligible candidates
searching
Selected candidate
18 sources · 42 fields · 4 documents
88
ready
System completion
Draft Division 09 section
ready
Readiness report
12 checks
Sample request plan
6 items
Why it matters
Architects spend hours cross-referencing PDFs, manually checking compliance, and assembling specifications from scattered spreadsheets. A single substitution request can derail a day.
Basis turns that into a structured workflow. It consumes MaterialGraph records, applies project and profile constraints, completes product systems, exposes unknowns, and assembles outputs a project team can review and act on.
The distinction
A consumer surface, not a second product graph.
Basis does not own product truth. It reads the graph, calls structured checks where needed, and keeps curation, readiness, and project review separate from the canonical record.
What Basis does
Each workflow is a real task architects do today manually. Basis structures them into repeatable, source-backed processes without collapsing review, compliance, and product truth into one opaque answer.
Natural-language product search grounded in MaterialGraph records, project context, budget, availability, readiness gates, and explicit missing-data flags.
Example prompt
“Floor tile for a boutique hotel lobby in Dallas. Warm tone. DCOF 0.42+. Class A interior finish. $25-35/sqft.”
Start with one chosen product. Basis uses graph relationships to identify the surrounding assembly, accessories, documents, and unresolved review tasks.
Example prompt
“We want this Italian porcelain in the bathroom. What else do we need?”
Run an existing selection set through profile-specific checks. Basis reports pass, fail, and unknown states without pretending missing source is a decision.
Example prompt
“Which selections are hurting our LEED target? Which fail ADA or fire?”
When a product is unavailable, over budget, or under-sourced, Basis finds candidates with comparable function, character, readiness, and constraints for review.
Example prompt
“The corridor carpet is out of stock. What can we swap without breaking budget or compliance?”
Once selections are reviewed, Basis assembles graph-backed exports: source summaries, mapped attributes, budget notes, and draft section output.
Example prompt
“Generate the Division 09 spec for the guest room finishes.”
Demo mode for decomposing a hospitality brief into zones, candidate product sets, review queues, readiness status, and sample-ready actions.
Example prompt
“45-room boutique hotel, Austin TX, adaptive reuse, LEED Silver, $180/sqft FF&E.”
How it works
Externally, one coherent product. Internally, Basis resolves project context, queries the graph, calls structured rule services, and produces reviewable artifacts instead of improvising a specification.
Basis
Standalone specification workflow product for architects
Project context
Zone, jurisdiction, occupancy, budget, certification, and design intent
MaterialGraph
Canonical product records, source, relationships, profiles, and export mappings
Rules services
Structured eligibility, sustainability, and project-readiness checks called where needed
Review gates
Pass, fail, unknown, blocked, and needs-human-review states
Downstream actions
Specification exports, sample requests, alternates, and project artifacts
What comes out
The flywheel
Better product data makes more products eligible for Basis. Eligible products appear in more project workflows. More workflows produce sample requests and specification signal. Brands get sharper pressure to fix missing data. Cycle repeats.
The dependency
If the canonical product record is weak, Basis becomes a polished uncertainty layer. If it’s trustworthy, Basis becomes the first consumer product that makes the value of that trust obvious to architects.
MaterialGraph record
Canonical product truth
Blocks, attributes, source, source quality, product relationships, profiles, and export mappings stay governed by MaterialGraph.
Basis readiness
Consumer workflow eligibility
Basis uses the record to decide whether a product can enter compliance-checked, system-complete, or sample-ready workflows.