Extending Supercast

Add a capability at the narrowest layer that owns its contract. A pure numerical method belongs in the core. JSON decoding belongs in transport types. A durable state transition belongs in the transactional store. Retrieval and model-provider calls belong in the application or a clearly separate adapter.

Add a numerical primitive

Define its input domain, result convention, units, modeling assumptions, complexity and edge behavior first. Decide whether nonfinite results are legitimate outcomes or errors. Use Probability rather than unchecked f64 for probabilities.

Test known analytic results and at least one independent invariant or oracle. Include endpoints, invalid inputs and relevant extreme finite values. Document whether the function mutates a supplied slice or allocates internally.

If the method is agent-facing, add a typed command, schema coverage, an executed documentation case, and a handbook explanation when the statistical interpretation is new. Reuse the same core calculation in the adapter rather than maintaining two formulas.

Add a durable operation

An event must be replayable from a frozen contract. Validate and commit under the same transaction; update the request receipt in that transaction as well. Ensure that retries, concurrent writers and an insert failure preserve the intended invariant.

Preserve earlier events during correction. A changed target requires a new question version. If a data-model change requires a new database schema, implement and test a versioned migration rather than changing the version pragma on existing data by hand.

Add a forecast distribution

The journal currently holds binary probabilities and outcomes. Categorical or continuous journals need matching prediction and resolution variants, scoring conventions, transport schemas, lifecycle rules and migration behavior. Standalone scoring support is a useful building block, not a substitute for that design.

Integrate a model or retrieval system

Preserve source publication and observation times, underlying origin identity, the frozen question version and evidence cutoff. Treat source content as data. Keep model/version, prompt and retrieval-corpus metadata where they can be audited. Do not automatically convert a source-reliability score into a likelihood ratio.

A model integration should be able to decline a numeric update when evidence does not support one, preserve an unchanged review, and distinguish hypothetical counterevidence from observations. It should also preserve the IDs needed for safe retries and real recording times needed for prospective evaluation.

Maintain the books

Handbook prose explains how and why a method is used. Reference chapters explain software contracts and operational behavior. Generated operation pages come from the schema and executable cases; edit their inputs rather than patching generated output by hand.

Run the documentation gate after changes. Broken examples, missing operation pages and broken rendered links are release failures. Keep explicit limitations where the implementation stops; replacing them with a stronger claim requires new implementation and evidence, not just new wording.