VIBEGUARD / LOCAL SIGNAL BOARD {{STATE_LABEL}}

See what happened after VibeGuard stepped in.

A first-win view for one local event stream: what was observed, what can be verified by order, what remains unresolved, and what to look at next.

scope{{SCOPE}} window{{PERIOD}} generated{{GENERATED_AT}}
FIRST WIN / HONEST READ

{{STORY_HEADLINE}}

{{STORY_BODY}}

Next action{{NEXT_ACTION}}

Evidence in two tiers

Headline evidence comes only from observe value --json.

VERIFIED ASSOCIATION

Time order in one non-empty session; not proof of cause.

Later build pass after intervention

{{VERIFIED_BUILD}}

{{VERIFIED_NOTE}}

OBSERVED SIGNALS

What the selected local event stream contains.

Follow-up after intervention

{{FOLLOW_UP}}

{{FOLLOW_NOTE}}

Sessions without later follow-up

{{UNRESOLVED}}

{{UNRESOLVED_NOTE}}

Observed hook overhead

{{OVERHEAD}}

{{OVERHEAD_NOTE}}

Friction, kept separate

OBSERVED FRICTION / NOT OUTCOME EVIDENCE
{{REPEATED}}sessions with repeated guardrail signals
{{SUPPRESSIONS}}suppressed guardrail signals
{{UNCORRELATABLE}}signals missing session/time correlation

{{FRICTION_NOTE}}

What this page cannot tell you

ESTIMATED / UNAVAILABLE

{{ESTIMATED_REASON}}

{{LIMITATIONS}}
BOUNDARY / BUILT-IN CHECK

A reproducible corpus is not a project result.

The built-in 5-positive/5-negative benchmark is a small reproducible corpus, not evidence of impact on your project.

Keep benchmark behavior checks separate from this local event-stream evidence.

Installation and health diagnostics

Secondary context for troubleshooting. Raw local output is shown only inside expandable details and is escaped before rendering.

Codex installation status
{{STATUS_OUT}}
{{STATUS_COMMAND}}
Hook health output
{{HEALTH_OUT}}
{{HEALTH_COMMAND}}
Trigger stats output
{{STATS_OUT}}
{{STATS_COMMAND}}
Observe-value command output
{{VALUE_OUT}}
{{VALUE_COMMAND}}