Skip to content

v1.7.0 APRA Governance and Source-Native Convenience

Choose a tag to compare

@AnthonyPuggs AnthonyPuggs released this 07 Jun 13:41
· 33 commits to main since this release

v1.7.0 - APRA Governance and Source-Native Convenience

This release strengthens APRA governance validation and improves the provenance exposed by the convenience tools, while keeping the public retrieval interface stable.

Highlights

  • Added maintainer-facing APRA governance validation for catalogue coverage, trusted XLSX seeds and fallbacks, audit metadata, table/variant wiring, and AASB 17 scope warnings.
  • Added scripts/audit_apra_governance.py with --check and --json modes for validating APRA source governance outside ordinary CI.
  • Extended list_release_events provenance:
    • ABS and RBA rows are labelled as official_calendar events from official_page sources.
    • APRA rows are labelled as expected_release events from cadence_estimate sources.
    • APRA release rows now include cadence, seed freshness, audit timestamp, and governance status metadata where relevant.
  • Extended describe_dataset with source-native retrieval guidance:
    • Exact identifier controls.
    • Supported filters and date-bound fields.
    • Explicitly unsupported arguments.
    • Safe example calls for get_latest_observations and get_top_observations.
    • APRA governance context and framework-break warnings.
  • Added latest selection metadata support alongside existing top_n metadata in the response schema.

Compatibility

This is an additive release. Existing MCP tool names and public inputs are unchanged:

  • get_latest_observations
  • get_top_observations
  • describe_dataset
  • list_release_events

The release does not add arbitrary APRA URL inputs, paid/authenticated data access, or weaker source-native identifier controls.

Maintainer Notes

APRA release rows should be interpreted as expected cadence estimates, not official release-calendar dates. ABS and RBA release rows continue to represent official calendar entries.

APRA governance validation remains a maintainer command rather than an ordinary CI gate to avoid upstream APRA landing-page flakiness in routine test runs.

Verification

Validated with targeted APRA governance, release-event, convenience, schema, and repository-hygiene tests; Ruff linting; direct response-schema validation; and a live APRA governance audit using:

UV_CACHE_DIR=.uv-cache PYTHONPATH=src uv run python scripts/audit_apra_governance.py --check