# flagship reference stack
Iridium Sprint 7 packages the product-owned execution evidence needed for the flagship GraphRAG reference stack release.
This is not a second runtime path. It is a release-facing packaging layer built on top of the Sprint 6 integrated harness and the existing service/package baselines.
## Iridium-owned release inputs
Generate the release-facing artifacts with:
```sh
python3 scripts/flagship_release_report.py --report-dir artifacts
```
This writes:
- `artifacts/flagship_release_report.json`
- `artifacts/flagship_release_report.md`
- `artifacts/flagship_release_handoff.json`
- `artifacts/flagship_release_handoff.md`
## What the flagship release report includes
- integrated execution evidence from the reference-topology harness
- recovery baseline from the core recovery gate
- service compatibility and install/package baselines
- Rhodium-backed compiled-plan cache reference evidence
- dependency boundary notes for cross-repo packaging
## Product-owned role in the flagship stack
Iridium owns:
- the execution anchor for ingest, query, restart, and recovery verification
- the single-node service/package baseline consumed by the flagship package
- the product-facing release evidence and handoff manifest for `alloy`
Iridium does not locally absorb ownership of:
- Plexus query/profile contracts or compiled-plan cache contract definition
- Rhodium cache storage and retrieval-artifact hydration behavior
- Strontium replay and fault publication packaging
- Palladium bounded-cluster control-plane integration
## Neighboring artifacts
- integrated harness: `artifacts/integrated_harness_report.json`
- service compatibility: `artifacts/service_compatibility_report.json`
- service install baseline: `artifacts/service_install_report.json`
- recovery baseline: `artifacts/core_recovery_gate_report.json`
- Rhodium compiled-plan cache reference: `artifacts/rhodium_compiled_plan_reference_report.json`
## Neighboring docs
- reference topology assumptions: `docs/reference_topology.md`
- service API and operator path: `docs/api/service.md`
- single-node runbook: `docs/service_single_node.md`
- install/package guide: `docs/service_install.md`