Skip to content

docs: sync ARCHITECTURE.md and benchmark pricing to match code#1720

Merged
esengine merged 1 commit into
esengine:mainfrom
FriendsHL:docs/sync-arch-benchmark-pricing
May 25, 2026
Merged

docs: sync ARCHITECTURE.md and benchmark pricing to match code#1720
esengine merged 1 commit into
esengine:mainfrom
FriendsHL:docs/sync-arch-benchmark-pricing

Conversation

@FriendsHL

Copy link
Copy Markdown

Three stale-doc fixes where documentation no longer matches the actual codebase:

1. ARCHITECTURE.md §4.3 — /pro single-turn arming (removed in 0.50.0)

Rewrote to describe the current /model flash|pro command and config-based model selection. Added a history note referencing #1657, #1630.

2. ARCHITECTURE.md §4.4 — FAILURE_ESCALATION_THRESHOLD=3 auto-escalation (never existed in code)

Replaced with the actual <<<NEEDS_PRO>>> model self-report mechanism. No failure-counter, no scavenge/storm counting — purely LLM-initiated. The "failure-threshold" variant in EscalatedEvent.reason is also dead code; kept the type union for now.

3. benchmarks/real-world-cache/README.md — pricing numbers out of sync with src/telemetry/stats.ts

The displayed pricing for v4-flash cache-hit was 10x the code value (0.028 → 0.0028). v4-pro pricing was entirely wrong (0.139/1.667/3.333 → 0.003625/0.435/0.87). Recalculated both cost tables and savings percentages. The headline cache-hit ratio (99.82%) is unchanged.

Verification

Three stale-doc fixes:

1. ARCHITECTURE.md §4.3 — Replace deleted /pro single-turn arming
   with current /model + config model selection. Add history note
   referencing v0.50.0 removal (esengine#1657, esengine#1630).

2. ARCHITECTURE.md §4.4 — Replace non-existent FAILURE_ESCALATION_
   THRESHOLD=3 auto-escalation with the <<<NEEDS_PRO>>> model self-
   report mechanism. Clarify no failure-counter or scavenge/storm
   counting exists.

3. benchmarks/real-world-cache/README.md — Fix pricing numbers to
   match src/telemetry/stats.ts (flash cache-hit was 10x too high,
   pro numbers were all off). Recalculate both cost tables and
   savings percentages accordingly.
@esengine esengine merged commit 7d49171 into esengine:main May 25, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants