Consumer / Features

Consumer-side capabilities. Nothing here is built or approved.

Read the Consumer foundation first. A feature never redefines the persona, the identity layer or the marketplace relationship — it plugs into them.

Structure

Every feature is a directory, so that adding the next one is a sibling rather than a restructure:

Consumer
│
├── Overview ................ what a Consumer is  (persona, lifecycle, My QR Setu, marketplace)
│
└── Features
    ├── Marriage Biodata Digital Identity
    │     ├── Overview            what it is, and its state
    │     ├── Problem analysis    the seven problems with a forwarded PDF
    │     ├── Research            reference landscape and market
    │     ├── Feature set         capabilities, and the MVP cut
    │     ├── User journey        creator, recipient, and the retirement path
    │     ├── Privacy & security  PII, consent, DPDP, duty of care
    │     ├── Analytics           what is measured, and the proactive surface
    │     ├── Growth              the viral loop and its weak link
    │     ├── Monetization        revenue model against the target
    │     ├── Architecture        fit, reuse, and the decisions to take first
    │     └── Design              design state and what to request
    │
    ├── (next consumer feature)
    └── (future consumer features)

⚠ Related life-event experiences belong under the feature they extend, not at the top level. An engagement card or a wedding invitation is an extension of the marriage journey and sits under it. A resume card is a different audience and would be its own feature directory.

Features

Feature	State	Summary
Marriage Biodata Digital Identity	🔵 research	Replace the WhatsApp-forwarded biodata PDF with a living, access-controlled destination attached to the consumer's identity.

The gates a consumer feature must pass

1. The proactive-value gate. "How does this help the user make progress on what they are actually trying to do?" A feature that only renders is not a feature.
2. The PII rule. Consumer data is personal and is never indexed. No consumer surface is an SEO surface. This has a caching consequence, not only a <meta> one — see Privacy and security.
3. The identity rule. A feature attaches to My QR Setu. It does not own the consumer's slug and it is not the consumer's identity.
4. The marketplace rule. A consumer feature must not become an island; the same account is also a customer of QRSETU merchants.
5. Reuse before extension, extension before new architecture — and the architecture page must say which of the three it is asking for, per the owner's classification.