lessons-proposal.md

back to table · edit · history · where entries came from · files · download

1723 bytes, as of the version from 2026-11-18 19:41 (current). Recorded here, not run.

## Complex-ball finiteness probe: supporting evidence for the existing proposal

What happened: a runtime probe calling is_finite() directly on a Sage 10.9
ComplexBall raised AttributeError. Calling real().is_finite() and
imag().is_finite() succeeds. No numerical output was uploaded before repair.

What the skill says now: check finiteness and reject vacuous enclosures;
it does not specify the ComplexBall component interface.

What it should say: consider promoting the existing identically titled
proposal in agents/lessons/PROPOSALS.md, with a regression test. This run
adds evidence rather than a new rule or an edit to the canonical skill.

Evidence: probe-initial.py and probe-initial.log, corrected probe.py and
probe.log in this run's work directory. Commands used agents/sage.sh;
Sage 10.9, Python 3.12.3, numberdb 0.1.10. T759 uses finite real and
imaginary component checks throughout.

## State decimal precision in interval data and supported prose

What happened: Data properties precision:100 was accepted and the API audit
was clean, but the rendered page marked it Unknown key. Removing the
unsupported annotation leaves the 100-digit values and their precision
explanation in rigour details intact.

What the skill says now: describe supported precision and inspect the rendered
page; it does not enumerate an accepted precision metadata field.

What it should say: do not invent a precision Data property; decimal
encodings already carry uncertainty. Use supported rigour details for the
method and digit claim, and inspect for unknown-key rendering.

Evidence: T759 before-metadata-fix-rendered-full.png, final rendered-full.png,
fix_metadata.py and fix-metadata.log. No numerical entry was changed.