Chandra Jewellery ERP · Discovery

Discovery Health

Every number explains itself — click any tile to see exactly why.

2 conflicts and 5 critical questions block Quotation ApprovalRequirement R-102 conflicts with R-118 on who may approve · 5 high-priority questions still unanswered by Sales Head.

72%

Knowledge completeness

▲ 6

64%

Overall confidence

▲ 3

14

Open questions · 5 critical

▲ 4

5

Pending reviews

—

Feature readiness

weights from methodology config

Feature	Questions	Reviews	Readiness
Quotation ApprovalM-Sales · Priya (PM)	5 open	2 of 3	Not ready
Design ReviewM-Design · Chandra	0 open	3 of 3	Ready
Customer Inquiry IntakeM-Sales · Priya (PM)	4 open	Not sent	In progress
Order CreationM-Orders · Chandra	3 open	Not sent	In progress
Karigar Job AllocationM-Production · Ravi	Not started	Not sent	Capturing

Why not 100%?

✕
2 unresolved conflicts
R-102 ↔ R-118 approver roles · R-131 ↔ POL-3 discount rule
✕
5 critical questions open
Awaiting Sales Head — sent 3 days ago
◐
3 assumptions unconfirmed
ASM-04, ASM-07, ASM-09
◐
Notifications 40% specified
6 of 15 notifications have exact message text
✓
No governance violations
Last checked at synthesis #9

Recent activity

Rajesh (Sales Head) answered 6 questionsvia magic link · 2h ago
Synthesis #9 — 4 changed, 2 new, 2 conflictsclaude -p · sonnet · 3m 12s · yesterday
RAW-089 Meeting transcript capturedCustomer visit — Shantivijay · yesterday
Meera requested changes on R-104review · 2 days ago

Layer 1 · Raw knowledge — append-only

Discovery Inbox

Capture everything. Nothing here changes the spec until you synthesize.

Type: Any ▾Author ▾Feature ▾Date range ▾

Sorted: newest first

ID	Capture	Type	Linked to	Status	When
RAW-092	Rajesh: approved quote can change only if customer changes design"…in that case old approval is invalid, price must be reworked…"	WhatsApp	Quotation Approval	New	2h ago
RAW-091	Thought: karigar app must work offline in workshop basementNetwork is patchy near the casting unit	Thought	Karigar Job Allocation	New	5h ago
RAW-089	Customer visit transcript — Shantivijay Jewels (42 min)Design approval flow, gold rate lock, hallmarking expectations…	Transcript	3 features	New	Yesterday
RAW-088	Email from Meera: GST invoice numbering must be sequential per FYFwd: CA confirmation on invoice series rules	Email	Order Creation	Filed	2d ago
RAW-087	Old ERP screenshot — quotation screen fieldsquotation-fields.png · existing requirement reference	Document	Quotation Approval	Synthesized	4d ago
RAW-086	Meeting note: weekly review with Ravi on production flowWax → casting → filing → polish → QC → hallmark → dispatch	Meeting	M-Production	Synthesized	5d ago

Showing 6 of 34 · Load more

Layer 3 · Canonical source of truth

Requirements

One canonical store. Every view, prototype and package derives from here.

Feature: Quotation Approval ✕Priority ▾Owner ▾

ID	Requirement	Completeness	Confidence	State	Trace
R-102	Modification of an approved quotationQuotation Approval · P1 · owner Priya	72%	64%	In review	4 src · 6 Q · 2 scr
R-104	Quotation approval workflow & statesQuotation Approval · P1 · owner Priya	88%	81%	Changes requested	6 src · 9 Q · 3 scr
R-118	Approval permissions by roleQuotation Approval · P1 · owner Chandra · conflicts with R-102	60%	45%	Conflict	3 src · 4 Q · 1 scr
R-121	Quotation validity & gold-rate lockQuotation Approval · P2 · owner Priya	95%	88%	Approved v4	5 src · 7 Q · 2 scr
R-131	Discount limits & escalationQuotation Approval · P2 · owner Priya · conflicts with POL-3	55%	58%	Conflict	2 src · 3 Q · 1 scr

Requirements / Quotation Approval

R-102 Modification of an approved quotation

v3 · owner Priya (PM) · In review 1 conflict

Why · Business objective

100%

Customers frequently change designs after quotation approval. Without a controlled modification flow, sales re-quote informally over WhatsApp, losing price control and approval history. This requirement defines when and how an approved quotation may be modified.

PersonasSales Executive · Sales Head · Customer · Accounts

Workflow

90%

Sales Executive opens an Approved quotation and requests modification, citing reason = customer design change (only permitted reason — see rules).
System snapshots the approved version; quotation returns to Draft (rev n+1); previous approval is marked invalidated.
Design reference is updated; pricing is recalculated (gold rate, making charges, stones) per CALC-2.
Revised quotation re-enters the approval flow (R-104); Sales Head must re-approve.
Customer is notified of the revised quotation (N-07).

Business rules

70%

✓
BR-1 — Modification allowed only when the customer changes the design. RAW-092ANS-14
✓
BR-2 — Prior approval is invalidated; approval history retained. ANS-14
✕
BR-3 (conflict) — Who may trigger modification: R-102 says Sales Executive; R-118 says only Sales Head. Unresolved
◐
BR-4 (open) — "What constitutes a design change?" — awaiting Q-233 answer.

Acceptance criteria

3 of 6 sections covered

AC-1 · happy path
GIVEN an Approved quotation Q-2041
WHEN Sales requests modification with reason "customer design change"
THEN Q-2041 becomes Draft rev 2, approval marked invalidated, audit entry created

AC-2 · permission
GIVEN a user without modify permission
WHEN they request modification
THEN the action is unavailable and no state change occurs

Missing: validation, error, notification-failure, timeout criteria — flagged by AI review.

Scores

72%

Complete

64%

Confidence

Objective 100 · Workflow 90 · Rules 70 · Validation 80
Permissions 60 · Notifications 40 · Acceptance 30

Low confidence: stakeholder disagreement (BR-3)

Sources

backward trace

RAW-092 · WhatsApp RajeshRAW-089 · Customer transcriptANS-14 · Rajesh answerC-27 · Meera commentDEC-06 · Re-approval decision

Trace

❓ 6 questions · 2 open (Q-233, Q-234)

🖥 Screens: PT-3/s-quote-modifyPT-3/s-quote-detail

🔔 Notifications: N-07 revised-quote

🔗 Depends on R-104 · conflicts R-118

🧮 Uses CALC-2 · Quote pricing

Comments

1 open

MR

Meera · Accountson "pricing is recalculated"

If gold rate moved >2% since approval, revised quote must use the new rate — old rate lock should not carry over.

History

v3 — BR-2 addedfrom accepted answer ANS-14 · 2d ago
v2 — workflow expandedsynthesis #8 proposal accepted · 6d ago
v1 — createdfrom RAW-067 (meeting note) · 12d ago

Layer 2 · Proposals — you decide what becomes canonical

Synthesis #9 — Triage

Scope: Quotation Approval · 12 captures + 6 accepted answers read · claude -p · sonnet · 3m 12s

Change summary4 requirements changed · 2 new requirements · 2 conflicts detected · 3 questions resolved · 5 new questions · 1 assumption raised · 2 prototype screens affected. Nothing has been applied — accept below.

3 triaged · 6 pending

CHANGED

PROP-58 · R-102 — add re-approval & notification steps

sources: RAW-092, ANS-14

Approved quotations cannot be modified.

An approved quotation may be modified only when the customer changes the design. The prior approval is invalidated (history retained), pricing is recalculated per CALC-2, Sales Head re-approves, and the customer is notified (N-07).

WhyRajesh's WhatsApp (RAW-092) and his questionnaire answer (ANS-14) both state modification is allowed on design change and requires rework of price and approval. This contradicts the current text, so an update is proposed rather than a new requirement.

CONFLICT

CONF-11 · Who may approve a revised quotation?

R-102 ↔ R-118

R-102 · from ANS-14 (Rajesh, Sales Head)

"Sales Head must re-approve revised quotations."

R-118 · from RAW-067 (kickoff meeting)

"Only managers approve quotations; sales executives can approve up to ₹50,000."

Why flaggedBoth statements govern the same approval action with different role boundaries. The engine never chooses — resolve by answering Q-235 (sent to Business Owner) or record a decision.

NEW

PROP-60 · R-146 — Gold-rate revalidation on quote revision

sources: C-27, RAW-088

When a quotation is revised after approval, the gold rate must be re-fetched; if it moved more than the locked tolerance (ASM-09: ±2%, unconfirmed), the revised quote uses the current rate and the customer is informed of the price difference.

WhyMeera's comment (C-27) introduces a rule not present in any requirement. Raised as a NEW requirement rather than an edit because R-102 governs flow, not pricing policy. Assumption ASM-09 raised for the tolerance value.

DUPLICATE?

DUP-4 · R-121 ↔ R-133 may overlap on validity period

Both define how long a quotation stays valid. Human resolution required.

In & out · reverse-synthesis into proposals

Artefact Bridge

Bring an existing document/prototype in, or send one out to edit in Claude Code and reconcile when you're done.

Nothing overwrites your spec directly.An imported or returned artefact is read into proposals (reverse-synthesis, claude -p) and you triage them into canonical — so the source of truth never silently diverges.

Import / adopt an existing artefact

bootstrap

Built a PRD + prototype in another Claude Code session? Paste its link (or upload) — the engine reverse-synthesizes it into requirement proposals and registers the prototype with screen ↔ requirement links.

Document / prototype link

Last import · adoption preview

chandra-quotation.html → 11 requirement proposals · 6 screens

✅ 9 requirements matched existing (merge proposals)

🆕 2 new requirements proposed ← doc §Pricing

⚠ 1 orphan screen — "Bulk discount" has no justifying requirement

◐ 3 components off the approved library (native selects) — flagged

TraceabilityThe imported file is stored verbatim as a source; every adopted requirement traces back to its exact location in it.

External round-trip

1 out for editing

1Checked outbaseline PT-3 v3

2Edited in Claude Codeoutside engine

3Brought backdiff ready

4Reconciledcanonical caught up

PT-3 · Quotation prototype

baseline v3 → returned v3-ext

Sent out to address Meera's 2 comments · returned 12 min ago · edited with Claude Code.

gold rate carried from original approval

gold rate re-fetched on revision; >2% move → new rate + customer notice (addresses C-27)

Reconcile mode

Reconcile canonical (recommended)Quick resolve only

◐
1 change → R-146 proposal
rate revalidation rule, ready to accept
✓
2 comments map to edits
C-27, C-31 → propose Addressed
✓
Anchors re-attached by req ID
0 orphaned comments

AuditWho edited, when, baseline → returned version, tool = Claude Code — recorded in the requirement history and trace graph. The round-trip never breaks traceability.

Clarify · Open questions register

Questions

Only questions that matter — every generated question states why it exists.

Feature: Quotation Approval ✕Category ▾Priority ▾Stakeholder ▾

ID	Question	Category	Priority	Owner / stakeholder	Status
Q-233	What exactly constitutes a "design change"?Stone swap? Size change? Engraving? Blocks BR-4 of R-102 · why: answer gates the only allowed modification reason	Rule	Critical	Priya→ Rajesh (Sales Head)	Sent 3d
Q-234	Is the customer notified when their old approval is invalidated?Follow-up generated from ANS-14 · affects N-07 timing	Notification	High	Priya→ Rajesh (Sales Head)	Sent 3d
Q-235	Who may approve a revised quotation — Sales Head only, or per value bands?Raised from conflict CONF-11 (R-102 ↔ R-118)	Permission	Critical	Chandra→ Business Owner	Open
Q-236	Should revised quotations expire faster than fresh ones?User-added by Priya	Business	Medium	Priya→ Rajesh (Sales Head)	Open
Q-228	Can a quotation be partially approved (some items only)?Answered: "No — all or nothing" → closed into R-104 v3	Workflow	High	PriyaRajesh · 2d ago	Answered

Clarify · Stakeholder answers

Questionnaires

Send magic links — stakeholders answer on any device, no login needed.

QNR-6 · Quotation approval clarifications

6 of 8 answered

RJ

Rajesh · stated name "Rajesh Mehta"

Sales Head · link sent 3d ago · last active 2h ago · expires in 4d

Latest answers to triage

ANS-14 ← Q-227 "Can sales modify an approved quotation?"

"Only if the customer changes the design. Then old approval is invalid, price reworked, and I approve again."

ANS-15 ← Q-228 "Partial approval?" · Accepted → R-104 v3

"No, all or nothing. Split into two quotations if needed."

Outstanding

QNR-7 · Production flowRavi (Workshop) · 5 questions	No response 6d
QNR-5 · Customer expectationsShantivijay Jewels · 4 questions	Complete

How magic links work

Each link opens exactly one questionnaire — no account, no app. The stakeholder states their name, answers by typing or device voice-to-text (only the transcript is stored), and can pause anytime. Links expire and are revocable. If adaptive follow-ups are ON, a clarifying question may appear right after an answer.

Preview · what the stakeholder sees (magic link, no login)

Stakeholder Portal

Chandra Jewellery ERP · 8 questions · ~10 min

Priya needs your input on Quotation Approval

Answer in your own words — type or use your phone's voice typing. You can pause anytime; your progress is saved.

Your name *

Question 7 of 8 · Rule

What exactly counts as a "design change" on an approved quotation?

For example: changing a stone, resizing, engraving text, metal colour…

Follow-up · because of your last answer

Is a resize beyond tolerance treated as a design change requiring re-approval?

6 of 8 answered

Clarify · Shared registers

Registers

Assumptions, risks, decisions, constraints and dependencies — nothing hides in prose.

ID	Assumption	Confidence	Affects	Status
ASM-09	Gold-rate lock tolerance is ±2%Raised at synthesis #9 from C-27 · author AI, source Meera	Low	R-146	Open
ASM-07	All approvals happen in-app (no offline paper approvals)author Priya · 8d ago	Medium	R-104 · R-118	Open
ASM-04	Quotation validity default is 7 daysConfirmed by Rajesh (ANS-11) → converted, source preserved	High	R-121	Converted → R-121

ID	Risk	P × I	Owner	Mitigation	Status
RSK-03	Sales may bypass system for urgent quotes via WhatsAppAffects R-102, R-104	High × High	Priya	Mobile quote flow ≤ 2 min; WhatsApp share of official PDF	Open
RSK-04	Gold-rate volatility disputes on revised quotesAffects R-146	Med × High	Meera	Explicit rate-difference note on revision (N-07)	Open

ID	Constraint	Type	Affects
CON-02	GST invoice numbers must be sequential per financial yearSource RAW-088 (CA email)	Regulatory	Order Creation
CON-03	BIS hallmarking mandatory before dispatchIncluded in every synthesis context bundle	Regulatory	M-Production
CON-04	Workshop devices are low-end Android phonesUX constraint — mobile flows must be lightweight	UX	Karigar Job Allocation

Validate · Formal review & approval

Reviews & Approvals

Disagreement is shown, never averaged away.

Quotation Approval — reviewer consensus

2 of 3 complete

Reviewer	Outcome	Completion	Confidence	Reviewed
Rajesh MehtaSales Head · required	Approved w/ comments	85%	80%	v3 · 2d ago
Meera ShahAccounts · required	Changes requested	70%	45%	v3 · 2d ago
ChandraBusiness Owner · final	Not reviewed	—	—	due in 2d

⚡ DisagreementMeera's confidence (45%) is far below Rajesh's (80%) — reason given: stakeholder disagreement on pricing rules (BR-3 / C-27). Resolve before final approval.

Approval matrix

✓
Sales Head — required
Rajesh · approved with comments
✕
Accounts — required
Meera · changes requested
◐
Operations — optional
not requested
✕
Business Owner — final
blocked until required approvals exist

Pending across project

Design Review specawaiting Chandra (final)	1 left
R-104 re-reviewstale — changed after Meera's review	stale
Prototype PT-3 reviewRajesh · due tomorrow	due

Derived artefact · regenerated from canonical

User Journeys & Process Maps

Business-readable flows — every step links to its requirements and screens.

Quotation to Order — happy path

in sync · canonical v-2026.08.29

1Customer InquiryR-090 · Sales

2Design CreationR-095 · Designer

3Design ReviewR-097 · Design Head

4Customer ApprovalR-099 · Customer

5Quotation & ApprovalR-104 · Sales Head

6Order CreationR-140 · Sales

Scenario"Customer rejects design after commercial approval" → flow branches at step 4: design returns to step 2 with rejection reason; quotation (if issued) is invalidated per R-102; customer notified via N-05. Walk it in the prototype →

Process map — Quotation Approval (actors & decisions)

Derived artefact · generated by claude -p on chandra-ui

Prototype Studio

PT-3 · Quotation Approval · desktop + mobile · pinned to canonical 2026-08-27

⚠ StaleCanonical moved on 2026-08-29 (R-102 v3). Regenerating shows a screen-level diff first; comment anchors are preserved by requirement ID.

Experience as: Sales ExecutiveSales HeadAccountsCEOCustomer

Persona gating hides what the role can't do

Quotation listjustifies: R-104 · STD-LIST golden path

Quotation detailjustifies: R-102, R-104, R-121

Modify approved quotejustifies: R-102 · reason modal + re-approval

Approval queue (Sales Head)justifies: R-104, R-118

Bulk discount screen⚠ orphan UI — no justifying requirement

AI UX review — advisory

◐
Missing empty state
Approval queue has no zero-pending state · GP-2 requires designed empties
◐
Reject flow lacks confirmation of consequences
Rejecting invalidates customer notification N-04 — say so before confirming
✓
All components from approved library
guardrail GG-1 satisfied · 0 violations

Design alternatives — approval UX

A · Inline approve from queuechosen · DEC-07

B · Full-page review before approvesafer, slower

C · Batch approvalrejected — audit risk

Approve · Readiness gate & business package

Sign-off — Quotation Approval

Only approved material enters the package. The gate explains exactly what blocks it.

Readiness gate

NOT READY — 4 blockers

✓
Business objective defined
✓
Stakeholders & personas identified
✓
Workflow complete, exceptions covered
✕
Business rules defined
BR-3 conflict unresolved (CONF-11) · BR-4 awaits Q-233
✓
Field validations defined
18 fields fully specified
✕
Permissions defined
approver bands undecided — Q-235 open
◐
Notifications defined
6 of 15 have exact message text
✓
Search / filter / sort / pagination addressed
STD-LIST golden path; 1 documented exception
✓
Exports addressed
quotation PDF layout specified; list → Excel
✕
Acceptance criteria complete
R-102 covers 3 of 6 mandatory categories
✕
Reviews completed
Meera: changes requested · Chandra (final): pending
✓
Prototype reviewed · governance satisfied

Package contents (v-preview)

Executive summary · Problem · Objectives · Stakeholders · Personas · Workflows · Business rules · Validations · Permissions · States · Exceptions · Notifications · Reports · Search/filter/sort · Exports · Acceptance criteria · Open questions · Assumptions · Risks · Decisions · Review comments · Approval status · Prototype · Sign-off sheet

Rendered as a self-contained HTML package in the house PRD style, from snapshot SNAP-10.

Snapshots

SNAP-9	After synthesis #92026-08-28 · 47 requirements
SNAP-8	Pre-review baseline2026-08-24 · 45 requirements

Shared language · used by every AI job

Glossary, Calculations & Policies

ID	Term	Definition	Used by
G-04	Quotation	Priced offer for a specific design, valid for a defined period; becomes an Order only on customer + commercial approval.	9 requirements
G-07	Design change	⚠ Definition pending — blocked by Q-233 (used in 4 requirements)	4 requirements
G-11	Karigar	Artisan/craftsman executing a production job stage (jewellery domain term, from domain pack).	6 requirements
G-13	Approval	A recorded, role-authorized confirmation that advances state; always auditable, never implicit.	14 requirements

ID	Policy	Referenced by	Status
POL-3	Discount authoritySales ≤5% · Sales Head ≤12% · beyond: Business Owner	R-131 · R-104	Conflict w/ R-131
POL-5	Customer approval evidenceEvery customer approval stores who/when/what version + shared artefact	R-099 · R-102	Active

Phase 5 · Reuse & cross-project learning

Knowledge Repository

Approved knowledge becomes reusable — labelled as known pattern vs project-specific, never blindly copied.

Standard Customer Approval Flow

pattern

Share artefact → customer decision (approve / reject / change) → evidence stored → state advance. Reused in 2 projects; traceable to Jewellery ERP R-099.

Jewellery domain pack

domain

Terminology (Karigar, hallmark, purity), gold-rate workflows, BIS constraints, 40-question jewellery question set, 3 golden paths. Attached to: Chandra Jewellery ERP.

Approvals template

pattern

Every approval feature must define: roles, bands, timeout, escalation, invalidation, notification, audit. Source: governance rule GR-7 (added in-app 2026-08-21).

Living layer · applies to every AI job & artefact

Governance

Rules · Guardrails · Golden Paths · Standards — data, not hardcoded prompts.

Scope: Effective at Quotation Approval ▾

ID	Rule	Scope	Applies during	Status
GR-1	Every requirement must have a clearly identified business ownerrationale: orphan requirements never get validated	Global	discovery · synthesis · review	Active
GR-7	Every approval feature must define timeout and escalation behaviouradded in-app 2026-08-21 — instantly part of AI context bundles	Project	questioning · synthesis · AI review	Active
GR-4	AI proposals must cite at least one sourceuncited output is rejected by the runtime	Global	all AI jobs	Active

ID	Guardrail	Severity	Last violation
GG-1	Never create a UI component outside the approved component libraryprototype generation is constrained to the chandra-ui registry	Blocking	never
GG-2	AI may never write to the canonical storeenforced in code; proposals only	Blocking	never
GG-3	No technical architecture in discovery outputsschemas/APIs flagged and stripped from packages	Needs approval	JOB-198 · flagged, blocked

ID	Golden path	Preferred for
GP-1	STD-LISTsearch + operator filters + sort + pagination + sensible defaults; exceptions must be stated in the requirement	every list experience
GP-2	Designed empty / loading / error statesevery screen ships all three	every generated screen
GP-4	Approval patternroles + bands + timeout + escalation + invalidation + notification + audit	approval features

ID	Standard	Value
GS-1	Date display	DD Mon YYYY (05 Sep 2026) everywhere user-facing
GS-2	Currency	₹ Indian grouping (1,15,943) · no decimals in quotes
GS-4	Component library	chandra-ui vX — registry of 70 approved components · simulate component change impact

Claude Code runtime · no API — local `claude -p` only

AI Console

Every AI action is a visible, priced, explainable job. Toggles keep cost in your control.

claude CLI connected · sonnet default

Job history

this week: 14 jobs · 41m runtime

Job	Capability	Model	Duration	Result
JOB-214	AI review · R-102claude -p --output-format json · 9 files in bundle	sonnet	1m 44s	Running
JOB-213	Synthesis #9 · Quotation Approval12 captures + 6 answers → 9 proposals · view input manifest	sonnet	3m 12s	9 proposals
JOB-212	Question generation · Order Creation18 generated, 3 filtered as duplicates of answered	haiku	41s	15 questions
JOB-209	Prototype generation · PT-3 mobileconstrained to chandra-ui registry · 0 guardrail violations	opus	11m 05s	6 screens
JOB-198	Package draft · Design Reviewguardrail GG-3: technical content flagged → blocked	sonnet	2m 20s	Blocked

Capability toggles

Synthesismanual only — never automatic

manual

Spec chatsonnet · session resume

Real-time follow-up questionsin-portal, after answers

Auto requirement suggestionson capture

AI reviewon demand per feature

Prototype generationopus · manual only

manual

Model per capability

Light (tags, dedupe) → haiku
Core (synthesis, questions, chat, review) → sonnet
Heavy (prototype, packages) → opus

Adapter: Claude Code CLI (only v1 adapter). Capability → model mapping is configuration; future adapters plug in without touching capability logic.

Discovery Health

Feature readiness

Why not 100%?

Recent activity

Discovery Inbox

Requirements

R-102 Modification of an approved quotation

Why · Business objective

Workflow

Business rules

Acceptance criteria

Scores

Sources

Trace

Comments

History

Synthesis #9 — Triage

PROP-58 · R-102 — add re-approval & notification steps

CONF-11 · Who may approve a revised quotation?

PROP-60 · R-146 — Gold-rate revalidation on quote revision

DUP-4 · R-121 ↔ R-133 may overlap on validity period

Artefact Bridge

Import / adopt an existing artefact

External round-trip

Questions

Questionnaires

QNR-6 · Quotation approval clarifications

Outstanding

How magic links work

Stakeholder Portal

Priya needs your input on Quotation Approval

What exactly counts as a "design change" on an approved quotation?

Is a resize beyond tolerance treated as a design change requiring re-approval?

Registers

Reviews & Approvals

Quotation Approval — reviewer consensus

Approval matrix

Pending across project

User Journeys & Process Maps

Quotation to Order — happy path

Process map — Quotation Approval (actors & decisions)

Prototype Studio

AI UX review — advisory

Design alternatives — approval UX

Sign-off — Quotation Approval

Readiness gate

Package contents (v-preview)

Snapshots

Glossary, Calculations & Policies

Knowledge Repository

Standard Customer Approval Flow

Jewellery domain pack

Approvals template

Governance

AI Console

Job history

Capability toggles

Model per capability

Capture to Discovery Inbox

Generate discovery questions

Spec chat — Quotation Approval

Regenerate prototype — impact preview

Add governance item — plain language

Impact preview — accepting PROP-58

Import an existing artefact