FASP Intel · Lite

Build a family safety dossier

Answer six short questions about who's moving and what you're worried about. You'll get a single sourced, dated dossier — bottom line first, what the numbers say, what the streets say, what specifically matters for your household, and what to verify in person before you sign anything.

Neighborhood or ZIP * Where are you considering? You can type a neighborhood name like "Sam Hughes, Tucson" or a ZIP like "85719." We currently only cover Tucson neighborhoods — if you enter something outside that, the dossier will tell you so honestly rather than make things up.

Your household * In one short phrase, describe who lives in the home. The dossier reads completely differently for "single parent + 7yo daughter" vs. "two parents + middle-schooler + dog" vs. "retired couple." This is the single biggest input shaping what the report emphasizes — be specific instead of generic.

What concerns you most? * Pick the one safety topic you most want a real answer to. The dossier still covers the others, but it leads with this one and dedicates the "for your household specifically" section to it. If two concerns are equally heavy, pick the one you'd lose sleep over.

School-age children If kids are part of this move, what age band? Determines whether the dossier weights elementary, middle, or high school data, and how it frames the walk-to-school analysis. Pick "None" to skip school content entirely.

Primary mobility How does your household actually move around day-to-day? Walking households need sidewalk + lighting + crossing analysis; driving households need traffic + parking + car-break-in analysis. Be honest about what you really do, not aspirational.

When are you moving? How urgent is the decision? Tight windows (under 30 days) get a "what's the minimum to verify in person before you sign" emphasis; longer windows get more research-oriented suggestions. "Just researching" tells the dossier you want depth, not urgency.

Anything else? Free-form. Add whatever shapes your decision but didn't fit above: budget, tenure (rent vs. buy), a child's specific needs, a parent's mobility, a pet, a remote-work routine that keeps someone home all day. The dossier reads this and re-weights accordingly. Skip anything about specific people — FASP doesn't research individuals.

Prototype: shows the prompt payload only.

What this dossier is — and isn't

It is: a sourced, dated, neighborhood-level family safety brief. Crime patterns, school quality, walk-to-school dynamics, daily-life texture, and a short list of things to verify in person before signing a lease.

It isn't:

A professional risk assessment. Don't use it for insurance, lending, or hiring decisions.
Research on specific people — FASP only covers neighborhoods, not individuals.
Address-level prediction. We trust the data at the neighborhood scale, not the parcel.
A real-estate recommendation. We don't list properties, take referral fees, or tell you whether to move.

Prompt payload (prototype echo)

In production, this gets sent to the dossier engine along with the master prompt at /intel/prompt. For now, it just echoes the structured inputs so you can confirm what was captured.

View the worked sample output → Clear and try another

Where this is in the build

This page is the input half of Find a Safe Place Intel. The output half is rendered separately — see the worked sample dossier for what the output looks like with the inputs the "Load the sample" button populates. The full master prompt that turns inputs into a dossier is published openly at /intel/prompt — same transparency principle as /methodology and /our-sources.

What lands next: model wiring (each submitted form actually generates a dossier), a coverage check that politely refuses neighborhoods we don't yet ingest, per-IP rate limiting, and an optional "email me the dossier" path. The order is intentional — the prompt + form pair is the contract; everything else is plumbing on top of it.