permit-bearings/prepare.html at main · ghzhost/permit-bearings · 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
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
<!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>Prepare the Woodland example | Permit Bearings</title>
<meta name="description" content="Explore a source-bound future-state simulation of a made-up Woodland ADU packet workflow.">
<meta property="og:title" content="Prepare the Woodland example | Permit Bearings">
<meta property="og:description" content="See reported gaps and staff questions in a future-state simulation; no current preapproved plan is represented as available.">
<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="readiness">
<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">Sources &amp; 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">Sources &amp; limits</a>
        <a href="review.html">For staff</a>
      </nav>
    </details>
  </div>
</header>

<main id="mainContent">
  <header class="tool-hero readiness-hero">
    <div class="page-shell readiness-hero-grid">
      <div>
        <p class="eyebrow">Made-up Woodland journey · Future-state simulation</p>
        <h1>Explore a future-state packet workflow</h1>
        <p class="lede">A strict, date-bound City program record controls
          whether this versioned example can open. Even when current, it
          unlocks only a simulation of how a bounded packet-presence check
          could work after a plan is listed. The page accepts no uploads and
          carries no applicant facts in its URL.</p>
      </div>
      <ca-shout class="boundary-note" color="yellow" role="note">
        <p><strong>This is a synthetic future-state packet.</strong> The
          prototype compares reported items with one checklist. It does not
          open plan files or query a live parcel. Two fabricated parcel values
          demonstrate source-field bindings; they are not verified parcel
          facts. The result does not decide legal sufficiency, certify
          completeness, or predict approval.</p>
      </ca-shout>
    </div>
  </header>

  <div class="page-shell readiness-main">
    <section id="programAvailabilityNotice" aria-live="polite">
      <ca-shout class="program-availability program-availability-hold"
        color="yellow" lang="en">
        <p class="utility-label">Official program status</p>
        <p><strong>Checking the date-bound City program record.</strong> Packet
          content remains locked until that record passes validation.</p>
      </ca-shout>
    </section>

    <section class="journey-entry-summary" id="journeyEntrySummary"
      aria-labelledby="journeyEntryHeading" hidden>
      <p class="journey-stage-label">Stage 3 of 4 · Packet</p>
      <h2 id="journeyEntryHeading">The made-up route is bound to this future-state packet</h2>
      <p>The page replays one generated evidence envelope. The URL contains
        only its public ID and version, not project answers or a real applicant
        record.</p>
      <dl>
        <div>
          <dt>Journey ID</dt>
          <dd><code id="journeyEntryId">Loading</code></dd>
        </div>
        <div>
          <dt>Version</dt>
          <dd><code id="journeyEntryVersion">Loading</code></dd>
        </div>
      </dl>
    </section>

    <section class="journey-evidence-summary" id="journeyEvidenceSummary"
      aria-labelledby="journeyEvidenceHeading"
      aria-describedby="journeyEvidenceBoundary" hidden>
      <header class="journey-evidence-header">
        <div>
          <p class="section-kicker">Portable future-state orientation</p>
          <h2 id="journeyEvidenceHeading">Future-state route-to-packet evidence summary</h2>
          <p>This printable view carries the made-up route, its assumptions,
            bounded preparation steps, and exact questions for staff in one
            place.</p>
        </div>
        <dl class="journey-evidence-meta" id="journeyEvidenceMeta">
          <div>
            <dt>Journey ID</dt>
            <dd><code id="journeyEvidenceId">Loading</code></dd>
          </div>
          <div>
            <dt>Version</dt>
            <dd><code id="journeyEvidenceVersion">Loading</code></dd>
          </div>
        </dl>
      </header>

      <section class="journey-evidence-route" id="journeyEvidenceRoute"
        aria-labelledby="journeyEvidenceRouteHeading">
        <p class="section-kicker">Candidate route</p>
        <h3 id="journeyEvidenceRouteHeading">The path carried into packet preparation</h3>
        <div id="journeyEvidenceRouteContent"></div>
      </section>

      <ca-mesh class="journey-evidence-grid" cell-size="large" gap="3">
        <section class="journey-evidence-panel journey-evidence-actions"
          id="journeyEvidenceActions"
          aria-labelledby="journeyEvidenceActionsHeading">
          <h3 id="journeyEvidenceActionsHeading">First preparation actions</h3>
          <p id="journeyEvidenceActionsReview"></p>
          <ol id="journeyEvidenceActionsList"></ol>
        </section>

        <div class="journey-evidence-context-grid">
          <section class="journey-evidence-panel journey-evidence-facts"
            id="journeyEvidenceFacts"
            aria-labelledby="journeyEvidenceFactsHeading">
            <h3 id="journeyEvidenceFactsHeading">Made-up facts and assumptions</h3>
            <p>Every value below is a synthetic fixture. Its provenance says how
              the prototype treats it, not that the value is true for a parcel.</p>
            <dl id="journeyEvidenceFactsList"></dl>
          </section>

          <div class="journey-evidence-context-column">
            <section class="journey-evidence-panel journey-evidence-questions"
              id="journeyEvidenceQuestions"
              aria-labelledby="journeyEvidenceQuestionsHeading">
              <h3 id="journeyEvidenceQuestionsHeading">Ask Woodland staff exactly</h3>
              <ul id="journeyEvidenceQuestionsList"></ul>
            </section>

            <section class="journey-evidence-panel journey-evidence-sources"
              id="journeyEvidenceSources"
              aria-labelledby="journeyEvidenceSourcesHeading">
              <h3 id="journeyEvidenceSourcesHeading">Source and evidence status</h3>
              <dl class="journey-evidence-source-list"
                id="journeyEvidenceSourcesList"></dl>
            </section>
          </div>
        </div>
      </ca-mesh>

      <ca-shout class="journey-evidence-boundary" color="yellow"
        id="journeyEvidenceBoundary" role="note"
        aria-labelledby="journeyEvidenceBoundaryHeading">
        <h3 id="journeyEvidenceBoundaryHeading">Synthetic orientation, not a decision</h3>
        <p id="journeyEvidenceBoundaryText"></p>
      </ca-shout>

      <div class="journey-evidence-controls" id="journeyEvidenceControls">
        <button class="button ca-button" id="printJourneySummary" type="button">
          Print or save this evidence summary
        </button>
        <a id="journeyEvidenceRouteBack" href="check.html?sample=adu">
          Return to the candidate route
        </a>
      </div>
    </section>

    <section class="packet-cover" id="packetCover"
      aria-labelledby="packetHeading" hidden>
      <div>
        <p class="section-kicker">Made-up future-state application record</p>
        <h2 id="packetHeading">Future-state simulation: Woodland preapproved detached ADU</h2>
      </div>
      <dl class="packet-facts">
        <div>
          <dt>Jurisdiction</dt>
          <dd>City of Woodland</dd>
        </div>
        <div>
          <dt>Workflow</dt>
          <dd>Hypothetical detached ADU using a plan after the City lists one</dd>
        </div>
        <div>
          <dt>Packet record</dt>
          <dd id="readinessPacketId">Loading</dd>
        </div>
        <div>
          <dt>Checked</dt>
          <dd id="readinessDate">Loading</dd>
        </div>
      </dl>
    </section>

    <div id="dataLoadError" class="hidden"></div>
    <div id="readinessOutput" aria-live="polite" aria-busy="true">
      <p>Checking the versioned journey record.</p>
    </div>

    <section class="readiness-method" id="readinessMethod"
      aria-labelledby="readinessMethodHeading" hidden>
      <p class="section-kicker">Technical boundary</p>
      <h2 id="readinessMethodHeading">What AI does, and what it does not do</h2>
      <ca-box class="decision-record">
        <dl>
          <div>
            <dt>Official checklist source</dt>
            <dd>The published City checklist is retained with a dated content
              fingerprint.</dd>
          </div>
          <div>
            <dt>AI-assisted draft</dt>
            <dd>AI proposed the checklist mapping and plain-language actions.
              Those drafts are still awaiting named human review.</dd>
          </div>
          <div>
            <dt>Deterministic check</dt>
            <dd>Versioned code compares explicit project facts and packet
              inventory statuses with the source-bound requirement list.
              Unknown facts stay unknown.</dd>
          </div>
          <div>
            <dt>Published output</dt>
            <dd>The generated evidence record lists each finding, source
              locator, content fingerprint, and prototype boundary. No model
              runs in the public browser.</dd>
          </div>
        </dl>
      </ca-box>
      <p class="small">No applicant data is sent to an AI provider. This page
        uses a made-up record bundled with the site.</p>
    </section>
  </div>
</main>

<footer class="site-footer">
  <div class="footer-inner">
    <p>Future-state packet-presence simulation only. The City’s checklist is a summary, and
      staff may request other material. This is not legal advice, a
      completeness certification, or a permit decision.</p>
    <div class="footer-links">
      <a href="evidence.html">Inspect sources and limits</a>
      <a href="check.html?sample=adu">Open the routing example</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>