Skip to content

v0.3.0-rc.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@michaelegner michaelegner released this 02 Sep 09:25
· 27 commits to main since this release
v0.3.0-rc.1
9f95d48
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.3.0-rc.1 release notes

Project status: Real-World Validation and Cross-System Hardening (I1-I4) complete; I5 (release
qualification) pending before v0.3.0 ships.

This is the release candidate for v0.3.0 — the release that proves the architecture intelligence
validated reproducibly in v0.2.0 survives real, independently authored systems, and hardens the
Canonical Model only where real evidence justifies it.

Highlights

  • I1 — real-world validation contract frozen: finding vocabulary, ground-truth independence
    rules, supported-scope rules, comparator semantics, dossier structure, runbook contract.
  • I2 — Quarkus Super Heroes (external reference architecture): 38 correct, 2 unsupported, 1
    insufficient evidence overall (0 in the comparator-only score), 0 incorrect/missing supported.
    Two independent runs, byte-identical.
  • I3 — Apache Airflow (real-world OSS software): 9 correct, 3 unsupported, 2 unresolved
    identity, 1 insufficient evidence, 0 incorrect/missing supported. Two independent runs,
    byte-identical.
  • I4 — Cross-System Model Hardening: all 10 findings from both dossiers dispositioned — zero
    required a production fix (NO_CHANGE/DOCUMENT_UNSUPPORTED/DEFER only). The
    canonical-redesign gate answered NO: no fundamental Canonical Model redesign is required
    before v0.4. Both systems revalidated twice each against this exact candidate, byte-identical
    captures and comparator output both times.

Full deterministic cross-system report:
docs/real-world-validation/cross-system/report.md.

No production changes

Every real-system finding from either dossier was NO_CHANGE, DOCUMENT_UNSUPPORTED, or DEFER —
AIP's supported-scope semantics are unchanged from v0.2.0.

Known limitations

  • gRPC/protobuf calls (Quarkus) — unsupported
  • Kafka topic/subscription semantics (Quarkus) — unsupported
  • messaging.operation legacy-attribute gap (Quarkus) — insufficient evidence, deferred
  • PostgreSQL/database dependencies (Airflow) — unsupported
  • Airflow Execution API caller identity — unresolved
  • Airflow runtime-role / Celery messaging identity — unresolved, deferred

None of these represents an incorrect supported claim — each is explicit and bounded.

What's next

I5 will qualify this exact candidate and publish v0.3.0. See
ROADMAP.md
for the full v0.3 track and the v0.4 (tools) → v0.5 (discovery) → v0.9 (freeze) → v1.0 (stable)
sequence.

Documentation

docs/real-world-validation/ — full Quarkus and Airflow dossiers, the cross-system decision trail,
and the report above.

Assets 2
Loading