review queue
—
engine roll-up
axis A · pipeline-station status
| monitor | phase A | phase B | challenge | ||||||
|---|---|---|---|---|---|---|---|---|---|
| collector | chatter | weekly-research | interpret | review | compose | apply | curate | ||
Flow Quality _flow_quality
Per-module content state at the publish stage. Amber means at least one module came back empty without a traceable reason.
Flow quality data not yet generated.
KB Size / Republish _kb_size
Per-consumer published-KB byte-size compared run-over-run. A red light means the
committed output was byte-identical to the prior pipeline run — a sign stale outputs
were republished unchanged. Grey means dormant or unread; green means the KB changed.
Content Republish _content_republish
Every periodic dated series on every consumer (weekly briefs, compose/interpret/review,
apply, daily-verified, per-jurisdiction runs) compared newest-vs-prior after stripping the
metadata wrapper. A red light means the substantive body was republished under a new
date/issue (the AIM incident class). Amber is a verdict-echo watch — categorical fields
repeat but the prose is fresh. Green means clean.
axis B · reservoir vs surface
monitors (commons)
| monitor | reservoir | surface | delta | last published | safe-projection check |
|---|
consumers (engine-owned)
| consumer | reservoir | surface | delta | last published | safe-projection check |
|---|
jurisdiction completeness · advennt reservoir
axis C · applied vs published reconciliation
| monitor | cycle | patches applied | patches rejected | publication | reconciliation |
|---|
role accountability · plumbing vs role
by first-failed role
by likely fix-type
| monitor | module | status | first-failed role | likely fix | conf | evidence | refs |
|---|