Concept build · the real latent-demand loop

What keeps being asked for
— detected, not asserted

The board shows a hardcoded "4 people asked…" card. This page is the loop that makes it real: every unmet ask is loggedclustered by underlying need → and once a cluster crosses the threshold it becomes a demand card with an honest count → widen / connect / create / inform.

The asks and sensed signals below are sample data (marked); everything downstream runs for real. One asymmetry: asked (what people typed) creates demand, sensed (what the matcher inferred) can only second it — never a card on its own.

📓 The unmet-ask log seeded with sample asks — live ones would flow in from the matcher's unmet field

Raw phrasings, exactly as people typed them. Nothing is interpreted until detection runs.

🫥 The sensed-signal log seeded with sample signals — live ones would flow in from needs the matcher inferred but correctly did not treat as asks

Distilled needs, never raw sentences: when a conversation implies a gap nobody asked for out loud (someone writing in Bengali → no ESOL on the board), the matcher logs the need, not the person's words. Sensed signals never count toward the card threshold — they can only corroborate what people actually ask for.