# reference topology assumptions
Iridium Sprint 6 treats the product as the execution anchor for the integrated reference topology, not as the owner of every topology concern.
This document states what the current product-owned integrated harness does verify, and what remains an external dependency.
## product-owned integrated harness scope
The current integrated harness verifies:
- service-backed retrieval compatibility
- ingest, query, restart, and recovery durability
- recovery latency and recovered-query gate behavior when the optional native Python module is available
- one integrated mixed ingest/query/recovery execution test path
- one Rhodium-backed compiled-plan cache path for Plexus serialized-plan execution when the `rhodium-backend` feature is enabled
Generate the harness artifacts with:
```sh
python3 scripts/integrated_harness_report.py --report-dir artifacts
```
This writes:
- `artifacts/integrated_harness_report.json`
- `artifacts/integrated_harness_report.md`
Rhodium-backed compiled-plan cache evidence currently runs from:
```sh
cargo test --test rhodium_compiled_plan_reference --features rhodium-backend -- --nocapture
```
This writes:
- `artifacts/rhodium_compiled_plan_cache_report.json`
- `artifacts/rhodium_compiled_plan_cache_report.md`
Legacy aliases remain available during the Sprint 7 transition:
- `artifacts/rhodium_compiled_plan_reference_report.json`
- `artifacts/rhodium_compiled_plan_reference_report.md`
## current topology boundary
- execution anchor: Iridium single-node product path
- runtime contract: integrated ingest/query/restart/recovery
- service shape: the Sprint 5 single-node service candidate path
## external dependencies
These topology concerns are intentionally not reimplemented in Iridium-local code:
- Plexus
- flagship query/profile assumptions
- compiled-plan cache contract
- Rhodium
- compiled-plan cache storage
- retrieval artifact cache path
- tiered hydration behavior for flagship compiled-plan artifacts
- Strontium
- full-stack replay and fault attachment
- Palladium
- bounded-cluster control-plane integration boundary
## interpretation
The current integrated harness is a controlled assembly seam:
- it proves Iridium’s product-owned execution contract is ready to participate in the reference topology
- it does not claim that the full multi-repo topology is complete inside the Iridium repo alone
## neighboring docs
- service API and artifact surface: `docs/api/service.md`
- single-node operator runbook: `docs/service_single_node.md`
- install/package guide: `docs/service_install.md`