Repository navigation
rosetta[java]: cross-language consistency — 1 red / 2 amber metrics, 3 ledgered shapes #2579
Description
Part of #2560 — per-language tracking for the keyword-rosetta control corpus (built for #1096). Planted intent is identical in every language, so every deviation below is measured bias vs. the 46-language median, validated in the corpus's deviation ledger. 🔴 = beyond ±50% of the cross-language median, 🟡 = ±25–50%.
Triage order (per the epic): structure detection first, then signal/keyword rules, then risk-score consequences — §3's numbers are downstream of §1–§2 and re-baseline as those fix. Cross-cutting engine issues (e.g. #2535/#2546) fix many languages at once; this issue tracks this language's residual after each cross-cutting fix lands, and closes when the language sits inside the ±25% band on every comparable metric (or every remaining deviation is ledgered as intended morphology).
1. Structure detection (fix first)
In band — no structure-level deviations.
2. Signal / keyword deviations
- 🔴
doc: 2 vs median 1 (+100%) - 🟡
safety: 3 vs median 2 (+50%)
3. Risk-exposure consequences (downstream)
- 🟡
risk_cognitive_load: 22.4845 vs median 15.1444 (+48%)
Ledgered shapes touching java
| defect | type | issue | evidence | summary |
|---|---|---|---|---|
census-requires-git-tracked |
engine-semantic | — | — | GalaxyScope's census enumerates git-tracked files only; an untracked folder scans as '0 files mapped' with no per-file warning |
state-flux-branch-weighting |
engine-semantic | #2546 | b.java | state_mutation is recorded x3 when branch context exists in the file ('flux' semantics, matching the state_flux column name) |
string-literal-selective-shielding |
upstream-question | #2535 | b.java | Keywords inside one string literal ('if eval fails, try open') count toward branch (+2), safety (+1), io (+1) but eval does NOT count toward high_risk_execution (routes … |
Decoy outcomes (file-level evidence)
- b.java ·
String note = "if eval fails, try open"(string): if + try count branch +2 (java branch includes try), try counts safety +1; volatile+Atomic 2 raw state tripled to 6. Ledger: string-literal-selective-shielding, state-flux-branch-weighting - c.java ·
int hack_level;(code): inert
Reproduce / evidence
- Corpus folder:
data/java/—expected_signals.jsoncarries the shape-by-shape accounting - Gate:
GALAXYSCOPE_BIN=<venv>/bin/galaxyscope python tools/verify_language.py javain the corpus repo - Full context: findings_by_language.md#java · bias_report.md · bias chart
Activity
squid-protocol commentedon Sep 3, 2026
Status: 0🔴 / 1🟡 unexplained, 3 further out-of-band cell(s) accounted for
Generated from
docs/bias_data.json+deviation_ledger.jsonbytools/issue_status.py, using the same verdict machinerybias_report.py --gateruns on (gitgalaxy#2669 E.1), so this comment and the gate cannot disagree about what is left.Still unexplained — the work this issue tracks
risk_tech_debtOut of band, but accounted for
ledgered — a validated ledger entry names this language and this metric
cog_raw— composite-nonlinearity-amplifies-in-band-inputsrisk_cognitive_load— path-and-extension-modifiersrisk_documentation— path-and-extension-modifiersClose criterion (gitgalaxy#2669 Batch E.4)
python tools/language_deviations.py javaexits 1: 1 unexplained cell(s) remain. Each needs a fix, or a validated ledger entry saying why it is correct, before this issue can close.squid-protocol commentedon Sep 6, 2026
Closed 2026-09-06 as superseded by #2812 (
docs/contract_roadmap.md, decision D2). Every out-of-band cell for java is accounted for (the gate reads 0 unexplained) and is now tracked by cause family, not by language: the ledger entry that explains it, its cause category in keyword-rosetta'sdocs/bias_data.json["cell_categories"](echo / inherency / extraction / correlation / scoring), and the family issue #2812 lists for that cause. Live standing at any time:python tools/language_deviations.py javain keyword-rosetta, ordocs/findings_by_language.md#java.This is a change of axis, not a claim that java is green. The §10 capstone in
docs/language_status/java.mdis written when the language reads clean bylanguage_deviations.py, by whichever family PR gets it there — no longer tied to this issue.