docs/landing/index.html · aaronrene/overseer-kit

<p class="sublead">ROADMAP holds the plan. HANDOVER carries the baton between sessions. Overseer Kit helps teams keep both honest from first review through final verification.</p>

42

43

44

<span class="hero-terminal-title">overseer — honesty loop</span>

49

</div>

50

<pre class="hero-terminal-body"><code><span class="term-prompt">01</span> <span class="term-cmd">PLAN</span> <span class="term-flag">freeze · challenge</span> <span class="term-str"></span>

51

<span class="term-out">independent review · revise until clear</span>

52

<span class="term-prompt">02</span> <span class="term-cmd">BUILD</span> <span class="term-flag">phases · checks</span> <span class="term-str"></span>

53

<span class="term-ok">VERIFY against freeze · HANDOVER truth</span> <span class="term-cursor" aria-hidden="true"></span></code></pre>

</div>

<a id="cta-download-mac"

58

href="https://github.com/aaronrene/overseer-kit/releases/download/v1.0.0-rc.1/INSTALL-AND-ROLLBACK.md">Install v1.0.0-rc.1</a>

59

60

<a href="https://github.com/aaronrene/overseer-kit">Clone on GitHub</a>

61

</p>

62

63

<a href="scenarios/index.html">Scenarios</a>

64

· <a href="docs.html">Docs</a>

65

· <a href="https://github.com/aaronrene/overseer-kit/releases/tag/v1.0.0-rc.1">Release</a>

</p>

</div>

<img src="assets/diagrams/honesty-loop.svg"

70

width="640"

71

height="560"

72

alt="Overseer honesty loop: freeze and independently review a plan, build it in phases, verify the result, and re-check findings until it passes">

</figure>

</div>

</section>

<img src="assets/diagrams/mechanical-check.svg"

82

width="448"

83

height="148"

84

alt="Mechanical check comparing a claim of DONE with on-disk evidence, passing only when the evidence matches">

</figure>

<p class="mech-check-kicker">The core workflow</p>

89

90

<summary>Technical detail</summary>

91

92

<p><strong>Two review boundaries for <code>ROADMAP</code>:</strong> challenge the frozen plan before build, then compare the completed implementation with that plan before <code>DONE</code>. A separate agent chat or human performs the judgment; Overseer provides the structure and durable record.</p>

93

<p class="mech-details-cmd-label">Current rc.1 continuity layer</p>

94

<pre class="mech-details-cmd"><code>ok -C . status --json

95

ok -C . next</code></pre>

96

<p class="mech-details-cmd-label">Publish the reviewed handoff</p>

97

<pre class="mech-details-cmd"><code>ok -C . next-write …</code></pre>

</div>

</details>

</div>

<h2>Mechanical check — the frozen plan against on-disk evidence</h2>

102

<p>Define what “done” means before the build: scope, phases, deliverables, files, test exits, or project-owned checks. Review that plan independently, then compare the completed work with the accepted freeze instead of trusting the builder’s summary.</p>

</div>

</aside>

</div>

<h2>Review before build</h2>

112

113

<li><strong>Freeze the plan</strong> — write the intended outcome, phases, outputs, and acceptance evidence in <code>ROADMAP</code> before implementation starts.</li>

114

<li><strong>Challenge it independently</strong> — give the freeze to a separate agent chat or human reviewer with no incentive to approve it.</li>

115

<li><strong>Loop on findings</strong> — revise and re-review until the plan is clear enough to build without guesswork.</li>

</ul>

</div>

</article>

</svg>

</div>

<h2>Roadmap · Handover · Phases</h2>

133

134

<li><strong>ROADMAP</strong> — the phase board: what is planned, frozen, building, under review, or done.</li>

135

<li><strong>HANDOVER</strong> — the session baton: what landed, what remains true, and what the next session should do.</li>

136

<li><strong>Phases</strong> — turn an accepted plan into bounded slices with explicit outputs and checks.</li>

137

<li><strong>Continuity</strong> — the current CLI binds NEXT to the repository and revision so the right work reaches the right session.</li>

</ul>

</div>

</article>

</div>

</div>

</section>

<p class="section-kicker">The failure mode</p>

148

<h2>Why governance honesty matters</h2>

149

<p class="section-lede">AI-assisted work breaks down at the boundaries between planning, building, review, and the next session.</p>

</header>

<li>

<span class="pain-label">Amnesia</span>

154

<p>Each new chat re-derives context from scratch.</p>

155

</li>

156

<li>

157

<span class="pain-label">Self-approval</span>

158

<p>The same builder declares its own plan or implementation complete.</p>

159

</li>

160

<li>

161

<span class="pain-label">Silent drift</span>

162

<p>A handoff outlives the branch or revision that produced it.</p>

163

</li>

164

<li>

165

<span class="pain-label">Skipped checkpoints</span>

166

<p>A plausible summary replaces evidence and expensive mistakes surface late.</p>

167

</li>

168

</ul>

169

<p class="problem-close"><span class="problem-close-lead">Overseer Kit makes shortcuts visible before work advances</span> — by keeping the plan, reviews, phase state, evidence, and next handoff explicit.</p>

</section>

<h2>How it works</h2>

176

<p class="section-lede">Lock the plan, challenge it independently, build accepted phases, then verify the implementation before DONE.</p>

</header>

<h3>Lock and challenge the plan</h3>

183

<p>Write what will be built, how it will be phased, and what evidence will count. Freeze it, then have a separate agent chat or human reviewer try to find gaps.</p>

</div>

</li>

<h3>Build in bounded phases</h3>

190

<p>Implement only the accepted scope. Each phase carries declared outputs and project-owned checks so later sessions do not have to reconstruct intent.</p>

</div>

</li>

<h3>Review the completed build</h3>

197

<p>Compare the implementation and its evidence with the frozen plan. Resolve findings and re-check before marking the phase complete.</p>

</div>

</li>

<h3>Hand over the truth</h3>

204

<p>Update ROADMAP and HANDOVER to match what actually landed. The rc.1 CLI then keeps the next task bound to the correct repository and revision.</p>

</div>

</li>

</ol>

</section>

<h2>Structure at a glance</h2>

212

<p>The original diagrams show the operating model: living documents, explicit reviews, phased work, project evidence, and a clean handoff to the next session.</p>

213

214

215

<figcaption>Each work lane pairs a ROADMAP phase board with a HANDOVER session baton. Keep lanes few and meaningful.</figcaption>

216

217

218

<li>Single-lane default: ROADMAP ↔ HANDOVER</li>

219

<li>Optional multi-lane: each work stream gets its own living-document pair</li>

</ul>

</figure>

<figcaption>Version control supports the governance work in the background. Git-only is complete; Muse authority and a controlled GitHub mirror are optional repository choices.</figcaption>

225

226

227

<li>git-only — permanent mode; no Muse required</li>

228

<li>muse+git-mirror — Muse authority + controlled GitHub mirror</li>

229

<li>muse-only — Muse authority; no GitHub mirror</li>

</ul>

</figure>

<figcaption>Start with living documents and plan review. Add project-owned checks and stronger separation of review when the work needs them.</figcaption>

235

236

237

<li>Baseline — ROADMAP, HANDOVER, frozen plan, and independent review</li>

238

<li>Project checks — tests, files, hashes, diffs, or domain scripts</li>

239

<li>Separation — an independent completed-build review before DONE</li>

</ul>

</figure>

<figcaption>The kit supplies the governance pattern and living documents. Each project supplies its own runtime, tests, domain checks, and product decisions.</figcaption>

245

246

247

<li>Kit → configuration + ROADMAP + HANDOVER + review pattern</li>

248

<li>Projects → implementation, tests, domain checks, and user experience</li>

</ul>

</figure>

</section>

<h2>Get started</h2>

<p>This site is <strong>informational</strong> and does not run Overseer. Install the reviewed prerelease, initialize an authorized repository, then use the governance loop with the agent tools and reviewers you already trust.</p>

256

257

258

<h3>Path 1 — Install and initialize <span class="path-badge">start here</span></h3>

259

<ol>

260

<li>Follow the reviewed <strong>v1.0.0-rc.1</strong> <code>INSTALL-AND-ROLLBACK.md</code> guide.</li>

261

<li>Set <code>PROJECT_ROOT</code> to an existing <code>Git</code> checkout you are authorized to initialize.</li>

262

<li>Run <code>./cli/ok</code> with <code>init --vcs git</code> and the required <code>repository name and context</code>. Existing ROADMAP and HANDOVER files are preserved.</li>

263

<li>Use the repository-bound launcher to inspect status and carry the reviewed next task between sessions.</li>

264

</ol>

265

<p class="cta-honesty">Git-only is a complete ongoing mode. The governance workflow does not require Muse, a hosted service, or a new agent product.</p>

</article>

<h3>Path 2 — Freeze and review the <code>plan</code></h3>

270

<ol>

271

<li>Write the goal, scope, phases, outputs, and acceptance evidence in <code>ROADMAP</code>.</li>

272

<li>Freeze the plan with the <a href="https://github.com/aaronrene/overseer-kit/blob/main/README.md#the-governance-loop" id="local-console-loopback">governance loop</a>, then give it to a separate agent chat or human reviewer.</li>

273

<li>Resolve <code>cited findings</code> and <code>re-review</code> until the plan is safe to treat as build input.</li>

274

<li>Record the accepted state so later phases do not silently reinterpret it.</li>

</ol>

</article>

<h3>Path 3 — Build, verify, and hand over</h3>

280

<ol>

281

<li>Build only the accepted <code>phases</code> and run <code>project checks</code>; then have a separate reviewer compare the implementation and evidence with the frozen plan.</li>

282

<li>After findings clear, update ROADMAP and HANDOVER together and publish the next reviewed task.</li>

</ol>

</article>

<p class="bound-honesty"><em>Overseer supplies the rails and durable state. It does not run agents, appoint the independent reviewer, decide that work is good, or merge code.</em></p>

287

<p>Operator detail:

288

<a href="https://github.com/aaronrene/overseer-kit/releases/download/v1.0.0-rc.1/INSTALL-AND-ROLLBACK.md">Installation and rollback</a>

289

· Release index: <a href="https://github.com/aaronrene/overseer-kit/releases/tag/v1.0.0-rc.1">v1.0.0-rc.1</a>

290

· Git guide:

291

<a href="https://github.com/aaronrene/overseer-kit/blob/main/docs/GIT-ONLY-QUICKSTART.md">Git-only quickstart</a></p>

</section>

</div>

<h2 id="musehub-heading">Optional history with MuseHub</h2>

301

<p>The honesty loop works in <code>Git-only</code> mode. When a repository benefits from Muse-backed history, Muse can become its explicit authority with or without a controlled GitHub mirror. That storage choice supports the workflow; it does not define it.</p>

302

303

<a href="#diagram-regimes">See version-control options</a>

304

· Adoption guide:

305

<code>docs/MIGRATE-EXISTING-REPO.md</code>

</p>

</div>

</div>

</section>

<h2>Where to go next</h2>

313

<p>This site explains the governance workflow and the bounded rc.1 CLI that carries its handoffs. Planning, building, and review stay in your existing tools.</p>

<h3>GitHub</h3>

<p><a href="https://github.com/aaronrene/overseer-kit">overseer-kit</a> — <code>source</code>, living docs, review patterns, issues, and release history.</p>

</div>

· <a href="https://github.com/aaronrene/overseer-kit/blob/main/docs/CONSUMER-ADAPTER-PATTERN.md">Adapter pattern</a>

323

· <a href="https://github.com/aaronrene/overseer-kit/blob/main/docs/GIT-ONLY-QUICKSTART.md">Quickstart</a></p>

</div>

<h3>Release</h3>

<p>After reviewing <code>v1.0.0-rc.1</code>:

328

<a href="https://github.com/aaronrene/overseer-kit/releases/tag/v1.0.0-rc.1">Open the release</a>

329

— see <a href="#console-access">Get started</a>.</p>

</div>

<h3>Scenarios</h3>

<p><a href="scenarios/index.html">Scenario gallery</a> — the original job flows, clearly labeled as examples.</p>

</div>

</div>

<span class="funnel-step" id="funnel-github">Freeze + review plan</span>

338

339

<span class="funnel-step" id="funnel-kit">Build in phases</span>

340

341

<span class="funnel-step" id="funnel-musehub">Verify before DONE</span>

</div>

</section>

<h2>Scenarios</h2>

<p>See how the same plan-review, phased-build, and completion-review loop applies to software, media, research, finance, and classrooms.</p>

348

<p><a class="btn btn-secondary" href="scenarios/index.html">Open the scenario gallery →</a></p>

</section>

</main>

<p>

<a href="https://github.com/aaronrene/overseer-kit/blob/main/LICENSE">MIT open source</a>

355

· <a href="https://github.com/aaronrene/overseer-kit/blob/main/SECURITY.md">Security</a>

356

</p>

357

<p class="footer-tagline">🆗 Overseer Kit — Honesty for Agents.</p>

358

</footer>

359

</body>

360

</html>

1	<!DOCTYPE html>
2	<html lang="en" data-theme="dark">
3	<head>
4	<meta charset="utf-8">
5	<meta name="viewport" content="width=device-width, initial-scale=1">
6	<meta name="description" content="Overseer Kit — honesty for agents through reviewed plans, phased work, verified completion, and durable handoffs.">
7	<title>Overseer Kit — Honesty for Agents</title>
8	<link rel="icon" href="assets/favicon.ico" sizes="any">
9	<link rel="icon" type="image/png" href="assets/favicon-32.png" sizes="32x32">
10	<link rel="apple-touch-icon" href="assets/apple-touch-icon.png">
11	<link rel="stylesheet" href="assets/style.css">
12	<script src="assets/theme.js" defer></script>
13	</head>
14	<body>
15	<header class="site-header">
16	<nav>
17	<a class="brand" href="index.html" aria-label="Overseer Kit home">
18	<span class="logo-mark" aria-hidden="true">OK</span>
19	<span class="brand-name">Overseer Kit</span>
20	</a>
21	<div class="nav-links">
22	<a href="#how-it-works">How it works</a>
23	<a href="#console-access">Get started</a>
24	<a href="scenarios/index.html">Scenarios</a>
25	<a href="docs.html">Docs</a>
26	<button type="button" id="theme-toggle" class="theme-toggle" aria-label="Switch to light mode" title="Light / dark">
27	<span class="theme-icon theme-icon-moon" aria-hidden="true">☾</span>
28	<span class="theme-icon theme-icon-sun" aria-hidden="true">☀</span>
29	</button>
30	</div>
31	</nav>
32	</header>
33
34	<main>
35	<section id="hero" class="hero">
36	<div class="hero-plane" aria-hidden="true"></div>
37	<div class="hero-inner">
38	<div class="hero-copy">
39	<h1>Honesty for Agents.</h1>
40	<p class="lead">Freeze the plan. Challenge it independently. Build in phases. Review the result before anyone marks it DONE.</p>
41	<p class="sublead">ROADMAP holds the plan. HANDOVER carries the baton between sessions. Overseer Kit helps teams keep both honest from first review through final verification.</p>
42
43	<div class="hero-terminal" role="region" aria-label="Overseer plan, build, review, and handover example">
44	<div class="hero-terminal-chrome" aria-hidden="true">
45	<span class="hero-terminal-dot"></span>
46	<span class="hero-terminal-dot"></span>
47	<span class="hero-terminal-dot"></span>
48	<span class="hero-terminal-title">overseer — honesty loop</span>
49	</div>
50	<pre class="hero-terminal-body"><code><span class="term-prompt">01</span> <span class="term-cmd">PLAN</span> <span class="term-flag">freeze · challenge</span> <span class="term-str"></span>
51	<span class="term-out">independent review · revise until clear</span>
52	<span class="term-prompt">02</span> <span class="term-cmd">BUILD</span> <span class="term-flag">phases · checks</span> <span class="term-str"></span>
53	<span class="term-ok">VERIFY against freeze · HANDOVER truth</span> <span class="term-cursor" aria-hidden="true"></span></code></pre>
54	</div>
55
56	<p class="hero-foot-links">
57	<a id="cta-download-mac"
58	href="https://github.com/aaronrene/overseer-kit/releases/download/v1.0.0-rc.1/INSTALL-AND-ROLLBACK.md">Install v1.0.0-rc.1</a>
59	<span class="hero-foot-sep" aria-hidden="true">·</span>
60	<a href="https://github.com/aaronrene/overseer-kit">Clone on GitHub</a>
61	</p>
62	<p class="tertiary-links">
63	<a href="scenarios/index.html">Scenarios</a>
64	· <a href="docs.html">Docs</a>
65	· <a href="https://github.com/aaronrene/overseer-kit/releases/tag/v1.0.0-rc.1">Release</a>
66	</p>
67	</div>
68	<figure class="hero-visual">
69	<img src="assets/diagrams/honesty-loop.svg"
70	width="640"
71	height="560"
72	alt="Overseer honesty loop: freeze and independently review a plan, build it in phases, verify the result, and re-check findings until it passes">
73	</figure>
74	</div>
75	</section>
76
77	<section id="kit-basics" class="band-kit-basics" aria-label="Plan review, build verification, and living docs">
78	<div class="kit-basics-inner">
79	<aside class="mech-check-strip" id="mechanical-check" aria-label="Mechanical check">
80	<figure class="mech-check-visual">
81	<img src="assets/diagrams/mechanical-check.svg"
82	width="448"
83	height="148"
84	alt="Mechanical check comparing a claim of DONE with on-disk evidence, passing only when the evidence matches">
85	</figure>
86	<div class="mech-check-copy">
87	<div class="mech-check-kicker-row">
88	<p class="mech-check-kicker">The core workflow</p>
89	<details class="mech-check-details">
90	<summary>Technical detail</summary>
91	<div class="mech-details-body">
92	<p><strong>Two review boundaries for <code>ROADMAP</code>:</strong> challenge the frozen plan before build, then compare the completed implementation with that plan before <code>DONE</code>. A separate agent chat or human performs the judgment; Overseer provides the structure and durable record.</p>
93	<p class="mech-details-cmd-label">Current rc.1 continuity layer</p>
94	<pre class="mech-details-cmd"><code>ok -C . status --json
95	ok -C . next</code></pre>
96	<p class="mech-details-cmd-label">Publish the reviewed handoff</p>
97	<pre class="mech-details-cmd"><code>ok -C . next-write …</code></pre>
98	</div>
99	</details>
100	</div>
101	<h2>Mechanical check — the frozen plan against on-disk evidence</h2>
102	<p>Define what “done” means before the build: scope, phases, deliverables, files, test exits, or project-owned checks. Review that plan independently, then compare the completed work with the accepted freeze instead of trusting the builder’s summary.</p>
103	</div>
104	</aside>
105	<div class="kit-basics-grid">
106	<article class="kit-basics-panel">
107	<div class="kit-basics-icon" aria-hidden="true">
108	<img src="assets/ok-mark.svg" width="64" height="64" alt="">
109	</div>
110	<div class="kit-basics-copy">
111	<h2>Review before build</h2>
112	<ul class="kit-basics-list">
113	<li><strong>Freeze the plan</strong> — write the intended outcome, phases, outputs, and acceptance evidence in <code>ROADMAP</code> before implementation starts.</li>
114	<li><strong>Challenge it independently</strong> — give the freeze to a separate agent chat or human reviewer with no incentive to approve it.</li>
115	<li><strong>Loop on findings</strong> — revise and re-review until the plan is clear enough to build without guesswork.</li>
116	</ul>
117	</div>
118	</article>
119	<article class="kit-basics-panel">
120	<div class="kit-basics-icon kit-basics-icon-docs" aria-hidden="true">
121	<svg xmlns="http://www.w3.org/2000/svg" width="78" height="78" viewBox="8 12 84 72" focusable="false">
122	<rect x="14" y="18" width="40" height="52" rx="4" fill="none" stroke="#7ec8ff" stroke-width="3"/>
123	<path d="M24 34h20M24 46h20M24 58h12" fill="none" stroke="#7ec8ff" stroke-width="2.5" stroke-linecap="round"/>
124	<path d="M24 34l3.5 3.5 7-8" fill="none" stroke="#5cb88a" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"/>
125	<path d="M68 28a18 18 0 0 1 0 36" fill="none" stroke="#e8a35c" stroke-width="3" stroke-linecap="round"/>
126	<path d="M68 64a18 18 0 0 1 0-36" fill="none" stroke="#e85d4c" stroke-width="3" stroke-linecap="round" stroke-dasharray="4 5"/>
127	<path d="M78 22l6 6-6 6" fill="none" stroke="#e8a35c" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"/>
128	<path d="M58 70l-6-6 6-6" fill="none" stroke="#e85d4c" stroke-width="2.5" stroke-linecap="round" stroke-linejoin="round"/>
129	</svg>
130	</div>
131	<div class="kit-basics-copy">
132	<h2>Roadmap · Handover · Phases</h2>
133	<ul class="kit-basics-list">
134	<li><strong>ROADMAP</strong> — the phase board: what is planned, frozen, building, under review, or done.</li>
135	<li><strong>HANDOVER</strong> — the session baton: what landed, what remains true, and what the next session should do.</li>
136	<li><strong>Phases</strong> — turn an accepted plan into bounded slices with explicit outputs and checks.</li>
137	<li><strong>Continuity</strong> — the current CLI binds NEXT to the repository and revision so the right work reaches the right session.</li>
138	</ul>
139	</div>
140	</article>
141	</div>
142	</div>
143	</section>
144
145	<section id="problem" class="band-problem">
146	<header class="section-intro">
147	<p class="section-kicker">The failure mode</p>
148	<h2>Why governance honesty matters</h2>
149	<p class="section-lede">AI-assisted work breaks down at the boundaries between planning, building, review, and the next session.</p>
150	</header>
151	<ul class="pain-grid">
152	<li>
153	<span class="pain-label">Amnesia</span>
154	<p>Each new chat re-derives context from scratch.</p>
155	</li>
156	<li>
157	<span class="pain-label">Self-approval</span>
158	<p>The same builder declares its own plan or implementation complete.</p>
159	</li>
160	<li>
161	<span class="pain-label">Silent drift</span>
162	<p>A handoff outlives the branch or revision that produced it.</p>
163	</li>
164	<li>
165	<span class="pain-label">Skipped checkpoints</span>
166	<p>A plausible summary replaces evidence and expensive mistakes surface late.</p>
167	</li>
168	</ul>
169	<p class="problem-close"><span class="problem-close-lead">Overseer Kit makes shortcuts visible before work advances</span> — by keeping the plan, reviews, phase state, evidence, and next handoff explicit.</p>
170	</section>
171
172	<section id="how-it-works" class="band-how">
173	<header class="section-intro">
174	<p class="section-kicker">The loop</p>
175	<h2>How it works</h2>
176	<p class="section-lede">Lock the plan, challenge it independently, build accepted phases, then verify the implementation before DONE.</p>
177	</header>
178	<ol class="loop-steps">
179	<li class="loop-step">
180	<span class="loop-index" aria-hidden="true">01</span>
181	<div class="loop-body">
182	<h3>Lock and challenge the plan</h3>
183	<p>Write what will be built, how it will be phased, and what evidence will count. Freeze it, then have a separate agent chat or human reviewer try to find gaps.</p>
184	</div>
185	</li>
186	<li class="loop-step">
187	<span class="loop-index" aria-hidden="true">02</span>
188	<div class="loop-body">
189	<h3>Build in bounded phases</h3>
190	<p>Implement only the accepted scope. Each phase carries declared outputs and project-owned checks so later sessions do not have to reconstruct intent.</p>
191	</div>
192	</li>
193	<li class="loop-step">
194	<span class="loop-index" aria-hidden="true">03</span>
195	<div class="loop-body">
196	<h3>Review the completed build</h3>
197	<p>Compare the implementation and its evidence with the frozen plan. Resolve findings and re-check before marking the phase complete.</p>
198	</div>
199	</li>
200	<li class="loop-step">
201	<span class="loop-index" aria-hidden="true">04</span>
202	<div class="loop-body">
203	<h3>Hand over the truth</h3>
204	<p>Update ROADMAP and HANDOVER to match what actually landed. The rc.1 CLI then keeps the next task bound to the correct repository and revision.</p>
205	</div>
206	</li>
207	</ol>
208	</section>
209
210	<section id="structure">
211	<h2>Structure at a glance</h2>
212	<p>The original diagrams show the operating model: living documents, explicit reviews, phased work, project evidence, and a clean handoff to the next session.</p>
213
214	<figure class="diagram-figure" id="diagram-lanes">
215	<figcaption>Each work lane pairs a ROADMAP phase board with a HANDOVER session baton. Keep lanes few and meaningful.</figcaption>
216	<img src="assets/diagrams/lanes.svg" alt="Single-lane ROADMAP and HANDOVER pair with an optional multi-lane layout for separate streams of work" width="720" height="280">
217	<ul class="diagram-fallback">
218	<li>Single-lane default: ROADMAP ↔ HANDOVER</li>
219	<li>Optional multi-lane: each work stream gets its own living-document pair</li>
220	</ul>
221	</figure>
222
223	<figure class="diagram-figure" id="diagram-regimes">
224	<figcaption>Version control supports the governance work in the background. Git-only is complete; Muse authority and a controlled GitHub mirror are optional repository choices.</figcaption>
225	<img src="assets/diagrams/regimes.svg" alt="Version-control options from git-only to Muse with GitHub mirror to Muse-only" width="640" height="320">
226	<ul class="diagram-fallback">
227	<li>git-only — permanent mode; no Muse required</li>
228	<li>muse+git-mirror — Muse authority + controlled GitHub mirror</li>
229	<li>muse-only — Muse authority; no GitHub mirror</li>
230	</ul>
231	</figure>
232
233	<figure class="diagram-figure" id="diagram-layers">
234	<figcaption>Start with living documents and plan review. Add project-owned checks and stronger separation of review when the work needs them.</figcaption>
235	<img src="assets/diagrams/layers.svg" alt="Three safety layers: baseline governance and freeze review, optional domain checkpoints, and optional dual-control records" width="420" height="280">
236	<ul class="diagram-fallback">
237	<li>Baseline — ROADMAP, HANDOVER, frozen plan, and independent review</li>
238	<li>Project checks — tests, files, hashes, diffs, or domain scripts</li>
239	<li>Separation — an independent completed-build review before DONE</li>
240	</ul>
241	</figure>
242
243	<figure class="diagram-figure" id="diagram-kit-consumer">
244	<figcaption>The kit supplies the governance pattern and living documents. Each project supplies its own runtime, tests, domain checks, and product decisions.</figcaption>
245	<img src="assets/diagrams/kit-consumer.svg" alt="Overseer Kit feeding governance and living documents into projects that retain their own domain checks and product runtime" width="760" height="260">
246	<ul class="diagram-fallback">
247	<li>Kit → configuration + ROADMAP + HANDOVER + review pattern</li>
248	<li>Projects → implementation, tests, domain checks, and user experience</li>
249	</ul>
250	</figure>
251	</section>
252
253	<section id="console-access">
254	<h2>Get started</h2>
255	<p>This site is <strong>informational</strong> and does not run Overseer. Install the reviewed prerelease, initialize an authorized repository, then use the governance loop with the agent tools and reviewers you already trust.</p>
256
257	<article class="path-card path-preferred" id="path-1">
258	<h3>Path 1 — Install and initialize <span class="path-badge">start here</span></h3>
259	<ol>
260	<li>Follow the reviewed <strong>v1.0.0-rc.1</strong> <code>INSTALL-AND-ROLLBACK.md</code> guide.</li>
261	<li>Set <code>PROJECT_ROOT</code> to an existing <code>Git</code> checkout you are authorized to initialize.</li>
262	<li>Run <code>./cli/ok</code> with <code>init --vcs git</code> and the required <code>repository name and context</code>. Existing ROADMAP and HANDOVER files are preserved.</li>
263	<li>Use the repository-bound launcher to inspect status and carry the reviewed next task between sessions.</li>
264	</ol>
265	<p class="cta-honesty">Git-only is a complete ongoing mode. The governance workflow does not require Muse, a hosted service, or a new agent product.</p>
266	</article>
267
268	<article class="path-card" id="path-2">
269	<h3>Path 2 — Freeze and review the <code>plan</code></h3>
270	<ol>
271	<li>Write the goal, scope, phases, outputs, and acceptance evidence in <code>ROADMAP</code>.</li>
272	<li>Freeze the plan with the <a href="https://github.com/aaronrene/overseer-kit/blob/main/README.md#the-governance-loop" id="local-console-loopback">governance loop</a>, then give it to a separate agent chat or human reviewer.</li>
273	<li>Resolve <code>cited findings</code> and <code>re-review</code> until the plan is safe to treat as build input.</li>
274	<li>Record the accepted state so later phases do not silently reinterpret it.</li>
275	</ol>
276	</article>
277
278	<article class="path-card" id="path-3">
279	<h3>Path 3 — Build, verify, and hand over</h3>
280	<ol>
281	<li>Build only the accepted <code>phases</code> and run <code>project checks</code>; then have a separate reviewer compare the implementation and evidence with the frozen plan.</li>
282	<li>After findings clear, update ROADMAP and HANDOVER together and publish the next reviewed task.</li>
283	</ol>
284	</article>
285
286	<p class="bound-honesty"><em>Overseer supplies the rails and durable state. It does not run agents, appoint the independent reviewer, decide that work is good, or merge code.</em></p>
287	<p>Operator detail:
288	<a href="https://github.com/aaronrene/overseer-kit/releases/download/v1.0.0-rc.1/INSTALL-AND-ROLLBACK.md">Installation and rollback</a>
289	· Release index: <a href="https://github.com/aaronrene/overseer-kit/releases/tag/v1.0.0-rc.1">v1.0.0-rc.1</a>
290	· Git guide:
291	<a href="https://github.com/aaronrene/overseer-kit/blob/main/docs/GIT-ONLY-QUICKSTART.md">Git-only quickstart</a></p>
292	</section>
293
294	<section id="musehub" class="musehub-band" aria-labelledby="musehub-heading">
295	<div class="musehub-band-inner">
296	<div class="musehub-brand">
297	<img class="musehub-logo" src="assets/musehub-logo.svg" width="360" height="80" alt="MuseHub">
298	</div>
299	<div class="musehub-copy">
300	<h2 id="musehub-heading">Optional history with MuseHub</h2>
301	<p>The honesty loop works in <code>Git-only</code> mode. When a repository benefits from Muse-backed history, Muse can become its explicit authority with or without a controlled GitHub mirror. That storage choice supports the workflow; it does not define it.</p>
302	<p class="musehub-links">
303	<a href="#diagram-regimes">See version-control options</a>
304	· Adoption guide:
305	<code>docs/MIGRATE-EXISTING-REPO.md</code>
306	</p>
307	</div>
308	</div>
309	</section>
310
311	<section id="next-steps">
312	<h2>Where to go next</h2>
313	<p>This site explains the governance workflow and the bounded rc.1 CLI that carries its handoffs. Planning, building, and review stay in your existing tools.</p>
314	<div class="card-grid suite-grid">
315	<div class="card">
316	<h3>GitHub</h3>
317	<p><a href="https://github.com/aaronrene/overseer-kit">overseer-kit</a> — <code>source</code>, living docs, review patterns, issues, and release history.</p>
318	</div>
319	<div class="card">
320	<h3>Docs</h3>
321	<p><a href="docs.html">Docs on this site</a>
322	· <a href="https://github.com/aaronrene/overseer-kit/blob/main/docs/CONSUMER-ADAPTER-PATTERN.md">Adapter pattern</a>
323	· <a href="https://github.com/aaronrene/overseer-kit/blob/main/docs/GIT-ONLY-QUICKSTART.md">Quickstart</a></p>
324	</div>
325	<div class="card">
326	<h3>Release</h3>
327	<p>After reviewing <code>v1.0.0-rc.1</code>:
328	<a href="https://github.com/aaronrene/overseer-kit/releases/tag/v1.0.0-rc.1">Open the release</a>
329	— see <a href="#console-access">Get started</a>.</p>
330	</div>
331	<div class="card">
332	<h3>Scenarios</h3>
333	<p><a href="scenarios/index.html">Scenario gallery</a> — the original job flows, clearly labeled as examples.</p>
334	</div>
335	</div>
336	<div class="funnel" id="funnel" aria-label="Honesty loop">
337	<span class="funnel-step" id="funnel-github">Freeze + review plan</span>
338	<span class="funnel-arrow">→</span>
339	<span class="funnel-step" id="funnel-kit">Build in phases</span>
340	<span class="funnel-arrow">→</span>
341	<span class="funnel-step" id="funnel-musehub">Verify before DONE</span>
342	</div>
343	</section>
344
345	<section id="scenarios">
346	<h2>Scenarios</h2>
347	<p>See how the same plan-review, phased-build, and completion-review loop applies to software, media, research, finance, and classrooms.</p>
348	<p><a class="btn btn-secondary" href="scenarios/index.html">Open the scenario gallery →</a></p>
349	</section>
350	</main>
351
352	<footer class="site-footer">
353	<p>
354	<a href="https://github.com/aaronrene/overseer-kit/blob/main/LICENSE">MIT open source</a>
355	· <a href="https://github.com/aaronrene/overseer-kit/blob/main/SECURITY.md">Security</a>
356	</p>
357	<p class="footer-tagline">🆗 Overseer Kit — Honesty for Agents.</p>
358	</footer>
359	</body>
360	</html>