Distillery Knowledge Graph
Review & approval flow
A structured operator pass for the static graph workflow: rebuild, inspect the exported surfaces, review the research/parity evidence, and make an explicit approval decision rather than relying on memory and scattered files.
Review Stages
Follow these in order. Each stage names the command, the approval test, and the evidence to inspect.
<section class="panel">
<h2>Approval Checklist</h2>
<p class="hint">This checklist is stored locally in the browser: it helps the operator resume a review pass without pretending to be a shared workflow system yet.</p>
<div class="progress"><div id="progressFill"></div></div>
<div class="progress-note" id="progressNote"></div>
<div class="checklist" id="checklist"></div>
<div class="actions">
<div class="action">
<h3 class="ok">If clear</h3>
<p>Approve the current snapshot for the next commit, handoff, or release artifact set. The parity gate is clean when pending links, fuzzy matches, KG-only rows, and conflicts are all zero.</p>
</div>
<div class="action">
<h3 class="warn">If blocked</h3>
<p>Route back into the next ticket or file a focused follow-up instead of carrying hidden uncertainty forward. This page is meant to surface that boundary clearly.</p>
</div>
</div>
<div style="height:18px"></div>
<h2>Evidence Files</h2>
<p class="hint">The primary artifacts an operator should read when something looks off.</p>
<div class="evidence-grid" id="evidence"></div>
</section>
Parity Exceptions
Rows that still need manual interpretation before the parity gate can be treated as clean. An empty table is the desired steady state.
| KG row | Decision | Portal row | Conflict |
|---|
<section class="panel">
<h2>Open Research Tail</h2>
<p class="hint">A sample from the queue that still needs confidence or chronology work.</p>
<table>
<thead><tr><th>Subject</th><th>Type</th><th>Flag</th></tr></thead>
<tbody id="rescanTable"></tbody>
</table>
</section>
<section class="panel">
<h2>Stub Review Sample</h2>
<p class="hint">Low-event stubs that still need explicit expansion decisions.</p>
<table>
<thead><tr><th>Name</th><th>Status</th><th>Events</th><th>State</th></tr></thead>
<tbody id="stubTable"></tbody>
</table>
</section>
<section class="panel">
<h2>Quick Routes</h2>
<p class="hint">The exported pages an operator is expected to scan during review.</p>
<div class="link-grid" id="views"></div>
</section>