Rewards Assistant Platform Documentation

Rewards Assistant Platform Documentation

The platform-wide table of contents for the Rewards Assistant. It spans six repos — consumer-agent, consumer-context-service, consumer-graph-worker, rover-agent, rover-mcp, consumer-graph-mcp — and links every platform spec to its hosted home on tech-docs.

Cross-repo links use absolute tech-docs.fetchrewards.com URLs by convention (PF-7 §4.6) — the docusaurus per-repo build does not resolve relative cross-repo paths. The six repos publish under a shared rewards-assistant/ folder inside the existing backend section (see the implementation note in PF-7). Some targets below 404 until their owning repo completes its PF-7 wiring (consumer-agent is Phase 2; CGW Phase 1; CCS Phase 3; the MCP repos Phase 4).

Platform Specs

Chat Stack

• PC-1 — Agent Composition (Skills + Connectors + Models)
• PC-2 — Runtime Discovery & Sub-Agent Execution
• PC-3 — Execution Modes & Event Streaming
• PC-5 — Agent CI/CD Pipeline
• PC-6 — Agent Variant CI/CD + Experiment-Gated Rollout

DM Stack

• PD-1 — Scheduled DM Execution
• PD-2 — DM Delivery & notification-service Contract
• PD-3 — DM Type Registry & Rollout

Services

• PS-2 — Connector Framework
• PS-3 — Config & Secrets
• PS-5 — Trace & Event Store

Foundation

• PF-1 — Sub-Agent Lifecycle (dev → test → promote → rollback)
• PF-7 — Documentation Site
• PF-9 — Eval Foundation

Per-Repo Documentation

• consumer-agent — Orchestrator, sub-agent host, mobile streaming, Chat + Foundation specs
• consumer-context-service — Domain enrichment, BFF assembly, Services specs
• consumer-graph-worker — DM Stack execution, knowledge graph, DM specs
• rover-agent — Agent runtime
• rover-mcp — MCP server (tools, widgets)
• consumer-graph-mcp — Knowledge-graph MCP server

Authoritative Roster

See the Platform Spec Lab on Confluence for the complete spec roster, dependency graph, status, and decisions. This site is the hosted home for the markdown body of each spec.

Maintenance (PF-7 §4.5). This index is hand-maintained. When a new spec lands in any of the six repos, the spec author opens a one-line follow-up PR adding the entry here. The platform-index drift lint (§7.6) enforces that every docs/specs/*.md has a matching entry.