Less navigation
Group the product by jobs, not every record type. Contextual views reveal the detail.
Company system / Design
Brand governs expression. Product governs the application. Website governs how the public story, proof and acquisition experience bring both systems together.
Design / Product
The visual source of truth for the next Design Registry interface: shared components, quieter navigation, standardized forms and a profile system designed around what each participant needs to understand and do next.
Group the product by jobs, not every record type. Contextual views reveal the detail.
Headers, tabs, activity, files, tasks and communication behave consistently.
Profiles explain state, next work and risk before presenting the complete record.
Workspace identity can lead while interaction patterns remain governed and shared.
Product foundations
Tokens make the interface consistent without making it rigid. They define the permitted visual vocabulary, while density, audience and workspace branding remain controlled configuration.
Body / 14 — operational copy stays direct and readable.
LABEL / 11 · 0.08EM TRACKINGLevel 01Boundaries and selected state
Level 02Menus, drawers and sticky bars
Level 03Modals and blocking decisions
Universal component contract
A reusable component is more than a styled rectangle. It owns anatomy, state, permissions, data behavior, accessibility, responsiveness, content rules and instrumentation.
2Choose the teammate accountable for the Project.
3Selection savedIdentityVisible label, accessible name and purpose
ControlTrigger, value, affordance and keyboard behavior
GuidanceHelper, validation, source and consequence
StateLoading, empty, error, disabled, read-only and restricted
EventsCreated, changed, failed and completed activity
Tab moves between controls; arrows move within composite controls; Escape closes temporary surfaces; focus returns to its origin.
Colour never acts alone. Text, iconography and programmatic state carry the same meaning.
Permissions determine whether records, fields and actions exist before the interface is rendered.
Dense tables project into prioritized mobile rows; important actions and status remain available.
Complete review register
This is the working inventory for component-by-component review. “Concept designed” means a visual direction appears below. “Dedicated pass” means the component still needs its full anatomy, states, responsive behavior and usage rules designed.
Shared component library
Components keep the same anatomy, interaction, validation and accessibility contract across Admin, Designer, Provider and Client experiences. Audience, permissions, density and content may change; the component does not fork.
One primary action per region. Destructive and irreversible actions never use the same visual treatment as ordinary progress.
Every field keeps a visible label, optional helper or error message and an explicit state. Formatting is presentational; canonical values remain structured.
Search, selection, empty, loading and restricted states are shared. Options are alphabetized unless business priority or chronology requires another documented order.
Atelier NorthDesigner Studio
Atelier MaisonDesigner Studio
Northline StorageProvider
Navigation shows location and information hierarchy. A tab changes the current record view; a filter changes the result set; neither is used as a decorative label.
Colour reinforces meaning but never carries it alone. Status labels use canonical state language and are distinct from categories, tags and priorities.
12 of 18 requirements complete
Cards group one coherent question. They do not become arbitrary containers or nested dashboards. The card title, action, state and empty behavior are part of its contract.
Eleanor WestFull-service client
Issued design package · 12.4 MB
Atelier NorthDesigner Studio · Toronto
PreferredOne governed grid provides selection, sort, filter, column, bulk action, export, density and saved-view behavior. Cells use shared formatters and never invent local controls.
Operational components connect action, owner, due state and source record. Notes and messages remain distinct; formal approval is never reduced to a comment.
Eleanor West approved revision 03.
Brad Mitchell · Client decision · 10:42 a.m.Kitchen Elevations — Rev 03.pdf
Maya Chen · Internal · YesterdayReview revision 03 before the millwork package is issued.
Feedback states explain what happened, what was saved, what is affected and what the person can do next. “Coming soon” is visibly disabled and never masquerades as active.
3 fields were suggested by AIReview the highlighted values before saving.
Delivery date is at riskThe carrier has not confirmed the revised window.
Unable to save changesYour entries are preserved. Try again or contact support.
Project createdProject Rosedale is ready.
Task archivedThis action can be undone.
Create a proposal from approved Project scope or invite a Provider to respond.
Learn how proposals work →Use a modal for a focused finite action, a drawer for contextual detail that benefits from the underlying page, and a full page for complex or deeply linkable work.
Detailed collaboration patterns
Notes, Tasks and Builders need enough depth to replace disconnected messages, spreadsheets and one-off setup screens. These concepts establish their information hierarchy and interaction model.
Brad MitchellToday at 10:42 a.m. · Edited
Client approved the stone direction. Confirm slab availability before the millwork package is released.
Confirm the selected Calacatta Viola slabs remain held and upload written supplier confirmation.
Release millwork packageBlocked by this Task
Application stagesDrag to reorder. Select a stage to configure its rules.
SubmittedNo blocking issues
Qualification review6 required fields · 2 automations
Site assessmentNo blocking issues
ApprovedNo blocking issues
STAGE SETTINGSQualification review
✉Send review received emailNotification template · Provider
✓Create qualification TaskDue in 2 business days
Operational component atlas
The same product language must carry the work from an email or calendar event through specification, purchasing, receiving, delivery, commercial approval and payment. These larger compositions show how the primitives operate together.
Email, SMS, calls and in-app messaging share one conversation frame while preserving channel-specific controls, consent and delivery state.
Eleanor WestKitchen elevations · Project Rosedale
We love the stone direction. Could we see the warmer hardware option before approving the kitchen?
@Olivia please add the aged brass option to the presentation before tomorrow.
Plans, images, spreadsheets, invoices and condition evidence
Kitchen elevations R03.pdf12.4 MB · Processing
Slab condition.jpg4.8 MB · Ready
Item import.xlsx820 KB · Mapping required
$67,440 specified$19,060 remaining
Calacatta Viola slabMaterial · ST-204
ApprovedCiot2$8,600$17,200Sep 14Aged brass pull setHardware · HW-118
ReviewDevol24$86$2,064Oct 02Opal globe pendantLighting · LT-072
OrderedAllied Maker3$1,450$4,350Nov 18Purchase Order PO-1042 · Project Glebe
Marcus Allen · Crew ATruck 04 · 18 Items · ETA 10:16 a.m.
DELIVERY WINDOW10:00 a.m.–12:00 p.m.
DESTINATION82 Roxborough St W
INSTALL CHECKLIST0 of 18 complete
Matching, Offers and commercial documents share Project scope, counterparties and history while preserving distinct commitments.
Northline StorageReceiving, Warehouse & Storage
93%Project Rosedale receiving48 Items · Sep 14–Nov 30
AwaitingWO-2026-0148Northline Storage
ActiveComplete shared profile system
They use the same Profile Header, Record Tabs, Overview Card registry, Activity, Projects, Files, Tasks, Communication and History patterns as every other profile. Their identity, permissions and Overview modules differ; the architecture does not.
USERBrad MitchellFounder · The Design Registry · Active
WORKSPACEThe Design RegistryRegistry Administration · Ottawa · Active
Application shell
The left rail becomes a stable operating spine. Primary navigation is reduced to eight jobs; audience-specific access hides entire jobs when unavailable. The workspace switcher and personal account remain persistent without competing with active work.
Here is what needs attention across your active Projects.
Shared form system
Forms use a consistent width, header, section rhythm, validation pattern and footer. Long forms disclose sections progressively. Address, currency, phone, select, multi-select and date fields use canonical shared controls.
Start with the essentials. You can complete the Project profile after creation.
Paste an intake form, proposal or client email and we will suggest these fields for review.
Placeholders never replace a field’s identity.
Currency, phone, postal code and dates display consistently while preserving canonical values.
Explain the exact problem beside the field and summarize it before submit.
Extracted values carry source and confidence; consequential values remain reviewable.
Shared entity profiles
Every profile begins with identity, relationship state and next action. Shared tabs stay familiar. Overview cards change by entity type: Clients centre active decisions and preferences, Designers centre capacity and network participation, and Providers centre operational readiness and awarded work.
The internal profile connects contact preferences, addresses, Project Opportunities, active Projects, decisions and communications. The Client-facing experience remains intentionally curated.
Toronto, Ontario · Client since March 2026
Full-service residential client
Requested changes were uploaded yesterday by Atelier North.
NEXT MILESTONEDesign Package approvedSeptember 18
PROJECT TEAMAtelier North3 active Providers
OPEN DECISIONS2 waitingOldest: 3 days
Eleanor replied yesterday at 4:18 p.m.
Approved design fees · $24,250 paid
The Designer Studio profile shows who they are, what they are best suited for, whether they have capacity, and how they are performing across Registry Projects—without erasing their independent brand.
Toronto, Ontario · Registry member since January 2026
Residential design studio specializing in full-home renovations, custom millwork and material-led interiors.
Next Project startOctober 2026
The shared Provider profile establishes trust and qualification. Its category module then surfaces the operational facts that matter—in this example, expected receipts, condition evidence, Storage Locations and releases.
Ottawa, Ontario · 24,000 sq. ft. facility
White-glove receiving, inspection, inventory and residential Project storage across the Ottawa region.
Receiving appointmentProject Rosedale · 10:30 a.m. · 8 itemsExpected
Condition reviewProject Glebe · Dining table · DR-284Action
Release for deliveryProject Elgin · 2:00 p.m. · 14 itemsReady
InsuranceValid to Mar 2027
Service area75 km
Photo evidenceRequired
Barcode scanningEnabled
Design and implementation sequence
The sequence protects the build-once architecture. Foundational primitives become stable before complex Builders and Provider-specific operations depend on them.
Tokens, shell, actions, form fields, selection, feedback, overlays and responsive rules
Profiles, Tasks, Notes, activity, files, Enterprise Data Grid and Calendar
Pipeline, Form, Automation, Notification, Project Template and Permission Builders
Items, Categories, Budgets, Purchase Orders, receiving, storage, delivery and installation
Matchmaking, Offers, Proposals, Work Orders, Invoices, payments and signatures
AI assistance, density personalization, advanced analytics and approved workspace branding
Implementation contract
These mockups should become a reusable product system, not three independent pages.
Identity, Entity type, relationship state, metadata and permission-aware actions
Overview, Activity, Projects, Files, Tasks, Communication and History
Configurable cards by Entity type, Provider Category and audience
Canonical Client, Designer, Provider, Project, User and Team selection
Standard sections, field controls, validation, draft state and action footer
The server determines records, cards, fields and actions before rendering