This is a behavioral comparison, not a module-count comparison. It answers three questions:
Naming. The legacy line is Aegis 0.1 (release 0.1.0). There is no separate product called
“Aegis 1.0” in this repository. People sometimes say “1.0” when they mean that pre-2.0 line; this
document and Coverage01VsTwoTest always mean 0.1 → 2.0.
The executable authority is Coverage01VsTwoTest. It reads the frozen 0.1 inventory extracted from the
tracked 0.1 tools.yaml resources and the 2.0 configuration files. A changed count or a 0.1 tool with
no verdict fails the build. This page explains that executable contract. The product-boundary record is
HISTORY.md.
| Area | Aegis 0.1 | Aegis 2.0 |
|---|---|---|
| Backend integrations | One Java mcp-adapter-<engine> module per engine |
Named YAML under adopters/configurations/adapters/<adopter>/, plus shared profiles (Flink, Iceberg, Kafka, Spark) |
| Typed protocols | Mostly adapter-local | Shared modules when a real client protocol requires one: JDBC, ZooKeeper, Kafka Admin, Spark Connect, A2A |
| Governance | In the 0.1 core | One governance engine shared by own-host and optional Knox |
| Planned typed sources | Product-specific clients in the 0.1 line | Arrow, Beam, Hudi, Kudu, and Ozone are later typed sources, not part of this release |
| Kafka and Kafka Connect | Kafka adapter surface | One shared Kafka profile and tutorial covering the broker and Connect (docs/tutorials/kafka.md, docs/TUTORIAL-KAFKA-AND-KAFKA-CONNECT.md) |
| Repository | Separate 0.1 tree / release | 2.0 is the repository root; 0.1 modules are not in this build |
Coverage is not the same as a real-engine Keep. This page accounts for every 0.1 tool and the shipped 2.0 surface. Whether a profile has a kept own-host + Knox run against a live product is tracked in evidence/ADOPTER-REAL-ENGINE-STATUS.md and VALIDATION.md.
| Measure | Aegis 0.1 | Aegis 2.0 | Enforcement |
|---|---|---|---|
| Engine surfaces in the frozen inventory | 33 | 28 in this release, 5 planned later | frozen inventory and verdict test |
| Implemented tools inherited from or replacing a 0.1 capability | 156 | 152 | exact Coverage01VsTwoTest verdict accounting |
| 0.1-successor comparison surface (excludes 2.0-only engines) | not applicable | 155 | EXPECTED_COMPARABLE_TOOLS (152 successors + 2 Kafka Admin reads + 1 Superset chart preview) |
| New 2.0 Kafka Admin tools | 0 | 2 | cluster and topic-configuration reads through the real AdminClient |
| New Burr tools | 0 | 10 | Apache Burr (incubating) is a 2.0 addition, not a 0.1 successor |
| New AsterixDB tools | 0 | 4 | Apache AsterixDB is a 2.0 addition, not a 0.1 successor |
| New SkyWalking tools | 0 | 3 | Apache SkyWalking is a 2.0 addition, not a 0.1 successor |
| Configuration files participating in the comparison | 33 Java adapter modules | 27 deployable adapter configurations plus shared reference configs | parsed from YAML |
| Shipped tools participating in the comparison | 156 | 172 | EXPECTED_SHIPPED_TOOLS (155 0.1-successor + 10 Burr + 4 AsterixDB + 3 SkyWalking) |
| Adapter configurations | n/a | 27 deployable adapter configurations and 123 tools | exact AdapterConfigsTest assertion |
| Implemented tools that became less guarded | n/a | 0 | class-order assertion |
How the 2.0 totals fit together:
152 successors of 0.1 capabilities (kept / renamed / backend-changed)
+ 2 new Kafka Admin read tools
+ 1 Superset chart read (dry-run preview for chart delete)
= 155 0.1-successor comparable tools
+ 10 Burr (2.0-only)
+ 4 AsterixDB (2.0-only)
+ 3 SkyWalking (2.0-only)
= 172 shipped comparison tools
Aegis 2.0 ships 152 successors of the 0.1 tool inventory, plus Kafka Admin reads, a Superset chart preview, Apache Burr (incubating), Apache AsterixDB, and Apache SkyWalking. Arrow, Beam, Hudi, Kudu, and Ozone are planned typed sources and are not part of this release.
The frozen 0.1 inventory is
aegis-0.1-tool-inventory.tsv
(one row per tool, 33 engines, 156 tools). Aegis 2.0 ships 27 deployable adapter configurations
under adopters/configurations/adapters/<engine>/, plus shared reference profiles (Flink, Iceberg, Kafka,
Spark) and typed sources (JDBC, ZooKeeper, Kafka Admin, Spark Connect, A2A, and others). The table below
is a per-engine view of the same contract Coverage01VsTwoTest enforces; regenerate the skeleton with
python tools/coverage-engine-table.py when the inventory or adapter layout changes, then keep the
notes in this file.
| 0.1 engine | 0.1 tools | Aegis 2.0 deployable adapter | Notes |
|---|---|---|---|
activemq |
3 | yes | |
airflow |
5 | yes | |
arrow |
3 | typed source / reference | entire surface deliberately absent (no real HTTP API) |
atlas |
4 | yes | contract config; real-engine Keep still pending (ROADMAP.md) |
beam |
4 | typed source / reference | entire surface deliberately absent (no real HTTP API) |
bookkeeper |
4 | yes | |
calcite |
3 | yes | backend changed to Avatica JDBC (aegis-source-jdbc) |
cassandra |
4 | yes | contract config; real-engine Keep still pending |
couchdb |
4 | yes | |
doris |
3 | yes | |
druid |
4 | yes | |
flink |
19 | shared profile | |
flume |
2 | yes | |
hadoop |
4 | yes | |
hbase |
4 | yes | |
hive |
4 | yes | jdbc_run_query; retained under examples/adopters/hive/ |
hudi |
4 | typed source / reference | entire surface deliberately absent (no real HTTP API) |
iceberg |
12 | shared profile | |
ignite |
4 | yes | |
impala |
3 | yes | contract config; real-engine Keep still pending |
kafka |
8 | shared profile | Kafka broker and Connect; plus 2 new Admin read tools in 2.0 |
kudu |
3 | typed source / reference | entire surface deliberately absent (no real HTTP API) |
nifi |
5 | yes | |
ozone |
4 | typed source / reference | entire surface deliberately absent (no real HTTP API) |
paimon |
4 | yes | contract config; real-engine Keep still pending |
pinot |
4 | yes | |
pulsar |
6 | yes | |
ranger |
4 | yes | examples/adopters/ranger/ |
solr |
4 | yes | |
spark |
5 | shared profile | submission/kill backend changed to Spark standalone REST |
storm |
4 | yes | |
superset |
4 | yes | plus chart-read preview tool in 2.0 |
zookeeper |
4 | yes | data-tree tools use aegis-source-zookeeper, not contrib REST |
burr |
0 | yes | 2.0-only: 10 tools (Apache Burr incubating) |
For every 0.1 tool row, the test assigns exactly one verdict (kept, renamed, backend changed, or
deliberately absent). The narrative tables in the sections below list the non-kept cases only.
| Verdict | Count | Meaning |
|---|---|---|
| kept | 111 | The 2.0 config exposes the same capability, normally with an engine prefix to avoid collisions. |
| renamed | 4 | The capability is present under a more precise 2.0 name. |
| backend changed | 7 | The capability is present but now reaches the real product through a different supported surface. |
| deliberately absent or roadmap | 34 | The tool is not shipped in 2.0; the reason is explicit and tested. |
| total | 156 | Every frozen 0.1 row has exactly one verdict. |
| Aegis 0.1 | Aegis 2.0 | Reason |
|---|---|---|
iceberg/get_table |
iceberg_load_table |
The Iceberg REST Catalog API calls the operation loadTable. |
iceberg/alter_table |
iceberg_set_table_properties |
The implementation changes table properties, so the name says what it changes. |
kafka/query_schema_registry |
schema_list_subjects, schema_latest_version, schema_check_compatibility |
Three endpoint and schema shapes replace one broad tool. |
hive/run_sql_readonly |
jdbc_run_query |
HiveServer2 is reached through its JDBC driver. Both front doors are retained under examples/adopters/hive/. |
| Aegis 0.1 | 0.1 surface | Aegis 2.0 | 2.0 surface |
|---|---|---|---|
spark/submit_batch |
Apache Livy batch API | spark_submit_batch |
Spark standalone Master REST submission API |
spark/kill_application |
Apache Livy or YARN | spark_kill_submission |
Spark standalone Master REST submission API |
calcite/get_status |
an operator-built HTTP root | jdbc_server_info |
Avatica JDBC metadata |
calcite/explain_sql |
Avatica JDBC | jdbc_run_query |
Avatica JDBC, with EXPLAIN accepted by the read-only guard |
calcite/run_sql_readonly |
Avatica JDBC | jdbc_run_query |
Avatica JDBC, with a single read statement and bounded result |
zookeeper/list_children |
zookeeper-contrib-rest |
zookeeper_list_children |
ZooKeeper Java client getChildren |
zookeeper/delete_znode |
zookeeper-contrib-rest |
zookeeper_delete_node |
ZooKeeper Java client delete with an expected version |
The Calcite and ZooKeeper tools use the protocols those products publish. Calcite and Avatica are reached through JDBC. ZooKeeper znodes use the ZooKeeper client. aegis-source-jdbc is exercised against Apache Derby, and aegis-source-zookeeper against an embedded ZooKeeper server. Target-version runs are in VALIDATION.md.
| Capability | Status and reason |
|---|---|
| Flink jar upload | Not exposed. Upload is a release/CI operation; governed execution starts from an approved jar. |
| Flink SQL Gateway reads and writes | Not exposed yet. SQL Gateway needs a session lifecycle, not one declarative request. |
| Iceberg maintenance procedures | Not exposed through the catalog. They execute in Spark or Flink, not in an Iceberg REST catalog. |
| Iceberg unbounded commit transaction | Not exposed. It cannot be bound accurately to one typed resource. |
| Spark SQL read | Present through the real Spark Connect source rather than the classic Spark monitoring source. |
| Kafka DLQ inspection and three Admin writes | Roadmap items for the Kafka Admin source. |
| Livy and YARN | Roadmap sources. They are outside the current Spark standalone source. |
| Arrow Flight (3 tools) | Planned typed Flight client. See the roadmap. |
| Beam JobService (4 tools) | Planned typed JobService client. See the roadmap. |
| Hudi table services (4 tools) | Planned typed source. See the roadmap. |
| Kudu table operations (3 tools) | Planned typed source. See the roadmap. |
| Ozone volume operations (4 tools) | Planned typed source. See the roadmap. |
The detailed source-by-source entry is ROADMAP.md.
It proves 0.1 capability accounting and guard-strength preservation. It does not prove every upstream
endpoint exists in every deployed version. AdapterConfigsTest exercises the 27 deployable adapter
configurations and 123 tools through Aegis governance; many HTTP adapters currently use a contract
route harness. Arrow, Beam, Hudi, Kudu, and Ozone are planned typed sources and are not in this release. The authoritative state,
including real, embedded-real, historical, contract and pending evidence, is
VALIDATION.md and evidence/CLAIMS-MATRIX.md.