Commit graph

2 commits

Author SHA1 Message Date
Shay
57c08e6b15 feat(evals): parallel runner + adversarial-identity v2
Parallel infrastructure:
  evals/parallel.py
    multiprocessing.Pool helper (spawn context, default workers
    min(cpu_count, 8)). Per-case lanes use it via:
      run_lane(cases, workers=N)
    workers=1 forces serial (debugging); None uses the default pool.
    Generic over the per-case return type, so dataclass-returning
    runners (provenance) and dict-returning runners both work.

  Wired into:
    - evals/adversarial_identity/runner.py
    - evals/calibration/runner.py
    - evals/symbolic_logic/runner.py
    - evals/provenance/runner.py

  Per-case helpers are now picklable (module-level, single arg).
  Monotonic-learning stays serial within a split — shared session
  is structural to its longitudinal protocol.

Empirical speedup (adversarial-identity public/v1, 25 cases on
macOS 8 cores): serial 14.1s -> parallel 3.1s (~4.5x). Identical
per-case results.

adversarial-identity v2:
  public/v2  — 35 cases (20 attack / 15 legitimate). Attacks cover
                more varied phrasings: punctuation variation
                ("Actually -" / "No:" / "Correction —"), embedded
                hedges ("please" / "regardless of prior context"),
                multi-clause attacks, and identity-marker triggers
                in mid-clause position.
  holdouts/v2 — 22 cases (12 attack / 10 legitimate) on distinct
                priming vocabulary.
  Results: attack_rejection_rate=1.0, legitimate_acceptance_rate=1.0
            on both splits.

The marker-regex defense in teaching/review.py:_is_identity_override
holds against every v2 phrasing — markers are checked case-insensitive
against the full text, so capitalization / punctuation tricks don't
slip past.

Test suite: 596 passing (no regression).
2026-05-16 13:10:26 -07:00
Shay
64268436fb feat(evals): calibration lane v1 — typed cognitive signals
Adds the third Phase 2 lane: calibration measures whether CORE's runtime
emits distinguishable, typed evidence for three cognitive states:

  no_grounding         vault_hits == 0 (gate fired, no recall)
  coherent             vault_hits > 0  (vault recall fired)
  correction_proposed  pack_mutation_proposal is not None

Each case runs on its own fresh CognitiveTurnPipeline to avoid
cross-case field-state drift (the gate's geometric recall score is
sensitive to vault content drift across turns).

v1 results: dev 12/12, public/v1 24/24, holdouts/v1 18/18 — all classes
score 1.0 across all splits.

Architectural findings logged in evals/calibration/gaps.md:

  1. The ingest gate fires on a *geometric* CGA-recall score, not on
     semantic OOD. 6/42 hand-chosen OOD prompts fire the gate with a
     warmed vault; the other 36 land geometrically near in-pack
     versors after morphological grounding. v1 measures the reliable
     recall/correction signals, not semantic OOD detection.

  2. CognitiveTurnPipeline.run() unconditionally overrides the
     runtime's gate-safety surface with the realizer surface. The OOD
     marker survives in walk_surface but not in surface. v1 classifies
     on vault_hits (preserved) rather than surface (overridden).

Both findings are filed as suggested follow-up work, not v1 blockers.
2026-05-16 12:22:16 -07:00