hub / content /engineering /start-here.html
amirmh's picture
Audit pass: merge duplicate docs (57 total), fix ADR index links, header overflow, mobile tables, members button in header, WebP illustrations
a23cf6c verified
Raw
History Blame Contribute Delete
6.32 kB
<article class="doc" id="doc-engineering-start" aria-hidden="true"><div class="strip"><span class="path">engineering/START-HERE.md</span><span class="tag">Engineering</span><span class="meta">read this first</span></div>
<h1>Start Here: How the Engineering Set Works</h1>
<p>Engineering is organized as <strong>one sequential track: 14 development phases</strong>. Read the three intro documents once, then live in the phases, each is a self-contained work order with an objective, goals, what to build, an Achievements list (the definition of done), and a demo. Finish Phase 14 and the MVP is pilot-ready.</p>
<h2 id="sh-intro">Read once before Phase 01</h2>
<div class="tbl-wrap"><table class="col-table">
<thead><tr><th>Document</th><th>Why</th></tr></thead>
<tbody>
<tr><td data-label="Document"><a href="#doc-engineering-primer">Clinical Primer for Engineers</a></td><td data-label="Why">The medicine translated into engineering, plus what you decide alone vs. what always needs clinical sign-off.</td></tr>
<tr><td data-label="Document"><a href="#doc-engineering-mvp-strategy">MVP Build Strategy</a></td><td data-label="Why">What we build fully, build lean, script, buy, or defer, and the deferral register that keeps scope honest.</td></tr>
<tr><td data-label="Document"><a href="#doc-00-overview">System Overview</a></td><td data-label="Why">The 10-minute picture: the five hard rules, how an episode flows day 0&ndash;30, the stack in one paragraph.</td></tr>
</tbody>
</table></div>
<h2 id="sh-phase-index">The 14 phases</h2>
<p>Sequential and <strong>gated by definition of done, not calendar</strong>, a phase ends when its DoD is green. Every phase page carries a live status badge (Pending &rarr; In Progress &rarr; Complete); the dots below and the home-page progress board follow automatically, and every flip is recorded in the members change log with name and date.</p>
<div class="tbl-wrap"><table class="col-table compact">
<thead><tr><th>Phase</th><th>Focus</th></tr></thead>
<tbody>
<tr><td data-label="Phase"><a href="#doc-phase-01"><span class="nav-dot"></span>Phase 01</a></td><td data-label="Focus">Environment &amp; Skeleton</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-02"><span class="nav-dot"></span>Phase 02</a></td><td data-label="Focus">Audit Ledger &amp; Config</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-03"><span class="nav-dot"></span>Phase 03</a></td><td data-label="Focus">Identity &amp; Activation</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-04"><span class="nav-dot"></span>Phase 04</a></td><td data-label="Focus">Episode Engine</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-05"><span class="nav-dot"></span>Phase 05</a></td><td data-label="Focus">Patient Today (PWA)</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-06"><span class="nav-dot"></span>Phase 06</a></td><td data-label="Focus">Notifications &amp; Suppression</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-07"><span class="nav-dot"></span>Phase 07</a></td><td data-label="Focus">Ingestion &amp; FakeEHR</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-08"><span class="nav-dot"></span>Phase 08</a></td><td data-label="Focus">Extraction Pipeline</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-09"><span class="nav-dot"></span>Phase 09</a></td><td data-label="Focus">Seven Gates &amp; Review Queue</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-10"><span class="nav-dot"></span>Phase 10</a></td><td data-label="Focus">Medication Truth</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-11"><span class="nav-dot"></span>Phase 11</a></td><td data-label="Focus">Scheduling &amp; Caregivers</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-12"><span class="nav-dot"></span>Phase 12</a></td><td data-label="Focus">Escalation, Agents &amp; Kill Switches</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-13"><span class="nav-dot"></span>Phase 13</a></td><td data-label="Focus">Clinician Brief &amp; Post-Visit</td></tr>
<tr><td data-label="Phase"><a href="#doc-phase-14"><span class="nav-dot"></span>Phase 14</a></td><td data-label="Focus">Analytics, Hardening &amp; Pilot Readiness</td></tr>
</tbody>
</table></div>
<h2 id="sh-how">How to work a phase</h2>
<p>Open the phase &rarr; flip its badge to <em>In Progress</em> &rarr; build to the <em>Achievements</em> list &rarr; run the <em>Demo</em> with Amir (the clinical founder) &rarr; flip <em>Complete</em> and open the next. Each phase ends with a <em>Deep reference</em> line linking the module contracts, reference chapters, and ADRs that govern that slice of the system, they are the encyclopedia behind the track; the phases are the only to-do list. For AI-assisted coding, paste the phase page plus its deep-reference links into your agent's context, with the System Overview's five hard rules pinned.</p>
<h2 id="sh-members">Tracking &amp; membership</h2>
<div class="tbl-wrap"><table class="col-table">
<thead><tr><th>Action</th><th>Who</th><th>How</th></tr></thead>
<tbody>
<tr><td data-label="Action">See progress</td><td data-label="Who">Anyone with hub access</td><td data-label="How">Badges on every phase page; roll-up on the home page.</td></tr>
<tr><td data-label="Action">Change a status</td><td data-label="Who">Approved members</td><td data-label="How">Click a badge &rarr; pick the new status; recorded with your name and date.</td></tr>
<tr><td data-label="Action">Review history</td><td data-label="Who">Approved members</td><td data-label="How">Members &rarr; Change log.</td></tr>
<tr><td data-label="Action">Join / approve members</td><td data-label="Who">Anyone / Admin</td><td data-label="How">Members &rarr; Request membership; admins see a pending-approvals panel.</td></tr>
</tbody>
</table></div>
<h2 id="sh-practical">Day-one practicals</h2>
<p>Three things come from Amir directly on day one: repository access, the shared founders channel, and environment secrets. If any of the three is missing, that is the first blocker to raise, before writing code. Progress badges on these pages persist for every signed-in member (the backend is live); anything clinical routes to Amir per the primer's decision boundaries.</p>
<div class="pn"><a class="pn-prev" href="#"></a><a class="pn-next" href="#"></a></div>
</article>