Reference

Contracts shared by both method families

• Input panel: Required columns, validation and source naming.
• Notation: Symbols used in equations.
• API reference: Generated parameter and return documentation.

Each family keeps its own contracts, settings and parameters beside its method page:

• Anchored family: the anchored estimate, parameters and eligibility.
• Bayesian family: the posterior contract, settings, presets, eligibility and the panel workflow.

Integration boundaries

• Acquisition: Model IDs, vendor access and file loading belong to the caller.
• Units: Match units across forecast, consensus and actual; conversion stays upstream.
• Calendars: Supply fiscal period ends and availability timestamps explicitly.
• Evaluation: Retain source vintages and replay each historical reading cutoff. Neither a period label nor an old timestamp proves historical model availability.
• Freshness: Anchored publication enforces parameter age limits; BayesianPosterior leaves freshness policy to the caller.
• Audit: Retain complete settings and reproducible input snapshots; see the audit recipe.