By junjslee
Enforce an epistemic-posture development workflow for AI coding agents: structured reasoning, named failure modes, operator profiles, governance gates, and handoff artifacts. Bootstraps repositories with scaffold files, runs automated quality checks on file edits, blocks tools until rules pass, and orchestrates research-planning-implementation-review loops across sessions.
Update project memory docs so the next agent or session can resume cleanly.
Define and maintain structural layers, entity boundaries, invariants, and vocabulary so execution stays conceptually coherent.
Anchor work to real domain outcomes, user utility, and adoption metrics so the system delivers value beyond infrastructure.
Enforce operational governance, risk policy, promotion gates, and rollback readiness before high-impact changes.
Execute bounded implementation work with clear file ownership and a concrete verification plan.
Design safe unattended or long-running loops with explicit limits, checkpoints, and handoff artifacts.
Senior-researcher interrogation of a load-bearing decision or conclusion — decompose into claims, verify the load-bearing ones in a fresh context with external evidence, argue the opposition, name the weakest link, pre-commit disconfirmation, record the verdict artifact the episteme gate reads.
Update progress and next-step docs so the next agent or session can resume with minimal context loss.
Bootstrap a repository with the standard episteme scaffold and verify the core memory files exist.
Turn project requirements into a staged implementation plan with verification and handoff criteria.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
episteme is a way to think — 생각의 틀 — an epistemic engine that makes AI-assisted decisions earn their confidence before they land.
A five-stage cognitive practice — Frame → Decompose → Execute → Verify → Handoff — anchored in Kahneman's System-2 forcing, Dalio's Radical Transparency, Boyd's OODA Orientation, and Munger's Latticework of Mental Models. v2.0 delivers it as three layers. Cognition — the senior-researcher interrogation: decompose a load-bearing decision into tiered claims (
measured / cited / inferred / assumed), verify the load-bearing ones in a fresh context against external evidence, argue the strongest opposition, name the weakest link, pre-commit a disconfirmation. Structure — deterministic hooks that route decision shapes, validate the verdict artifact (astopverdict fails closed), and hard-block only genuinely destructive operations; the operator-signed Reasoning Surface (Ed25519, structurally out of the agent's reach) remains the operator-side framing artifact. Memory — lessons from verified interrogations become hash-chained, context-scoped protocols that resurface at the next matching decision. The division of labor is the research record's, not ours: models judging their own drafts get worse, form-checks are gameable by reasoning-shaped tokens, and only architectural constraint converts epistemic awareness into behavior.The MIRROR benchmark (arXiv 2604.19809) settled the empirical question: across 16 models from 8 labs and ~250,000 instances, "providing models with their own calibration scores produces no significant improvement; only architectural constraint is effective." Confident Failure Rate drops from 0.60 to 0.14 under external architectural constraint. The practice itself is the product. The artifacts under
core/andsrc/episteme/— the typed Reasoning Surface, the Append-Only Hash Chain, the Active-Guidance loop — are the Sovereign Cognitive Kernel that keeps the practice alive at frontier model strength, when vigilance-as-willpower fails. Posture over prompt.→
docs/THE_WAY_TO_THINK.md— the practice, operationalized.
See it in 60 seconds ↓ · Install ↓ · Why the file-system, not the prompt ↓ · Architecture & philosophy ↓ · Does it work? ↗

The practice in docs/THE_WAY_TO_THINK.md names six cognitive moves per high-impact decision — Core Question, distinction map, signal-vs-noise filter, because-chain, hypothesis-as-bet, disconfirmation conditions. Each move counters a specific named System-1 failure (question substitution, WYSIATI, anchoring, narrative fallacy, planning fallacy, overconfidence — Kahneman). A prompt can request these moves, but prompts are advisory: they live for one call, get skipped at deadline, and disappear from context. Frontier models comply on the surface and skip the moves underneath — fluently, confidently, and the operator stops checking. That is exactly the failure mode the practice is for.
Concrete example. You ask the agent: "Evaluate whether our retrieval-augmented memory system is actually improving response quality."
The agent treats your prompt as a measurement task. It pulls metrics from the last 30 days, compares with-memory vs without-memory response samples, finds a 7% positive lift on thumbs-up rate, writes a memo concluding "memory helps; keep shipping." You read it.
npx claudepluginhub junjslee/episteme --plugin epistemeRoute upstream epistemic deficits and evaluate execution-time risks — /attend (προσοχή: attention)
Thoughtbox observability, protocol enforcement, and CLI for Claude Code
Metacognitive advisor that monitors Claude Code and provides feedback
First Principles Framework (FPF) for structured reasoning using workflow command pattern. Implements ADI (Abduction-Deduction-Induction) cycle via propose-hypotheses workflow with fpf-agent for hypothesis generation, logical verification, empirical validation, and auditable decision-making. Includes utility commands for status, query, decay, actualize, and reset.
Structured thinking and multi-perspective deliberation tools
The operational layer for coding agents. Bookkeeping, validation, and flows that compound knowledge between sessions.