Project status: Experimental / pre-1.0. The Canonical Model, REST API surface, Graph Schema,
Adapter SPI, and configuration format are not yet guaranteed stable — expect breaking changes on a
future minor version bump. See
ROADMAP.md.
License: Apache License, Version 2.0.
What v0.3 proves
AIP v0.3.0 proves that the architecture intelligence validated reproducibly in v0.2 survives two
independently authored real systems — an external reference architecture and mature real-world
OSS software — and hardens the Canonical Model only where real evidence justifies it.
v0.2 proved AIP's architecture intelligence behaves correctly against known, hand-authored
ground truth. v0.3 does not add another architecture-intelligence dimension — it tests the same
model against systems AIP's own authors did not build: Quarkus Super Heroes (a controlled,
externally authored microservice reference architecture) and Apache Airflow (a mature real-world
system with API server, scheduler, workers, and asynchronous task execution). The result is
deliberately bounded, not a claim of complete conformance: supported claims are materially
correct, unsupported mechanisms remain explicit, unresolved identity is never guessed, and
non-observation is never treated as absence.
Candidate identity
Candidate SHA: eeff933da3a8f1e5fc6749cb9a77bbf2e5123fd1
Dependency-lock SHA-256: 484361e9e5fc5f498809549cc413e4545832cd91e8720e8bb16406dcdfca0644
Promoted from RC: v0.3.0-rc.2 (v0.3.0-rc.1 preceded it but was superseded by a required
pyproject.toml/uv.lock version-consistency fix before GO)
Quarkus Super Heroes result
Two different counts, per the frozen dossier's own convention — the comparator only scores what
expected.yaml declares, and expected.yaml declares no insufficient_evidence: entries:
Comparator-only Overall dossier
Correct: 38 38
Unsupported: 2 2
Unresolved identity: 0 0
Insufficient evidence: 0 1 (qsh-kafka-operation-type-gap — found by a
separate diagnostic inspection, not the
comparator itself)
Incorrect supported: 0 0
The comparator result reproduced across two independent runs against the qualifying candidate,
with byte-identical captures and comparator reports both times. The separate diagnostic finding
(qsh-kafka-operation-type-gap) was not emitted by either comparator run — it was discovered once,
by a distinct raw-telemetry inspection, and carried forward as part of the accepted overall dossier
disposition.
Apache Airflow result
Correct: 9
Unsupported: 3
Unresolved identity: 2
Insufficient evidence: 1
Incorrect supported: 0
Two independent runs against the qualifying candidate, byte-identical.
Cross-system hardening outcome
Every finding from both dossiers (10 total) was dispositioned NO_CHANGE, DOCUMENT_UNSUPPORTED,
or DEFER — zero required a production fix. The canonical-redesign gate answered NO: no
fundamental Canonical Model redesign is required before v0.4. Full ledger, decision records, and
evidence:
docs/real-world-validation/cross-system/report.md.
Deterministic evaluation result
AIP Evaluation — I4
Scenarios: 10
Passed: 10
Failed: 0
Missing facts: 0
Unexpected facts: 0
Forbidden facts present: 0
Wrong statuses: 0
Evidence errors: 0
RESULT: PASS
Reproduced deterministically across repeated runs, requires no LLM API key.
Quick Start
git clone --branch v0.3.0 --depth 1 \
https://github.com/michaelegner/architecture-intelligence-platform.git
cd architecture-intelligence-platform
cp .env.example .env
docker compose upThen open http://localhost:8000. See the root
README.md
for the full Quick Start, runtime demo, and feature walkthrough.
Known limitations
- gRPC/protobuf calls (Quarkus) — unsupported.
- Kafka topic/subscription semantics (Quarkus) — unsupported.
messaging.operationlegacy-attribute recognition gap (Quarkus) — insufficient evidence,
deferred.- PostgreSQL/database dependencies (Airflow) — unsupported.
- Airflow Execution API caller identity — unresolved by design, not guessed.
- Airflow runtime-role / Celery messaging identity — unresolved, deferred.
- Pre-1.0: Canonical Model, REST API, Graph Schema, Adapter SPI, and configuration format are not
yet guaranteed stable.
None of the above represents an incorrect supported claim — each is explicit and bounded.
What changed since v0.2.0
See
CHANGELOG.md
for the full entry. In summary: no production architecture-intelligence semantics changed. This
release is validation and hardening evidence, not a new capability.
What's next
v0.4 — Architecture Intelligence Tools, goal: Trusted Architecture Context for Agents.
v0.4 will expose snapshot-bound, evidence-qualified, auditable architecture answers through
structured contracts and read-only tools — an agent may consume and reason over AIP evidence, but
it must never become the source of architectural truth. See
ROADMAP.md
for the full v0.4 → v0.5 → v0.9 → v1.0 sequence.
Documentation
README.md— project overview, Quick Start, runtime demodocs/real-world-validation/— the full Quarkus and Airflow dossiers and the cross-system decision traildocs/specifications/0.3.0/— thev0.3.0design/implementation history (I1-I5)ROADMAP.md/CHANGELOG.md— where this is headed, and what's shipped so fardocs/release-validation/v0.3.0-post-release-verification.md— independent verification of this exact published release: GHCR digest match, anonymous pull, non-root execution, health/import smoke, and a fresh tagged-source clone
Security
Please report security vulnerabilities privately — see
SECURITY.md.
Never report a vulnerability as a public issue.