Captures the end-to-end behavior of the gloss-feature landing as a
durable, replayable artifact. Two files:
notes/live_probe_2026-05-19.py
Probe script — walks 51 prompts across 13 categories through
fresh ChatRuntime() instances (cold-start invariant; no vault
contamination across prompts). Runs offline / locally:
uv run python notes/live_probe_2026-05-19.py
notes/live_probe_2026-05-19.txt
Captured output of the script on commit a8b611a. Acts as a
golden-master record: anyone can rerun the script and diff the
output to detect surface drift.
Categories covered:
- Cognition (5 prompts) — truth, knowledge, memory, ...
- Speech-act / discourse (5) — fact, idea, statement, ...
- Mental-state (5) — doubt, believe, self, mind, view
- Adjectives / attitude (5) — true, important, evident, ...
- Temporal (5) — now, moment, future, before, time
- Spatial (4) — here, place, above, between
- Action verbs (4) — incl. infinitive-stripped form
- Quantitative (4) — all, some, more, enough
- Causation (4) — effect, outcome, consequence, trigger
- Polarity / frequency (4) — yes, always, never, maybe
- Teaching-chain multi-clause (1) — Why is truth important?
- Genuinely OOV (3) — hypothesis, javascript, quasar
- Cause without teaching chain (2) — How does memory work?
What causes doubt?
Grounding distribution observed:
pack 45 (88.2%) fluent gloss-backed surfaces
oov 3 ( 5.9%) honest OOV invitations
none 2 ( 3.9%) honest "I don't know" (CAUSE w/o chain —
deferred SurfaceSelector target)
teaching 1 ( 2.0%) multi-clause teaching-chain composition
Sample surfaces:
[PACK] What is truth?
Truth is a claim or state grounded by evidence and coherent
judgment. pack-grounded (en_core_cognition_v1).
[PACK] To use means to put something into service for a purpose.
pack-grounded (en_core_action_v1).
[PACK] Something is important when it carries weight or priority in
some judgment context. pack-grounded (en_core_attitude_v1).
[PACK] Always indicates the frequency of occurring without exception
across all instances. pack-grounded (en_core_polarity_v1).
[TEACH] truth — teaching-grounded (cognition_chains_v1):
cognition.truth; logos.core. truth grounds knowledge
(cognition.knowledge). No session evidence yet.
[OOV] I haven't learned 'hypothesis' yet (intent: definition).
Mounted lexicon packs: ...
Teach me via a reviewed PackMutationProposal.
[NONE] I don't know — insufficient grounding for that yet.
(CAUSE on memory — no teaching chain rooted here; the
deliberate non-fallback the teaching pipeline uses as a
discovery-gap signal)
No code change in this commit. Pure documentation artifact for the
fluency-push baseline.
Three companion docs to the 2026-05-19 fluency push. Captures the
deferred architectural work and the measured lift so the next
engineering pass has fixed substrate to build on.
notes/surface_selector_design_2026-05-19.md
Deferred RFC for the typed-candidate-lattice + single-selector
refactor the 2026-05-19 design review prescribed. Names the
remaining symptom this fixes (warm_grounding_stability=0 on the
warmed lane) and the migration shape: PackSurfaceCandidate
already shipped in commit 46ac737 is a structural subset of the
proposed SurfaceCandidate type. Six-step landing plan; each
step ends green and is independently revertable.
notes/spine_unification_design_2026-05-19.md
Companion RFC for the cognitive-spine unification. Enumerates
the three spines today (ChatRuntime.chat, CognitiveTurnPipeline,
scripts/run_pulse) + 5 eval-lane runners that split between
them. Proposes one canonical entrypoint with opt-in mode
parameter. Depends on the SurfaceSelector landing first.
notes/fluency_lift_baseline_2026-05-19.md
Numbers-only baseline. Per-lane before/after metrics across
cold_start_grounding, warmed_session_consistency,
deterministic_fluency, and cognition (public + holdout).
Sample probe showing fluent vs. structured-disclosure output
for 6 prompts. Lexicon + gloss coverage by pack (323/331 =
97.6% English-pack coverage). Reproducer command at the bottom
so anyone can re-measure in one paste.
Both RFCs explicitly document what's IN scope (so the next pass
isn't ambiguous) and what's OUT of scope (so it isn't accidentally
absorbed). Both flag the appropriate landing surface (reviewer's
track, not solo) and the dependency order.
No code change in this commit. Pure documentation.
Shay