N.°01 — Norma
Norma
Your studio's product memory.
02 What it is
A practice that remembers.
Norma is a product and materials specialist for architecture and design studios. It starts from the living project record — the FF&E schedule, spec book, product list, or procurement tracker — and helps maintain it as the project evolves. Every source, correction, approval, and decision becomes part of a private studio library.
03 Why it exists
The most valuable data in a studio is not the generic product catalog. It is the studio's own history with that catalog.
Canoa proved that product data matters, but also that pre-ingesting the whole product universe is unrealistic. Architecture Studio proved that Claude can be structured with orchestration, skills, rules, and tools. Norma is the next step: memory and agency around the actual project documents where product decisions live.
i.
Canoa's lesson
A design tool with product data is powerful, but product data arrives through messy project work: quotes, PDFs, schedules, vendor links, substitutions, private pricing, and decisions.
ii.
Architecture Studio's lesson
Useful AI for the built environment needs orchestration, tools, source expectations, and review rules. But workflow structure without durable memory still starts too much from zero.
iii.
Norma's bet
The studio's own project history is the moat. Norma turns each schedule, correction, source, and approval into memory the next project can reuse.
04 How it works
01
Joins the project record
Norma works around the schedule, spec book, product list, or tracker your studio already uses. Those documents stay in existing tools; Norma gives Claude a private corpus of product memory, sources, URLs, parsed PDFs, vendor context, and prior decisions to reason against them.
02
Maintains the work
It identifies missing fields, traces products back to sources, fills clean updates, flags uncertainty for review, and checks for stale pricing, lead times, links, and substitutions.
03
Prepares outputs for review
Norma can prepare rows, notes, source refreshes, comparisons, and export candidates for a schedule or spec book. Where a workflow supports writing or projection, those changes should be permissioned, traceable, and tied to receipts.
04
Builds the library
Every approved fact, correction, vendor note, source, preference, and decision becomes part of the studio's private product memory.
05 What it does
Parse
Reads product artifacts
Quotes, PDFs, vendor pages, catalogs, cutsheets, EPDs, spreadsheets, and spec books become source-backed product records.
Clean
Normalizes messy schedules
Norma maps inconsistent columns and project-specific structures into useful, reviewable updates without pretending every studio uses the same schema.
Enrich
Fills what is missing
Dimensions, materials, finishes, certifications, lead times, links, and notes are added with source and date attached.
Audit
Catches drift
Vendor pages, pricing, lead times, availability, and broken links can be re-checked so stale information surfaces before client review.
Stage
Prepares document-ready output
Norma can assemble rows, notes, comparisons, source refreshes, and export candidates. In Claude workflows, the studio can use that corpus to make decisions, fetch URLs, parse PDFs, build an XLS schedule, update a Google Sheet, or draft a spec-book section through the tools it already uses.
Remember
Carries decisions forward
Approved products, rejected options, preferred vendors, confirmed finishes, and project conventions become reusable studio knowledge.
06 Memory layers
| Layer | What it contains | Privacy |
|---|---|---|
| Studio memory | Specs, quotes, pricing, corrections, preferences, vendor history, approvals, substitutions | Private to the studio |
| Review state | Verified, review, stale, missing fields, duplicate hints, import receipts, permission history | Visible to the studio |
| Shared product facts | Manufacturer specs, public SKUs, dimensions, finishes, certifications, source URLs | Pooled only when redacted |
The boundary is the product. Public facts can make the baseline better. Review state keeps the work accountable. Existing tools remain the surface. Studio memory preserves the practice.
07 Built for
01
Interior designers
FF&E schedules and spec books that stay sourced, current, and reusable across projects.
02
Architects
Product, material, finish, and fixture decisions with provenance instead of orphaned PDFs and stale spreadsheet rows.
03
Small studios
The product librarian, specs manager, procurement analyst, and data steward most teams cannot hire full time.
04
Product-heavy teams
Studios whose advantage comes from how they specify, source, substitute, approve, and remember.
08 Research step
After Canoa and Architecture Studio.
Canoa asked whether design tools could understand real products. Architecture Studio asked whether Claude could be structured for professional workflows. Norma asks what happens when the project record becomes private, cited, askable studio memory that can act.
i.
Not a universal schema
The built environment's messy data is valuable because it exposes how different practices actually work. Norma builds contextual structure around the task.
ii.
Not another search box
The goal is not to make the studio search better. The goal is for the project record to remember what the studio already learned.
iii.
Not just automation
Automation saves time once. Memory compounds every time the studio specifies, corrects, approves, or rejects something.
iv.
Agency with provenance
Norma can propose, check, and maintain updates, but the record stays reviewable because every fact carries source, date, context, and write history.
Build a practice that remembers.
Norma turns the living project record into private studio memory.
Visit norma.llc →