Oracle - v1.0.9
Release Type: Semantic Stabilization & Contract Formalization Status: Public Stable
Overview
Oracle v1.0.9 formalizes the analytical contracts that govern verdict generation, availability handling, and narrative integrity across all evaluation axes.
This release eliminates false-negative verdicts caused by incomplete data and introduces a deterministic, contract-driven evaluation layer that prevents semantic regressions going forward.
No gameplay formulas were changed. This is a correctness and reliability release.
Key Changes
1. Formal Contract Layer (@oracle/contracts)
A new standalone package defines the canonical contracts for:
Axis availability (
FULL | PARTIAL | NONE)Verdict eligibility and confidence gating
Narrative tone enforcement under limited data
Identity and sustain classification invariants
These contracts are consumed by the engine but can be validated independently via contract tests.
2. Availability-Driven Verdict Semantics (Breaking)
Previous behavior
Axes with missing data could escalate to
RISKYSafety locks could act as primary decision drivers
Negative narratives were emitted under uncertainty
v1.0.9 behavior
Any axis with
availability !== FULLis non-decisiveVerdicts degrade to
UNKNOWNunder incomplete dataConfidence is explicitly reset to
UNKNOWNSafety locks no longer act as primary drivers when availability is
NONE
This is a semantic breaking change by design.
3. Survivability Axis Corrections
Sustain absence is no longer interpreted as structural failure
EHP remains informative but cannot independently escalate verdicts
sustainStatus now resolves to Unknown when sustain data is unavailable
False RISKY migrations caused by missing regen/leech data are eliminated
4. Damage Axis Hard Gating
Builds with
Total DPS = 0are now classified as insufficient dataNo negative verdicts or narratives are emitted in this state
Damage comparisons require
availability = FULLto influence outcomes
5. Speed Axis (Gate-Only Enforcement)
Speed analysis no longer penalizes or rewards under limited data
Axis acts strictly as a qualitative modifier when availability is FULL
Prevents false “slow build” classifications from partial movement data
6. Narrative Integrity Improvements
All narratives now explicitly reflect data certainty
Negative or alarming language is forbidden under
availability !== FULLIntroduced standardized summaries for insufficient or partial data cases
7. Contract Test Pack (Jest/Bun)
Introduced a standalone Contract Test Pack
Tests invariants without importing the engine
Prevents regression via snapshot drift or heuristic reintroduction
Acts as the authoritative safety net for future tuning
Known Limitations
PoB / PoE2 data extraction limitations may still result in PARTIAL or NONE availability This is now treated as a first-class analytical state, not an error.
Some historical snapshots may show changed verdict labels due to corrected semantics.
Migration Notes
No action required for end users.
Developers should:
Consume verdicts defensively (UNKNOWN is now a valid, stable state)
Avoid assuming verdict escalation without FULL availability
Reference @oracle/contracts for all future axis logic
Versioning Rationale
Although the internal work began under a v0.9 milestone, the introduction of:
formal contracts,
deterministic availability semantics, and
a public stability guarantee
justifies the institutionalization as v1.0.9.
This version marks the point where Oracle’s analytical output becomes contractually stable.
Summary
Oracle v1.0.9 is a trust release.
It prioritizes correctness over aggressiveness, clarity over speculation, and guarantees that Oracle will never penalize a build for data it does not actually possess.