Skip to content

Events 137+138: gate signal quality + v2.0 epistemic engine#93

Merged
junjslee merged 2 commits into
masterfrom
event-138-epistemic-engine-v2
Jun 10, 2026
Merged

Events 137+138: gate signal quality + v2.0 epistemic engine#93
junjslee merged 2 commits into
masterfrom
event-138-epistemic-engine-v2

Conversation

@junjslee

Copy link
Copy Markdown
Owner

What this is

Two events, one arc: the Event 137 audit found the kernel checking form while its compounding loop sat dead and its own falsifiability condition (E1) had fired unnoticed; Event 138 rebuilds the center as the v2.0 Epistemic Engine per operator directive and the 2023–2026 research record.

Event 137 — gate signal quality (audit-driven fixes)

  • Read-only command exemption ahead of cascade Trigger 2 (positive-system allowlist; redirection / substitution / mutating heads disqualify). Root cause of alarm fatigue: 18.8k ops classified high-impact drove this repo to advisory mode and 57.9% authoring vs the 80% floor.
  • SessionStart injection bounded: NEXT_STEPS.md capped at an 8KB head with truncation marker (live: 233KB → 10KB per invocation).
  • E1 self-falsification mechanized: SessionStart digest + episteme report § Protocol Synthesis evaluate FALSIFIABILITY_CONDITIONS § E1 against live state. E1 status → FIRED (0 protocols, ~49 days); README marks the compounding arm per E1's prescribed action.

Event 138 — v2.0 Epistemic Engine (docs/DESIGN_V2_0_EPISTEMIC_ENGINE.md)

Division of labor from the research record: deterministic structure guarantees the epistemic work happened; model judgment — factored, evidence-anchored, in a context that never sees the draft — checks it was real.

  • skills/custom/epistemic-interrogation/ — the senior-researcher protocol: decompose into tiered claims, factored verification of load-bearing claims (CoVe, arXiv 2309.11495), argued opposition (debate, arXiv 2402.06782), weakest link, pre-committed disconfirmation, verdict artifact.
  • core/hooks/_interrogation.py — floors only: freshness via max(ts, mtime), external-evidence requirement (self-correction without external signal degrades accuracy, arXiv 2310.01798), verdict consistency; stop fails closed.
  • Guard accepts a fresh verdict as an alternative satisfier (v1 surface path fully preserved); advisory text converted to factual statements per the Claude Code hooks doctrine; audit records carry source for the E3 falsifiability measurement.
  • Lesson synthesis: verified interrogations with non-null lessons emit context-scoped protocols on success — E1's compounding claim finally has a live source; e2e test covers interrogation → protocol → guidance.
  • New falsifiability conditions E3/E4/E5 with measurement methods; REFERENCES.md carries the v2 empirical record.

Verification

  • 1298 tests + 54 subtests green (33 new in Event 137, 24 new in Event 138; zero regressions).
  • Live smoke: session context 233KB → ~10KB with E1 FIRED line; episteme report renders § Protocol Synthesis; read-only exemption verified against adversarial bypass shapes (redirection into sensitive paths, command substitution, mixed pipelines, xargs, git mutating subcommands — all still fire).

Out of scope (logged in NEXT_STEPS / deferred discoveries)

i18n README parity for the v2 reframe; web/ landing copy; imperative-tone pass on remaining hooks; architecture_v2 diagram regen.

junjslee added 2 commits June 9, 2026 21:28
Event 137 — audit-driven fixes to the loops that were defeating the
kernel's own thesis:

- cascade detector: positive-system read-only command exemption ahead
  of Trigger 2 — wc/ls/grep on sensitive paths no longer classify as
  cascade:architectural. Root cause of alarm fatigue: 18.8k ops
  classified high-impact drove the kernel's own repo to advisory mode
  and 57.9% authoring vs the 80% floor.
- session_context: bound NEXT_STEPS.md injection to an 8KB head with a
  truncation marker (live: 233KB -> 10KB per hook invocation).
- E1 self-falsification: SessionStart digest and episteme report
  (new Protocol Synthesis section, --framework-dir override) evaluate
  FALSIFIABILITY_CONDITIONS § E1 against live framework state. E1 is
  FIRED (0 protocols, ~49 days); kernel doc status updated and README
  marks the compounding arm aspirational per E1's prescribed action.

1274 tests + 54 subtests green (33 new: 17 exemption incl. adversarial
bypass shapes, 11 session-context bounds/E1, 5 report E1).
…d verification, lesson synthesis

Event 138 — the product's center shifts from deterministic form-gates to
a senior-researcher epistemic engine, per operator directive and the
2023-2026 research record (DESIGN_V2_0_EPISTEMIC_ENGINE.md):

- epistemic-interrogation skill: decompose a load-bearing decision into
  tiered claims, verify load-bearing claims in a fresh context against
  external evidence (CoVe-factored), argue the opposition, name the
  weakest link, pre-commit disconfirmation, write a verdict artifact.
- core/hooks/_interrogation.py: deterministic floors only — freshness
  via max(ts, mtime) (fixes stale-at-birth), external-evidence
  requirement, verdict consistency (refuted load-bearing claim +
  proceed = contradiction; stop fails closed).
- reasoning_surface_guard: a fresh verdict is an alternative satisfier
  to the v1 surface for high-impact ops; advisory text converted to
  factual statements per the hooks doctrine; audit records carry
  source: surface|interrogation (E3 measurement).
- fence_synthesis: lesson synthesis on successful ops — non-null
  lessons from verified interrogations become context-scoped protocols
  (deduped by lesson hash), giving E1's compounding claim a live
  source; e2e test covers interrogation -> protocol -> guidance.
- Identity docs reframed (README lede, THE_WAY_TO_THINK § 5 division
  of labor, FALSIFIABILITY E3/E4/E5, REFERENCES v2 empirical record).

1298 tests + 54 subtests green (24 new).
@vercel

vercel Bot commented Jun 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
episteme Ready Ready Preview, Comment Jun 10, 2026 3:32am

@junjslee junjslee merged commit f7b4d79 into master Jun 10, 2026
5 checks passed
@junjslee junjslee deleted the event-138-epistemic-engine-v2 branch June 10, 2026 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant