Back to the journal

APGR 0.9.0: evidence an integration can actually consume

A strict CI summary contract and caller-owned adapters support composition with JACA XO.

The qualification interface gains a machine-readable summary containing version, subproject, suite, test status, gate status and source commit. A caller can bind a result to a source identity instead of scraping a human log and guessing what passed.

The release distinguishes policy, unit, integration and combined qualification roles. It also demonstrates Go-library consumption through a caller-owned XO adapter fixture: APGR supplies its domain primitives, while the consuming project owns its own data types and orchestration decisions.

This fixture is not JACA’s production adapter, and JACA-side CI registration was still pending at this release. That separation is the important integration story. A toolkit can make evidence portable without becoming the authority that decides whether a larger system is ready to ship.

Sources and release records