nearmiss/index.html at main · ghzhost/nearmiss · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
<!doctype html>
<html lang="en">
  <head>
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1" />
    <meta name="theme-color" content="#2543d8" />
    <meta
      name="description"
      content="NearMiss turns community road-safety evidence into a privacy-safe, auditable corridor case for public decisions."
    />
    <meta property="og:type" content="website" />
    <meta property="og:site_name" content="NearMiss" />
    <meta property="og:title" content="NearMiss — evidence to action for safer streets" />
    <meta
      property="og:description"
      content="Turn community road-safety evidence into a privacy-safe, auditable corridor case for public decisions."
    />
    <meta property="og:url" content="https://nearmiss.chelseakr.com/" />
    <meta name="twitter:card" content="summary" />
    <meta name="twitter:title" content="NearMiss — evidence to action for safer streets" />
    <meta
      name="twitter:description"
      content="Turn community road-safety evidence into a privacy-safe, auditable corridor case for public decisions."
    />
    <link rel="canonical" href="https://nearmiss.chelseakr.com/" />
    <link rel="icon" href="/web/vendor/brand/clearance-mark.svg" type="image/svg+xml" />
    <link rel="stylesheet" href="/web/style.css" />
    <link rel="stylesheet" href="/web/brand.css" />
    <link rel="stylesheet" href="/web/landing.css" />
    <link rel="stylesheet" href="/web/interface.css" />
    <title>NearMiss — evidence to action for safer streets</title>
  </head>
  <body class="gateway-page">
    <a class="skip-link" href="#main">Skip to main content</a>

    <header class="gateway-header">
      <nav class="gateway-nav" aria-label="Primary">
        <a class="brand-lockup" href="/" aria-label="NearMiss home">
          <svg class="clearance-mark" viewBox="0 0 48 32" aria-hidden="true" focusable="false">
            <path class="clearance-path clearance-path-a" d="M3 27 17 13h5" />
            <path class="clearance-path clearance-path-b" d="M45 5 31 19h-5" />
          </svg>
          <span class="brand-lockup-copy">
            <strong>nearmiss</strong>
            <span>evidence to action</span>
          </span>
        </a>
        <div class="gateway-nav-links">
          <a href="/studio/">Check your data</a>
          <a href="/dossier/">Sample dossier</a>
          <a href="/fars/national/">Conflict Atlas</a>
          <a href="/fars/national/?lang=es" hreflang="es" lang="es">Atlas en español</a>
        </div>
      </nav>

      <div class="gateway-hero">
        <div class="gateway-hero-copy">
          <p class="gateway-kicker">Community evidence, made reviewable</p>
          <h1>Turn safety reports into a case a city can examine.</h1>
          <p class="gateway-lede">
            NearMiss helps advocates and public-interest teams carry community reports, exposure,
            and official outcomes into one privacy-safe corridor case—without mistaking raw report
            volume for risk.
          </p>
          <div class="gateway-actions">
            <a class="gateway-action gateway-action-primary" href="/dossier/">Inspect a complete sample dossier</a>
            <a class="gateway-action gateway-action-secondary" href="/studio/">Check whether your data is ready</a>
          </div>
          <p class="gateway-caveat">
            <strong>Claim boundary:</strong> community reports can identify a signal worth examining.
            They do not, by themselves, prove danger, fault, cause, or that a treatment worked.
          </p>
        </div>
        <aside class="gateway-hero-proof" aria-label="What a NearMiss decision packet carries">
          <p class="gateway-proof-label">Decision packet · review mode</p>
          <h2>A claim, its limit, and a next step—kept together.</h2>
          <dl>
            <div><dt>Source</dt><dd>Community reports</dd></div>
            <div><dt>Boundary</dt><dd>No causation claim</dd></div>
            <div><dt>Output</dt><dd>Field-audit request</dd></div>
          </dl>
          <a href="/dossier/">Open the worked example <span aria-hidden="true">↗</span></a>
        </aside>
      </div>
    </header>

    <main id="main">
      <section class="gateway-sample" aria-labelledby="sample-heading">
        <div class="gateway-section-heading">
          <p class="gateway-kicker">The output, before the machinery</p>
          <h2 id="sample-heading">A case someone can review—not another map to interpret.</h2>
          <p class="gateway-section-intro">
            The complete fictional sample shows how the requested action, permitted claim,
            evidence tracks, limitations, and follow-up measurement stay together.
          </p>
          <a class="gateway-text-link" href="/dossier/">Open the complete sample dossier</a>
        </div>
        <article class="gateway-dossier-preview" aria-label="Fictional Decision Dossier preview">
          <div class="gateway-preview-meta">
            <span>FICTIONAL SAMPLE</span>
            <span>EVIDENCE TIER 2</span>
          </div>
          <h3>Mercer Avenue at 8th Street</h3>
          <p class="gateway-preview-ask">
            <strong>Requested action:</strong> conduct a field audit and return with a scoped
            response within 60 days.
          </p>
          <ol class="gateway-preview-chain" aria-label="Dossier evidence chain">
            <li><span>Source</span><strong>3 distinct tracks</strong></li>
            <li><span>Claim</span><strong>Elevated observed rate</strong></li>
            <li><span>Limit</span><strong>No causation</strong></li>
            <li><span>Verify</span><strong>Tier-bounded language</strong></li>
          </ol>
        </article>
      </section>

      <section class="gateway-process" aria-labelledby="process-heading">
        <div class="gateway-section-heading">
          <p class="gateway-kicker">The work is a chain of custody</p>
          <h2 id="process-heading">From lived experience to an accountable next step</h2>
        </div>
        <ol class="gateway-steps">
          <li>
            <span class="gateway-step-number">01</span>
            <h3>Bring the evidence you have</h3>
            <p>Community reports, bike counts, route data, and official outcomes stay distinct so their gaps remain visible.</p>
          </li>
          <li>
            <span class="gateway-step-number">02</span>
            <h3>Check the claim</h3>
            <p>Rates, confidence intervals, privacy floors, source tiers, and bias notes travel with the finding.</p>
          </li>
          <li>
            <span class="gateway-step-number">03</span>
            <h3>Carry a corridor case</h3>
            <p>A Decision Dossier names the requested action, the supporting evidence, its limits, and how follow-up will be measured.</p>
          </li>
        </ol>
      </section>

      <section class="gateway-dossier" aria-labelledby="dossier-heading">
        <div>
          <p class="gateway-kicker">The primary artifact</p>
          <h2 id="dossier-heading">A Decision Dossier keeps the caveat with the claim.</h2>
        </div>
        <div class="gateway-dossier-grid">
          <article>
            <h3>What it asks</h3>
            <p>A named owner, corridor, decision, and next step—rather than an open-ended map of complaints.</p>
          </article>
          <article>
            <h3>What it shows</h3>
            <p>Rates, uncertainty, report patterns, exposure quality, and independent evidence as separate, inspectable tracks.</p>
          </article>
          <article>
            <h3>What it refuses</h3>
            <p>Unqualified safety claims, individual trip disclosure, cross-city leaderboards, and false before-and-after certainty.</p>
          </article>
        </div>
        <div class="gateway-dossier-links">
          <a class="gateway-text-link" href="/studio/">Run the local readiness check</a>
          <a class="gateway-text-link" href="https://github.com/ChelseaKR/nearmiss/blob/main/docs/DECISION-DOSSIER-TEMPLATE.md">Open the Markdown template</a>
          <a class="gateway-text-link" href="https://github.com/ChelseaKR/nearmiss/blob/main/docs/PRODUCT-EXPANSION-PLAN.md">Read the product direction</a>
        </div>
      </section>

      <section class="gateway-reference" aria-labelledby="reference-heading">
        <div class="gateway-reference-copy">
          <p class="gateway-kicker">Available now</p>
          <h2 id="reference-heading">Reviewed national fatal-crash reference data</h2>
          <p>
            The Conflict Atlas is a separately scoped reference surface: it presents reviewed
            2020–2024 NHTSA FARS fatal-crash counts by state and involved road-user mode. It is
            not a near-miss map and does not estimate local risk.
          </p>
          <a class="gateway-text-link" href="/fars/national/">Open the Conflict Atlas</a>
        </div>
        <aside class="gateway-reference-note" aria-label="Reference data limitations">
          <p class="gateway-note-label">Read the label</p>
          <p><strong>Counts are not risk.</strong> The Atlas does not normalize for trips, miles, population, or exposure. Modes can overlap within a crash.</p>
        </aside>
      </section>
    </main>

    <footer class="gateway-footer">
      <p>NearMiss is an independent, open-source evidence tool for safe-streets advocacy.</p>
      <a href="https://github.com/ChelseaKR/nearmiss">Inspect the source and methods</a>
    </footer>
  </body>
</html>