test-driver/research
tegwick 04e9573b5a T04: deterministic semantic kernel
Alice/Bob/Carol runs end to end, deterministically, replayable from seed.
16 tests pass, no third-party dependencies.

- src/testdriver: intent, provenance, world, actions, drivers, observers,
  oracles, evidence, energy, scenario, runner
- lab/minimal.py: the SUT, exposing the independent observation channel
  required by D-07
- evidence is stratified S1/S2/S3; Runner refuses to attribute S2/S3 to an
  actor; claims are frozen and provenance-checked at construction
- missing evidence yields INCONCLUSIVE, which outranks PASS in the run verdict
- EnergyEvents captured, no scoring (H-005 dormant)

The observation channel records both stored state and an out-of-band
enforcement probe; their disagreement is an invariant and is what detects an
authorization defect that leaves the audit trail intact. A seeded
RevokeIsCosmetic lab fails the run via both the claim and that invariant.

Also closes TD-WP-0001-T02 (stack and commands now exist).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1629012@bnt-lap001
Assistant-Session: 78d4fb13-8a1e-474b-87a3-9b9261c49a39
2026-08-22 23:21:07 +02:00
..
concepts T04: deterministic semantic kernel 2026-08-22 23:21:07 +02:00
decisions T03: research control plane 2026-08-22 23:11:21 +02:00
experiments T03: research control plane 2026-08-22 23:11:21 +02:00
findings T01: establish canonical milestone sequence, record F-0001 2026-08-22 23:07:31 +02:00
hypotheses T03: research control plane 2026-08-22 23:11:21 +02:00
README.md T03: research control plane 2026-08-22 23:11:21 +02:00

Research Control Plane

Deliberately small. This directory exists so that claims about test-driver can be falsified rather than accumulated. It is plain files — no CLI, no schema, no tooling — until there are enough readings to justify tooling.

research/
├── hypotheses/   H-NNN — a claim with a falsification condition
├── experiments/  E-NNN — a planned or executed test of a hypothesis
├── findings/     F-NNNN — findings about test-driver itself
├── concepts/     the Concept ↔ Implementation Fitness Map
└── decisions/    pointers to decisions recorded in State Hub

Identifier convention

Prefix Scope Example
H-NNN Hypothesis H-001
E-NNN Experiment E-001
F-NNNN Framework Finding F-0001
C-<slug> Concept in the fitness map C-actor-isolation
D-NN Decision, scoped to its design note D-07
TD-WP-NNNN-TNN Workplan task (State Hub) TD-WP-0002-T04

Identifiers are stable and never reused. A rejected hypothesis keeps its number.

Hypothesis lifecycle

PROPOSED → EXPERIMENTING → SUPPORTED → PRACTICALLY_VALIDATED → ARCHITECTURAL
                  └──────→ REJECTED

A hypothesis may be reopened if later evidence contradicts it. Reopening is recorded in the file, not by creating a new identifier.

Rules

  1. Every hypothesis states what would falsify it, in terms of an observable outcome, before any experiment runs. A hypothesis with no falsification condition is an opinion.
  2. Concepts with no supporting evidence are marked as such, not quietly retained. The fitness map is expected to contain unsupported entries; hiding them defeats its purpose.
  3. Subtraction counts as progress. A rejected hypothesis or a removed abstraction is a result, not a setback.