# Reckon Graph 0.3 evidence ledger

This ledger freezes the field and competitor evidence used to define the 0.3
release. Historical observations are not rewritten as current measurements.

## Minions field observation

The prior 0.1.22 field run recorded:

- 3,006 source files;
- 2,949 indexed files and 157 health findings before repair;
- 3,006 indexed files after repair;
- current HEAD `cbf058aa...`;
- recorded indexed HEAD `4d45fe02...`;
- a 16-commit distance while 0.2.0 status incorrectly reported healthy;
- 195 repair operations, including reconciliation of stale/orphaned state and
  regeneration of 1,874 symbol embeddings.

The workload fast-forwarded main across 15 merged commits and removed 16 linked
worktrees. The checked-in lifecycle regression recreates those lifecycle
shapes, including additions, edits, renames, deletions, policy transitions,
overlapping hook workers, immediate queries, and cleanup.

The Minions checkout is a read-only field fixture for this release. Its current
HEAD on 2026-07-30 was `44c91f6d013fd8d6f4e106d063a87eab94b19866`;
the historical SHAs above belong to the original observation, not that later
checkout state. Existing modified and untracked Minions files were left intact.

## Token Optimizer observation

The complete 102.8-second demo artifact has SHA-256
`a8085ec26d56ab220f3b31578f818a911caf277e604ed9f8d46c0d9f31fbb60d`.
It demonstrates seven named surfaces: file outline, symbol extraction, symbol
find, batch outline, project overview, output compression, and command running.
It describes Python AST parsing and heuristic/regular-expression coverage for
other languages.

At release time, no authorized immutable source commit, packaged executable,
README, version, or raw measurement data was available, so the original
observation was `demo-only`. A post-release source audit now pins the authorized
GHES implementation at
`a2b9cef5efdfcf0393e9e7a5ded229ffd9f613d7`. It verifies the source inventory
and selected implementation observations, including a behavioral compression
budget probe. Equivalent end-to-end measurements remain incomplete, and the
displayed savings remain hypotheses: the demo showed two calls, used a bytes/4
token estimate, and showed inconsistent 83% and 93% targeted-lookup figures.

The reproducible comparison contract is
[`../benchmarks/evaluations/token-optimizer-20260730/comparison-manifest.json`](../benchmarks/evaluations/token-optimizer-20260730/comparison-manifest.json).
The immutable source result is
[`../benchmarks/evaluations/token-optimizer-20260730/raw-source-audit-20260730.json`](../benchmarks/evaluations/token-optimizer-20260730/raw-source-audit-20260730.json).
Missing behavioral measurements are `null`, never zero.

The later C56 replay now executes all seven pinned workflows with shared
fixtures, real-token counts, 20 warm samples, five cold-process samples, and
explicit correctness oracles. Both products pass the five structural oracles.
The result is intentionally `complete-with-gaps`: Token Optimizer is smaller
and faster on all five small-fixture structural calls, Reckon has no output
compressor yet, and command execution remains containment-gated. See
[`../benchmarks/evaluations/token-optimizer-20260730/summary.md`](../benchmarks/evaluations/token-optimizer-20260730/summary.md).

## Implemented and deferred

Reckon now provides parser-grounded bounded file and batch outlines, compact
source-only extraction, deterministic project overview, natural-prompt routing,
real-token local telemetry, and a static local report through the existing
single `reckon` gateway.

`reckon run` is not shipped. A no-shell launcher alone could not prove portable
hard memory limits and process-tree termination across POSIX and Windows. The
full gate and adversarial fixtures remain documented in
[`COMMAND-OUTPUT-COMPRESSION.md`](COMMAND-OUTPUT-COMPRESSION.md). This is a
security decision, not a claim that the competitor implementation is unsafe.