forked from ChelseaKR/permit-bearings
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathevidence.html
More file actions
309 lines (291 loc) · 14.3 KB
/
Copy pathevidence.html
File metadata and controls
309 lines (291 loc) · 14.3 KB
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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="referrer" content="no-referrer">
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'none'">
<title>Evidence & updates | Permit Bearings</title>
<meta name="description" content="Inspect the prototype’s committed source-watch snapshot, rule dependencies, regression cases, external-evidence gate, known gaps, and change rehearsal.">
<meta property="og:title" content="Evidence & updates | Permit Bearings">
<meta property="og:description" content="See which sources are dated, which rules depend on them, and what the prototype still cannot verify.">
<meta property="og:type" content="website">
<link rel="icon" href="assets/favicon.svg" type="image/svg+xml">
<link rel="stylesheet" href="assets/california-design-system.css?v=20260809b">
<link rel="stylesheet" href="assets/site.css?v=20260810a">
</head>
<body data-page="evidence">
<div id="skip-to-content">
<a class="skip-link" href="#mainContent">Skip to main content</a>
</div>
<header class="site-header">
<div class="header-inner">
<div class="site-identity">
<a class="brand" href="index.html" aria-label="Permit Bearings home">
Permit Bearings
</a>
<span class="prototype-label">Prototype</span>
</div>
<nav class="site-nav" aria-label="Primary">
<a href="check.html">Start</a>
<a href="evidence.html" aria-current="page">Sources & limits</a>
<a href="review.html">For staff</a>
</nav>
<details class="mobile-menu">
<summary>Sections</summary>
<nav class="mobile-nav" aria-label="Mobile primary">
<a href="check.html">Start</a>
<a href="evidence.html" aria-current="page">Sources & limits</a>
<a href="review.html">For staff</a>
</nav>
</details>
</div>
</header>
<main id="mainContent">
<header class="tool-hero">
<div class="page-shell tool-hero-grid">
<div>
<p class="eyebrow">Evidence & updates</p>
<h1>Evidence and source status</h1>
<p class="lede">Inspect the dated source record behind each encoded
rule, replay the structured cases, and see which records would need
review after a source changes.</p>
</div>
<ca-shout class="boundary-note" color="yellow" role="note">
<p><strong>Source status is not approval.</strong> A date on file means
source evidence was recorded. It does not mean a jurisdiction,
counsel, or named human reviewer accepted the encoded interpretation.</p>
</ca-shout>
</div>
</header>
<div class="page-shell tool-main">
<section aria-labelledby="statusHeading">
<p class="section-kicker">Current prototype state</p>
<h2 id="statusHeading">Rule-source status</h2>
<p class="section-intro">The browser recomputes these figures from the
same generated data bundle used by the project guide and applies the
reviewed source-watch snapshot committed with that bundle.</p>
<ca-mesh class="evidence-summary rule-evidence-summary" gap="2">
<article class="evidence-stat">
<p class="utility-label">Within review window</p>
<p class="hero"><span id="pct">Loading</span><span aria-hidden="true">%</span></p>
<p class="small">of rule records have dated source evidence inside
the 180-day review window.</p>
</article>
<article class="evidence-stat">
<p class="utility-label">Structured replay</p>
<p class="hero" id="goldenScore">Loading</p>
<p class="small" id="goldenLine">Loading structured scenarios…</p>
</article>
<article class="evidence-stat">
<p class="utility-label">Registry reach</p>
<p class="hero" id="coverageScore">Loading</p>
<p class="small" id="covLine">Loading jurisdiction registry…</p>
</article>
<article class="evidence-stat">
<p class="utility-label">Named interpretation review</p>
<p class="hero" id="verificationScore">Loading</p>
<p class="small" id="verificationLine">Loading the strict
rule-verification ledger…</p>
</article>
</ca-mesh>
<div class="meter" id="meter" role="img"
aria-label="Loading rule-source status"></div>
<p class="small" id="meterLegend"></p>
<p class="utility-label coverage-meter-label">Statewide HCD-letter orientation</p>
<div class="meter coverage-meter" id="coverageMeter" role="img"
aria-label="Loading statewide coverage"></div>
<p class="small" id="coverageMeterLegend"></p>
<ca-box class="simulation-box" aria-labelledby="sourceSnapshotHeading">
<p class="utility-label">Committed source-state receipt</p>
<h3 id="sourceSnapshotHeading">Snapshot used by this build</h3>
<p id="sourceSnapshotSummary">Loading the committed source-state
receipt…</p>
<ca-shout id="sourceImpactQueue" class="notice hidden"></ca-shout>
<p class="small"><strong>Receipt status “reviewed”</strong> means a
repository maintainer deliberately adopted this completed-run
receipt for publication. It does not mean that a named human,
counsel, or a jurisdiction approved the legal interpretation or
product guidance.</p>
<p class="small"><a id="sourceSnapshotRun" href="evidence.html">
Open the exact workflow receipt</a> ·
<a href="data/source-status/current.json">Inspect the machine-readable
snapshot</a></p>
</ca-box>
<ca-box class="simulation-box" aria-labelledby="simulationHeading">
<p class="utility-label">Dependency rehearsal</p>
<h3 id="simulationHeading">What happens when § 66321 changes?</h3>
<p>Temporarily layer a change to one source ID over the committed
snapshot. Every linked rule turns stale; unrelated records remain
unchanged. The rehearsal itself is not written back to the committed
receipt or review queue.</p>
<p>
<button class="ghost ca-button ca-button-outline" id="simBtn" type="button" disabled>
Rehearse the source change
</button>
<button class="ghost hidden ca-button ca-button-outline" id="resetBtn" type="button" disabled>
Reset the rehearsal
</button>
</p>
<ca-shout class="notice hidden" color="yellow" id="simNote">
Gov. Code § 66321 has been marked changed for this rehearsal. Linked
rules below are stale until a person checks them against the new
source text. To see that state on applicant records, open the
<a href="check.html?changed=ca-gov-66321">project guide with the
rehearsal applied</a>.
</ca-shout>
<p id="simulationStatus" class="visually-hidden"
aria-live="polite"></p>
</ca-box>
<div id="dataLoadError" class="hidden"></div>
<div class="table-scroll" role="region"
aria-label="Rule source status table" tabindex="0">
<table class="ca-inner-border ca-outer-border ca-stripes ca-hover-rows"
id="ruleTable">
<thead>
<tr><th>Rule</th><th>Scope</th><th>Source status</th>
<th>Interpretation review</th></tr>
</thead>
<tbody></tbody>
</table>
</div>
<p class="small">Machine-linked means the rule is connected to its
recorded source; it is not named human or jurisdiction review. Inspect
the <a href="data/validation/rule-verification.json">machine-readable
rule-verification ledger</a>.</p>
</section>
<section class="source-section flagship-evidence-gate"
aria-labelledby="externalEvidenceHeading">
<p class="section-kicker">Flagship evidence gate</p>
<h2 id="externalEvidenceHeading">Prepared, not run</h2>
<p class="section-intro">The review and research package is versioned so
future evidence can be tied to one journey, source snapshot, and
commit. Preparing the package is not evidence that any external work
occurred.</p>
<ca-shout class="notice" color="yellow">
<p><strong>No external outcome is claimed.</strong> No qualified content
review, participant session, manual accessibility signoff, Spanish
semantic review, complete maintenance rehearsal, or qualifying
partner commitment is recorded.</p>
</ca-shout>
<ca-mesh class="evidence-summary" gap="2" role="group"
aria-label="External evidence gate status">
<article class="evidence-stat" aria-labelledby="contentReviewLabel">
<h3 class="utility-label" id="contentReviewLabel">25-item content review</h3>
<p class="hero evidence-gate-status">Not run</p>
<p class="small">Two independent reviewer slots are prepared. Every
row-level mapping and action disposition remains pending.</p>
</article>
<article class="evidence-stat" aria-labelledby="sessionStatusLabel">
<h3 class="utility-label" id="sessionStatusLabel">Same-version sessions</h3>
<p class="hero evidence-gate-status">Not run</p>
<p class="small">No applicant or practitioner session, score, task
time, quotation, or usability outcome is recorded.</p>
</article>
<article class="evidence-stat" aria-labelledby="partnerGateLabel">
<h3 class="utility-label" id="partnerGateLabel">Partner gate</h3>
<p class="hero evidence-gate-status">Pending</p>
<p class="small">No written next step with an owner and date is on
file. Interest or praise would not satisfy this gate.</p>
</article>
</ca-mesh>
<dl class="method-list">
<div>
<dt>Manual access and language</dt>
<dd><strong>Not run.</strong> Keyboard, screen-reader, zoom, mobile,
print/PDF accessibility, forced-colors, and Spanish semantic checks
still require signed, version-bound evidence.</dd>
</div>
<div>
<dt>Maintenance rehearsal</dt>
<dd><strong>Not run.</strong> The browser simulation above is not the
timed detection-to-republication rehearsal and does not establish
an acceptable maintenance burden.</dd>
</div>
</dl>
<p class="small">Inspect the
<a href="data/validation/woodland-flagship-gate.json">machine-readable
gate ledger</a>,
<a href="data/validation/woodland-content-review.json">25-row review
matrix</a>, and
<a href="data/validation/woodland-manual-evidence.json">manual evidence
matrix</a>. Inspect the
<a href="data/validation/woodland-participant-sessions.json">six-session
scorecard ledger</a> and
<a href="data/validation/woodland-source-change-rehearsal.json">source-change
rehearsal ledger</a>. Read the
<a href="https://github.com/ChelseaKR/permit-pathways/blob/main/docs/VALIDATION-EVIDENCE.md"
rel="noopener">execution and claim protocol</a>.</p>
</section>
<section class="source-section" aria-labelledby="sourcesHeading">
<p class="section-kicker">Recorded source evidence</p>
<h2 id="sourcesHeading">Source monitoring</h2>
<p class="section-intro">Selected official state and local sources have a
recorded content hash and are re-fetched by the repository workflow.
A reviewed snapshot of the last run is bundled above and overlays its
exact changed-source dependencies on applicant outputs. Unwatchable
sources remain visible as reference-only records. Automatic adoption,
review assignment, and new-law discovery remain planned.</p>
<div class="table-scroll" role="region"
aria-label="Source monitoring table" tabindex="0">
<table class="ca-inner-border ca-outer-border ca-stripes ca-hover-rows"
id="sourceTable">
<thead>
<tr><th>Source</th><th>Monitoring</th><th>Recorded</th><th>SHA-256</th></tr>
</thead>
<tbody></tbody>
</table>
</div>
</section>
<section class="source-section method-section"
aria-labelledby="methodHeading">
<p class="section-kicker">How to read this page</p>
<h2 id="methodHeading">Four boundaries stay visible.</h2>
<p>Trust comes from showing what each artifact proves and what it does
not prove.</p>
<dl class="method-list">
<div>
<dt>Matching</dt>
<dd><strong>Rules choose the records.</strong> Deterministic criteria
use the applicant’s structured answers. Explanation copy cannot
create or change a match.</dd>
</div>
<div>
<dt>Language</dt>
<dd><strong>Readable copy stays separate.</strong> English and Spanish
explanations are versioned AI-assisted prototype drafts. None is
represented as human-reviewed or jurisdiction-approved.</dd>
</div>
<div>
<dt>Currency</dt>
<dd><strong>A changed source affects its dependents.</strong> Stable
source IDs connect rules to evidence. A reviewed watch snapshot is
committed with the public bundle; the change rehearsal remains a
separate temporary overlay.</dd>
</div>
<div>
<dt>Coverage</dt>
<dd><strong>Statewide screening is not local encoding.</strong> The
statewide candidate-rule set can run for the registry. That does
not mean local codes, forms, parcel facts, or exceptions are
comprehensively represented.</dd>
</div>
</dl>
</section>
</div>
</main>
<footer class="site-footer">
<div class="footer-inner">
<p>This page reports prototype evidence and known gaps. It does not claim
legal correctness, jurisdiction acceptance, comprehensive coverage, or
completed human accessibility testing.</p>
<div class="footer-links">
<a href="check.html">Check a project</a>
<a href="review.html">Review local rules</a>
</div>
</div>
</footer>
<script src="data/demo-data.js?v=20260810a" defer></script>
<script src="assets/demo.js?v=20260810a" defer></script>
</body>
</html>