“Show jewellery online and let people try it virtually.”
A compelling storefront feature, but only one slice of the rental operation.
ONE AMBITIOUS CUSTOMER REQUEST
Can Chaitra rent jewellery online without losing control of the physical piece, the customer promise, or her books?
Chaitra wants a beautiful online catalogue and virtual try-on, but her actual business spans unique physical assets, shop visits, date-based reservations, restricted delivery districts, deposits, returns, undelivered items, accounts and a future network of semi-independent shops. Omkara turns that ambition into an approved, testable delivery chain.
CUSTOMERChaitra Rental Jewellery
PILOTOne Bengaluru shop
SURFACESStorefront + operations
LANGUAGESKannada + English
One unique set cannot be promised twice.
Every booking, shipment, return, exception and financial record must agree on the asset, dates, location and custody.
Why Omkara matters here
An agent could quickly build an attractive ecommerce site. Omkara preserves the harder truth: this is a rental and custody system with a customer storefront—not a generic “buy now” catalogue.
STAGE 1 · DISCOVERY RECORD
Separate what was seen from what was assumed.
Every finding retains source, classification, approval and confidentiality.
“The booking is not finished when the customer pays. I need to know which exact set is where until it is returned, inspected and ready again.”
Observed evidence
Two spreadsheet rows reserve the same physical bridal set for overlapping dates.
Stakeholder claim
Failed deliveries are followed through calls, courier messages and handwritten notes.
FDE recommendation
Give every set an asset ID and explicit custody lifecycle before automating recommendations.
Agent inference — unapproved
All Karnataka districts should be enabled because shipping is technically possible.
Customer journey
Browse → shortlist/try-on → visit or delivery → reserve dates → receive → use → return → inspection.
Service boundary
Only owner-configured districts around Bengaluru; unsupported locations may choose a shop visit.
Custody problem
“Undelivered” must show whether the shop, courier or customer has the sealed item.
Finance need
Link invoices, receipts, deposits, refunds, adjustments and supporting records for accountant review.
Future model
Standalone branches close locally and send controlled day-end batches to the main entity.
Safety boundary
Tax configuration is accountant-reviewed; the product does not invent rates or filing obligations.
STAGE 2 · APPROVED INTENT PROOF
Chaitra approves the business workflow visually.
The product mockup is attached as a versioned Visual Contract.
Browse, try and book
Date-aware catalogue, shop visit or virtual try-on, and serviceability before delivery booking.
Asset and custody control
Unique sets, booking states, courier exceptions, returns, inspection, finance records.
Day-end synchronization
Signed local closing batches, main-entity reconciliation and no silent conflict resolution.
VISUAL CONTRACT · V1
READY FOR OWNER REVIEWChaitra Rental Jewellery Services
AvailableHeldBookedPackedCourier custodyDeliveredWith customerReturn dueInspectionCleaning / repairAvailable again
Open interactive product mockup ↗What must be true
- No overlapping booking of one asset.
- Unsupported districts cannot reach delivery payment.
- Virtual try-on is described as a preview, not exact fit.
- Every custody transition has actor and evidence.
What waits
- Autonomous pricing and recommendations.
- Statewide shipping.
- Automated tax filing.
- Full multi-branch operations before the single-shop model is proven.
STAGE 3 · MULTI-AGENT DELIVERY
Different workers, one product truth.
Omkara gives every role the approved evidence, states and prohibitions.
Asset, availability, custody, booking, ledger and branch batch.
Catalogue, try-on, visit and serviceable delivery journey.
Inventory lifecycle, exceptions, billing records and closing.
Exact-commit customer, owner and branch scenarios.
Intent alignment, evidence, security and merge readiness.
Attached truth
Discovery v2 · Intent Proof v1 · Visual Contract v1 · asset-state model · service boundary · finance boundary.
Prohibited drift
No purchase checkout, no nationwide delivery, no pooled SKU count, no silent branch conflict, no automated tax judgment.
Completion gate
Parity critical paths pass against the reviewed commit and Chaitra approves the corrected visual comparison.
STAGE 4 · VISION-DRIFT GATE
Beautiful ecommerce can still be the wrong system.
The first implementation optimizes checkout and hides physical custody.
“Buy now · ships across Karnataka”
Jewellery is a SKU with quantity. The same physical set can be promised twice, and “shipped” ends the operational timeline.
≠
Rent one traceable asset
Date-bounded reservation, configured delivery areas, visit alternative, deposit/return workflow and continuous custody evidence.
BLOCKING DEVIATION CRJ-07: Purchase checkout, statewide delivery and pooled SKU stock contradict Chaitra’s approved rental lifecycle and operating boundary. Merge is disabled.
Not subjective design feedback
The finding links to the overlapping-booking evidence, service district decision, undelivered-item workflow and approved mockup.
Restore the contract
The Executor introduces asset IDs, date conflicts, custody states and configuration-driven serviceability; any changed business decision requires a new approval version.
STAGE 5 · PARITY EXACT-COMMIT PROOF
Test business truth, not feature presence.
Illustrative evidence matrix tied to one implementation commit.
✓
Try-on and shop-visit paths
Preview disclaimer and appointment state captured.
✓
Delivery boundary
Supported district proceeds; unsupported district is blocked with visit alternative.
✓
Overlapping dates
Second hold on the same asset is rejected.
✓
Courier exception
Custody remains visible through failed delivery and shop return.
✓
Accountant pack
Invoice, receipt, deposit and adjustment references reconcile.
✓
Day-end conflict
Branch batch pauses for human reconciliation; neither source disappears.
PR EVALUATION · COMMIT 4fc91bd
HUMAN MERGE APPROVALIntent aligned · evidence complete
Parity run P-CH-104, security review, Visual Contract comparison and finance-boundary review are attached to the exact commit.
STAGE 6 · DEPLOYMENT RECORD
Start narrow; preserve the expansion path.
The branch architecture is prepared, but the pilot proves one shop first.
Storefront + owner operations
Run P-CH-104 attached
Selected assets and districts
Daily custody and ledger review
Virtual try-on, districts, then branch
Lineage
Discovery v2 → Intent v1 → commit 4fc91bd → Parity P-CH-104 → PR evaluation E-CH-12.
Configuration
Enabled assets · supported districts · booking windows · deposit/terms · accountant-reviewed tax codes.
Daily control
Open custody exceptions, overdue returns, unreconciled ledger items and inventory availability.
Rollback
Pause online bookings without losing existing reservations or custody history.
STAGE 7 · OUTCOME RECORD
Did Chaitra gain trusted control—not just a website?
Targets below are illustrative pilot measures, not claimed results.
Pilot target
Open movements have owner
Records linked before close
Visit vs try-on vs delivery
Confidence before booking
Customers can shortlist visually, understand availability and choose the right fulfilment path.
Every piece accounted for
Booking, custody, exception and finance records describe the same real-world asset journey.
Earn the next branch
Add districts or shops only when operations, service quality, reconciliation and economics support it.
Omkara’s contribution
It preserves Chaitra’s original ambition while preventing a polished but misleading ecommerce build. The final chain connects her evidence → approved experience → agent decisions → exact code → Parity proof → rollout → measurable business outcome.