Wichita Housing Logistics

What it replaces

A case manager in Wichita tracks fifteen households on a legal pad, a shared Google Sheet that nobody trusts, and a group text with three coordinators. When a landlord calls asking "did the family get the keys?" nobody can answer without a round of "let me check and call you back." Beds sit empty because the person holding them didn't tell the person doing assessments. Families fall out of follow-up because there's no view that says "moved in 14 days ago, check on them."

What it is

One URL. Four stages with real counters and a live activity feed. Add a household, assign a bed, post a note. That is the whole app. No accounts to provision, no implementation consultant, no quarterly product roadmap. It runs on Cloudflare's edge with a single database; hosting cost is pocket change.

• StackRust + Leptos 0.8 (SSR + hydration) on Cloudflare Workers, D1 for persistence
• SizeSingle crate, ~3,500 lines. Four tables. One migration path.
• PostureNo login. No AI matching. No maps. No vendor contract.

The one novel piece

Every household carries a private share_token. The URL /case/<token> is both the address and the authentication — whoever holds the link reads their own case in plain language ("you're moved in," "we're holding a spot for you") and sends messages back to the case team. No app install. No password reset. No portal. The relationship changes when the family can see what the case manager sees.

Pilot-scope tradeoffs (rate limiting, log redaction, recovery flow) are documented in the repository's CLAUDE.md under "Customer lane".

What's in the box

• Intake, assessment, placement, follow-up pages with inline stage transitions.
• Housing inventory with kind + status (shelter bed, transitional, PSH, rental, offline).
• Placement lifecycle: proposed → confirmed → moved-in → exited / cancelled.
• Activity feed with typed entities, author attribution, household-authored entries.
• Per-household share-token case page with rotation + clipboard copy from the admin roster.
• Security headers baked at the edge: CSP, HSTS, X-Frame-Options, tightened Referrer-Policy and noindex on customer pages.
• CI verifies both build configurations (SSR + hydrate) on every push.

See it

• Live demo → Ten fictional households, eight inventory units, a week-and-a-half of seeded activity. Poke around — no login, no account.
• GitHub repository → Public archive. Code, migrations, CLAUDE.md with the full architecture / security / pilot-scope notes.