Mandi rates + SHG pages, the business track's government-value layer (B-PHASES B5 — zero dependency on B1–B4, ships first). Governed by B5-brief.md + B-UX-PLAN.md §1 ten laws / §3-B5 / §4 reuse map. The farmer field spec is binding on the strip row: ₹ number = the largest element, freshness chip adjacent, mandi+km subline, table not chart in the detail. The traffic-light freshness chips (L4) are designed once here and become the B-series standard. SHG = facilitated create (distinct from the B1 wizard) + an official-not-social group page (L6) with the state-agnostic srlm badge (DECISIONS #16). Frames are English except the binding Hindi copy specified by the brief — those strings ARE the spec (DECISIONS #8; b5f = hi locale check).
The farmer workflow (B-PHASES B5): block page opens → mandi paid ₹2,280 yesterday → he negotiates or goes himself. IA: mandi rides the Today-strip 3rd cell on block/district pages ONLY (village keeps the personal cell) — number-first per the S3 amendment, ₹ teaser + crop word. Strip row = the farmer field spec exactly: crop icon · crop name (server-driven locale label — NEVER Agmarknet English, §6 i18n) · ₹/क्विंटल at 23px, the largest element on the row · freshness chip adjacent to the number (green आज / amber कल — L4) · mandi+km subline · "+ 4 फसलें देखें". 2 my-crop rows by default (block+season inference until b5c capture). "फसल बदलें" chip = the recapture entry, section-header aside. Source line visible on the strip too — government data is the trust spine (one-strike rule: Agmarknet ONLY, never manual). Local groups row beneath = the SHG rail surfacing on the same Overview (S4 .off row + JEEViKA badge → b5e). 2G: text+SVG only, payload <4KB cached 48h — cached views show amber/red chips, never silent-stale, never blank (app-only). Garkha is not home → level-aware Follow block (S3 D14).
Tap a strip row → detail sheet, screenshot-complete in one frame (the screenshot IS the share format on 2G). TABLE, no chart — the farmer reads numbers, not curves; ruling: the net-new micro-sparkline is CUT (L10 ceiling spent elsewhere) and the 7-day story renders as a low–high RANGE line with today's marker — a number-anchored band, not a graph. Table = मंडी | दूरी | आज | कल, 3 rows: nearest-first, and the third row is the RED-CHIP STALE variant — date chip + number greyed (L4: red ⇒ de-emphasized), never hidden, never blank. Transport-cost reference line ("अनुमानित ट्रांसपोर्ट…") closes the go-myself decision — field-seeded one-liner per mandi, ops not engineering. "स्रोत: Agmarknet सरकारी डेटा" sits unscrolled above the fold. "भाव शेयर करें" = the virality mechanism: pre-formatted Hindi WhatsApp string shown verbatim beneath the CTA — what he forwards to the village group tonight. Sheet = the S4 .poish surface 1:1 (§4 reuse map).
First open of any mandi surface: one-time sheet, 2 taps total — tap गेहूं, tap धान, the sheet saves and dismisses itself (no Next button, no confirm; ruling: the closing line states the auto-save so the absence of a CTA reads as done, not broken). Chips are giant pictogram targets (L1 — a non-reader picks his crop by the glyph); the candidate list is block+season inferred, server-driven labels (§6), rabi/kharif ordering by month. "बाद में" = the only escape (L1: never "Skip") — defaults then stay on block-inference, never empty. Behind the sheet the strip already lives in its post-capture state: the "फसल बदलें" chip is the permanent re-entry to this exact sheet (state 2 of the brief). App-only: choice stored per-user, drives the 2-row default; re-prompt never repeats.
DISTINCT variant of the B1 wizard (§3-B1/SHG: 13-step session ≤12 min, facilitator drives, full script in the flow-walk record) — the 5 key screens stacked as a spec strip: ① समूह tile on the create picker (B1 giant-pictogram tiles; tap advances, no Next) · ② group name ("समूह का नाम", mic on field, NEVER auto-filled from the facilitator's profile) + reg number optional · ③ products multi-select (same giant-chip grammar as b5c) · ④ contact step — phone EMPTY with the binding prompt "समूह/अध्यक्ष का नंबर", whose-number radio (president's vs the group's shared phone), contactDisplayName "Rekha didi — President", and the caller-view PREVIEW (L5): the consent step IS seeing the exact card a stranger sees — name · category · village · 🔒 no number · ⑤ ADMIN HANDOFF — sent to the president's phone, she accepts via one OTP, ownership transfers, the facilitator never stays admin. Same proxy-create machinery as CSC seeding + elder onboarding (one feature, three channels).
Pushed page, S13 chrome lite (§4 reuse map: app bar + back, never place tabs). L6 official-not-social: zero reactions, zero comment counts, no feed chrome — the page reads like a notice board entry. srlm badge "JEEViKA समूह" = SERVER CONFIG (DECISIONS #16): the same component renders Kudumbashree in Kerala, Mission Shakti in Odisha — zero hard-coding; reg number quietly beneath. Every product carries the migrant-qualification trio (§3-B5): price-range + min-order + delivers-to/collect-from — Santosh in Patna can qualify the call before he makes it. Nyburs-first contact ladder (DECISIONS #19): ① MESSAGE = Nyburs chat enquiry, the primary CTA (product context auto-attached) ② Call second via the locked sheet ③ WhatsApp DEMOTED to a row inside the locked Call·WhatsApp·Copy sheet — never a primary button (the prior WhatsApp-first ordering of §3-B5 is AMENDED); the number never renders (lock line at the buttons, not a tooltip). Contact = "Rekha didi — President" as plain text with a lock: NO member personal profiles, ever (family-surveillance safety). L4 activity chip on the header; L7 viewed-honesty footer ("viewed", never "called"; zero never renders).
DECISIONS #8: ONE language per screen via i18n — this frame renders B5·A end-to-end in hi to validate the structural keys around the (already-Hindi) binding mandi copy: header गढ़खा · प्रखंड, "प्रखंड फ़ॉलो करें", rung sublabels ज़िला/प्रखंड/गाँव, Today cells नई/खुली + the mandi teaser, tabs, "स्थानीय समूह", row sublines. Numerals and "Nyburs"/"APMC"/"SHG"/"JEEViKA" stay Latin. Crop names + srlm brand = server-driven domain vocabulary (§6) — identical in both frames by design, NOT ARB keys. SHG-page hi keys ride the normal 12-locale translation pipeline (flagged for the lead — only one hi frame per the brief).
DECISIONS #20: small groups (SHG/FPO/co-op/artisan) are a PROMOTED CLASS, not listings. The Garkha BLOCK Overview carries a "स्थानीय उत्पाद" carousel aggregating group products UP the hierarchy (#20b) — Mahila Vikas's सत्तू from Bheldi sits beside Sitalpur's अचार and Dumri's handloom on the block page (and rides further to the district carousel). REACH-UP is the group privilege: the solo kirana stays village-scoped; only group products travel. Card = photo tile · name · ₹range · group + village attribution ("महिला विकास SHG · भेलड़ी") · gold shield = verified group (#20f, reg no.→SRLM-verified = rank boost; unverified renders plain, never excluded). This is FREE editorial placement (gov-alignment #16, free-FIRST invariant) — NEVER a "Sponsored" label; rank = verified + L4 activity (red-chip groups sink, L4 grammar reused). FESTIVAL STATE (#20d): during Chhath the same slot leads with the "छठ संग्रह · हमारे गांवों से" banner + collection-ribboned cards — festival windows are CMS-config'd per state (Chhath in Bihar, Onam in Kerala), timed to peak diaspora buying; the migrant showcase (#20c) = this rail surfacing to diaspora followers of the home block + the b5h share-cards. Tap card → b5e group page (Message-first, #19); L6: cards are catalogue entries — zero social chrome. App-only: rail assembly/rank server-side; card payload rides the Overview DTO.
TOP — the block-level SRLM CLUSTER DIRECTORY (#20g): a pushed page "JEEViKA समूह · गढ़खा" listing every group in the block as rows (name · village · products line · L4 active dot · verified badge #20f — Bunkar Sahkari renders unverified + amber, present but de-emphasized, never hidden). Title/brand = srlm SERVER CONFIG (#16): the identical page renders Kudumbashree in Kerala, Mission Shakti in Odisha — zero hard-coding. This page IS the coordinator's showcase: what the JEEViKA cluster coordinator projects at the weekly cluster meeting to recruit the next 11 groups — the framing lives in field ops; no coordinator profile in the UI (same no-member-profiles rule as b5e). BOTTOM — the group-page additions riding b5e: ① PROOF LOOP (#20h) — "इस महीने 12 ऑर्डर Nyburs से"; L7 binding: measured Nyburs-chat orders only, zero never renders (a new group shows NO line, never "0 ऑर्डर") — this line is the cluster-meeting adoption trigger. ② "हमारा चैनल" (#21) — the page links the group's broadcast CHANNEL: join CTA sits beside the #19 ladder (Message primary · Call · WhatsApp inside the locked sheet); DM = Message, channel = one-to-many — together they replace WhatsApp + WhatsApp-Channel; never auto-join (page-follow vs channel-join = the open Q parked for the B3 council). ③ 9:16 share-out card (#20c) + "शेयर करें" — share-OUT to WhatsApp/diaspora is the growth channel (#19 allows OUT; the conversation comes back to Nyburs via the card's page link). Share card = a rendered asset — fixed brand art, identical in both themes.
B5 position: the business track's government-value layer (B-PHASES B5 — zero dependency on B1–B4, ships first; DECISIONS #17 locks B5+B1 as the design order). App-only/ops mechanics cited, not designed: Agmarknet daily ingest (national, ~47 Bihar mandis) + one-time mandi↔place mapping · payload <4KB JSON cached 48h — cached views show amber/red chips, never silent-stale, never blank · government source ONLY, never manual (one-strike trust rule) · transport-cost lines are field-seeded per mandi (ops, not engineering) · crop names / srlm brands / mandi proper nouns = SERVER-DRIVEN domain vocabulary (§6 — directoryTemplate precedent, CMS-editable per state, never Agmarknet English) · srlm config per DECISIONS #16 (JEEViKA = Bihar; Kudumbashree/Mission Shakti/MAVIM render from the same component) · SHG facilitated create rides the B1 PROXY-CREATE machinery (create-on-behalf + one-OTP ownership handoff — one feature, three channels: SHG facilitator, CSC VLE seeding, elder onboarding; 13-step ≤12-min session script in the B-UX-PLAN flow-walk record) · seeding toolkit (forwardable create deep-link + CMS field-ops dashboard) = B5 feature 3, a CMS surface outside this app mockup. Ruling log: micro-sparkline CUT (table beats chart; the 7-day story = a low–high range band, not a graph) · the L4 freshness chips designed here are THE B-series standard · b5b shows the red-chip stale state as the third table row (greyed number) so green/amber/red all render once across b5a+b5b · b5f = the block page in hi (highest structural-key coverage); SHG-page hi keys ride the normal translation pipeline · R+ (2026-06-11 owner): Nyburs-first contact ladder per DECISIONS #19 — WhatsApp demoted to locked-sheet row on all conversation surfaces; share-out links unchanged. R++ (2026-06-11 owner, GROUP PROMOTION PACK — frames b5g+b5h, DECISIONS #20/#21): groups = a PROMOTED CLASS — "स्थानीय उत्पाद" rail aggregates group products UP the hierarchy (#20b: reach-up is the group privilege; solo kirana stays village-scoped) · rail = FREE editorial placement, NEVER a "Sponsored" label (free-FIRST + gov-alignment #16) · unverified groups render plain attribution/no shield — present, never excluded; verified (#20f) = gold shield + rank boost · festival collections (#20d) = CMS-config'd windows per state (Chhath/Bihar shown; Onam/Kerala from the same component), timed to peak diaspora buying; ribbon = collection tag, not a price flag · cluster directory (#20g) brand/title = srlm server config (#16); coordinator-showcase framing lives in field ops — NO coordinator profile in UI (no-member-profiles rule extends) · proof loop (#20h) counts measured Nyburs-chat orders ONLY; L7: ZERO NEVER RENDERS (new group = no line, never "0 ऑर्डर") · "हमारा चैनल" (#21) joins the #19 ladder as the one-to-many surface — never auto-join; page-follow vs channel-join = OPEN Q parked for the B3 council · 9:16 share-card (#20c) = a rendered asset (fixed brand art, identical both themes); share-OUT to WhatsApp allowed (#19), the conversation returns via the card's page link · group-page additions (proof/channel/share) are designed in b5h and RIDE b5e — b5e itself unmodified.