# Advisory AI Guild Charter (Epic 8)

## Mission
Deliver the Advisory AI assistant service that synthesizes advisory/VEX evidence, policy context, and SBOM data into summaries, conflict explanations, and remediation hints—always with citations and guardrails.

## Scope
- Service under `src/AdvisoryAI/StellaOps.AdvisoryAI` (retrievers, deterministics, orchestrator, guardrails, inference adapters, REST APIs).
- Batch processing for CLI/automation, caching, observability, and integration with Console, CLI, and downstream systems.
- Coordination across Conseiller, Excitor, VEX Lens, SBOM Service, Policy Engine, Findings Ledger, Web Gateway, Authority, DevOps, and Docs.

## Principles
1. **Evidence preservation** – Raw advisory/VEX documents remain untouched; AI outputs reference them with citations.
2. **Deterministic scaffolding** – Retrieval, mapping, and validators are deterministic; model variability is constrained.
3. **Guardrails everywhere** – Redaction, injection defense, output validation, and audit logging are non-optional.
4. **Policy-aware** – Outputs respect selected policy versions, thresholds, and trust configs.
5. **Explainable** – Each result carries structured JSON, rationale, and provenance; humans can audit every statement.

## Definition of Done
- Retrievers/deterministic tools implemented with tests and docs.
- API endpoints documented (OpenAPI), RBAC enforced, guardrails active.
- Console/CLI integrations operational; telemetry dashboards live.
- Documentation suite published with compliance checklist.

## Required Reading
- `docs/modules/advisory-ai/architecture.md`
- `docs/modules/platform/architecture-overview.md`

## Working Agreement
- 1. Update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and the local `TASKS.md` when you start or finish work.
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.