insight-engine v0.1.21 — legend and update-path repair

Three defects, each of which alone required this release, plus a corpus-wide plain-English pass.

Defect 1 — the legend was false

The fixed reader-facing legend shipped at v0.1.20 stated that only the first three [N] situations can move. That is wrong. A claim that inherits its cap moves when the unverified thing it depends on is itself verified.

The legend therefore told readers not to spend a verification that would in fact have settled the claim. That is the false-closure failure the Architecture document gives as its reason for declining an [N] permanence suffix — so the legend committed, in every deliverable it produced, the error the suffix was refused in order to avoid. It also contradicted §4 of the document it implements.

The legend now carries the canonical five-situation definition in full: uncorroborated or contradicted; interested-party only; party-held and pending; inherited cap; permanently capped by design. It states which situations can move and how, and it states that value, framing, blame and forecasts made outside the systems map are routed rather than graded.

The legend is versioned behaviour. It appears verbatim in every full-pass deliverable, so its wording is now recorded in the version table whenever it changes.

Defect 2 — the update path was unguarded

track delegates re-grading to verify, and neither stated the permanent set. An operator following either text could lift a permanent [N] on loop dominance, lever effectiveness or tipping to [V] on new evidence. Both now carry the same invariant, worded identically. track's spine gains a field recording which of the five situations each [N] is in, which its update behaviour depends on.

Defect 3 — verify graded what should be routed

Irreducibly-open items were being marked rather than routed unmarked. Corrected.

Also

analyse Step 7 now requires each [N] to state its situation on its own line, because the legend promises it. Step 6 distinguishes a revisable judgement from an unmovable grade. render carries the map invariants and the legend requirement in its own text. The provocation page moves to v1.1 under its page-revision governance rule — the first time that rule has been used.

Plain-English pass

Roughly 190 figurative constructions were replaced across the engine, the public documents, the explainer scripts and the test record, against a protected list of technical terms kept for precision. This implements a standing instruction that had been applied to conversation but not to authored documents.

How these were found

Four adjudicators audited disjoint slices of the corpus concurrently under one identical rule set, then a reconciliation pass resolved their disagreements, corrected the canonical definition they had been given, and produced a single edit list. The concurrent design is what surfaced Defect 1: no single sequential reviewer saw both the legend and the architecture document, and the contradiction was only visible across that boundary.

The documents and the packaged legend re-converge here. v0.1.20's documents led the plugin for part of a day.

Install (Cowork)

Download insight-engine-0.1.21.plugin below, then Customize → Plugins → Add → Upload plugin. Uploading over an existing install replaces it in place.

insight-engine v0.1.20 — notation clarity and a ceiling correction

Notation clarity, and one correction to the specification.

The spec correction

The systems pass's cardinal rule caps behaviour, timing and prediction at [N]. The drop-in text that became this skill compressed that to "whether or when the system tips", which left loop dominance and lever effectiveness on a hedged "usually [N]" — while the reader-facing legend, the Guide and the Architecture document already promised a hard ceiling. The authoring text and the reader contract disagreed.

Step 5 now reads "capped at [N]" in both slots, and the ceiling sentence names all three items.

Nothing is lost by capping. Evidence bearing on a capped grade is graded where it is checkable — the loop's existence, a link, or an ordinary finding about a study — and travels with the routed question to the human at the gate. The change moves who applies the evidence, not whether it can be applied.

This was tested before it shipped. T-SM-005 seeded a case with the two strongest arguments for a lift: an in-case econometric decomposition asserting which loop dominates, and a glowing pilot evaluation of one lever. Two arms of five, shipped wording against repaired.

0 of 100 capped grades lifted, in either arm. The old permission was live in the text and dead in practice, so this is a consistency fix and it closed no observed leak. Runs attacked the bait's method rather than its conclusion — one noticing that a decomposition of a revenue series is not a decomposition of a decline — which confirms against runs, rather than against an argument, that the ceilings cost no information.

The clarity work

[N] is one symbol over five situations: uncorroborated after search; resting only on an interested party; awaiting a named document; inheriting a cap from an unverified dependency; or a judgement the method never grades higher by design. Only the first three move if you look harder. The fixed legend, the Guide, the Manual, the README and the Architecture document now all say so.

A tier on a causal-map link is now disclosed as grading the mechanism in general rather than this arrow in this case — the specification had been re-basing its own tier semantics between Step 4 and Step 5, on the exact boundary v0.1.19's fixed-tier rule polices.

Also: the analogy-capped [V3] records a named weakness; "calibration" stragglers that survived the v0.1.13 rename are cleared; the Guide and Manual no longer diverge; and the explainer scripts are corrected on joint assumption variation and on per-case probe selection.

What was considered and declined

An [N] suffix marking permanent from movable. The permanent set is positionally determined by the slot name, so a mark would be a third encoding of a bit already carried twice — and a mis-applied mark creates false closure, where a bare [N] promises nothing false.

Both the sweep that found these and the adjudication that settled the ceiling question were run by Fable 5 as an independent adversarial pass. render, verify and the provocation page are byte-identical to v0.1.19.

Known gap: the explainer video still carries the old narration audio. The scripts are fixed; the re-record is deferred.

Install (Cowork)

Download insight-engine-0.1.20.plugin below, then Customize → Plugins → Add → Upload plugin. Uploading over an existing install replaces it in place.

insight-engine v0.1.19 — grade-transport repair

A discipline patch. Seven edits — five in analyse (Steps 4 and 5) and two in verify — repairing grade-lock transport. No new capability, no new files.

What changed

• Step 4's party-held and irreducibly-open marks now travel: any downstream claim whose mechanism depends on one caps at [N], however well attested the general mechanism is.
• Tier definitions are fixed by the specification and never re-based for a case. Where no external source can exist, that is a reason to grade [N], not to redefine [V1]/[V2] locally to mean "stated in the case".
• Step 5 gains a pre-draw presupposition check: an entity supplied by the question rather than established in the case goes through the evidence router before it can be drawn. The premise of a question is not evidence for it.
• Inheritance cap on any link either of whose ends was marked.
• Quote-or-cap: an in-case citation must quote the case text it rests on; an unquotable "in-case" caps at [N].
• Disclosed truncation when the loop cap binds, typed as ungraded self-report.

Testing, stated honestly

A smoke test was pre-registered for this patch and was not run before the release. It was run on 24 August 2026 and passed: 0 of 5 premise-dependent links graded above [N] on the fixture that motivated the edits, against 2 of 5 before them, with 5 of 5 naming the presupposition as unevidenced.

A same-day suspicion that these edits had caused a loop-parity regression rested on one run per arm. It was replicated at n=5 per arm and did not survive: 0 parity errors in 119 retained loops across both specification versions in the shipped Steps 4+5 configuration.

Install (Cowork)

Download insight-engine-0.1.19.plugin below, then Customize → Plugins → Add → Upload plugin. Uploading over an existing install replaces it in place.

v0.1.18 — the multi-provider cross-lab build

The multi-provider cross-lab build. Rung A — the opt-in, off-by-default independent second pass (Step 10) — becomes provider-agnostic. Every part was independently adjudicated by Fable 5 before landing (the same-lineage guard and the adapter loader adversarially). The adjudication layer stays opt-in and off by default, and its decision-flip benefit remains unproven — it is a rigour-and-defensibility check that sharpens a sound analysis, not a safety net, and it never flips the call.

What's new

• Predefined labs for rung A: OpenAI (default gpt-5.6-sol), Google Gemini (gemini-3.5-flash), and xAI Grok (grok-4.5), each via its own adapter, chosen with the crosslab_provider setting.
• "Other" mode: any OpenAI-compatible endpoint you configure (base URL + key + model), or an opt-in, hash-pinned, shape- and lineage-validated operator-written adapter file (default off; it runs your own code, so it is gated with a warning).
• Hard same-lineage guard: any Anthropic-lineage target on rung A is refused with no override — rungs B (Fable) and C (Opus panel) remain the honest same-lineage path.
• Switchable settings v3: prefs schema v2→v3, now 19 keys (adds provider, base-url, key-env-name, lineage, adapter-files, adapter-name); a shared prefs→env resolver with provider auto-inference and a provider/model-mismatch refusal.
• Monitor AMENDMENT-3: a per-provider split of the rung-A yield read-out.

Verification honesty

OpenAI is live-verified (a real smoke returned a clean parse). The Google Gemini and xAI Grok adapters are built to each lab's current published API (2026-07-09) but not live-smoked — they are live-verified only when you run the preflight smoke with that lab's own key. The keyless in-boundary rungs (B Fable / C Opus panel / D self-adversarial) are unchanged.

Install

Download insight-engine-0.1.18.plugin below and, in Cowork, Customize → upload from file.

v0.1.17 — the switchable-settings adjudication build

The switchable-settings adjudication build for the opt-in independent-adjudication layer (Step 10). Every part was independently adjudicated by Fable 5 before landing. The adjudication layer stays opt-in and off by default, and its decision-flip benefit remains unproven — it is a rigour-and-defensibility check that sharpens a sound analysis, not a safety net, and it never flips the call.

What's new

• 13-key switchable settings (schema v2, code-backed in prefs/): every adjudication behaviour is operator-switchable, standing and per-run; nothing is centrally locked. Ask-removing / egress-widening / block-reopen / breadth-raising changes require a deliberate confirmation.
• Privileged cross-lab gate changed from "never waivable" to default-blocked but operator-overridable by a deliberate typed act, logged to the local monitor (never the deliverable).
• Tagged cross-lab errors (CROSSLAB-BLOCKED / CROSSLAB-FAILED [...], HTTP-code classified) and a configurable multi-provider crosslab_model.
• Panel sizing — Opus panel N, cross-lab breadth M, runs-per-model — all as on-divergence offers, never automatic.
• Monitor AMENDMENT-2: a pre-registered per-class retirement rule for deciding, from real use, when adjudication has become redundant for a class of problem.
• The standing crosslab_model preference now retargets a run (CROSSLAB_MODEL remains the per-run override).

Install

• Cowork: download insight-engine-0.1.17.plugin attached below.
• Claude Code marketplace: the insight-engine plugin at v0.1.17.

v0.1.16: consecutive 1-12 step numbering (render/track split)

v0.1.16 — consecutive 1-12 step numbering

• Consecutive 1-12 step numbering. The analyse pipeline now uses a single, consecutive step scheme: triage (1) through decision brief (9), adjudication (10), render (11), track (12).
• Render and track are now separate steps. The former combined "follow-ons" step is split into Step 11 (render) and Step 12 (track).
• Adjudication relabelled Step 10. The old "L4.5" tag is replaced by "Step 10" across the adjudicate skill and its preferences (schema, prefs.py, README).
• Skill fixes. Restored the analyse and adjudicate skill files (recovered truncated tails) and corrected two stale internal cross-references in analyse (resilience check to Step 7; decision-brief items to 9d/9e).

Numbering, labelling, and consistency release — no change to pipeline behaviour.

insight-engine 0.1.15

v0.1.15: code-backed standing opt-out for adjudication

Makes the L4.5 adjudication standing opt-out mechanical instead of
model-remembered, closing the T-L45-001 B4 carry-forward.

New skills/adjudicate/prefs/:
- prefs.py: stdlib CLI — status / opt-out --scope crosslab|all /
  re-enable / should-offer --rung (exit 0 offer, 1 suppressed) /
  selftest. Persists to ~/.insight-engine/preferences.json (env
  override INSIGHT_ENGINE_PREFS), outside the plugin so it survives
  upgrades and is never committed. Fails safe to "offer" on a
  missing/corrupt file; no rung ever auto-runs.
- preferences.schema.json: draft-07 schema; scope enum none/crosslab/all.
- README.md: location, schema, scope semantics, exact commands.

Wiring:
- adjudicate/SKILL.md: gate now consults prefs.py should-offer before
  offering and persists via opt-out / re-enable.
- analyse/SKILL.md: Step 6.5 honours the persisted opt-out by code.

Packaging:
- plugin.json + marketplace.json bumped 0.1.14 -> 0.1.15.
- dist/insight-engine-0.1.15.plugin repackaged (22 files; clean-scanned
  for keys and real-case data; crosslab.py intact).

Verified: prefs selftest passes all transitions incl. corrupt-file
fail-safe; harness offline preflight and mock adjudicator still green.

insight-engine 0.1.14

v0.1.14

insight-engine 0.1.14 - opt-in adjudication layer

Insight Engine v0.1.7

Full Changelog: https://github.com/ComplexAR/Insight-Engine/commits/v0.1.7