Platform

The Platform context owns the decision host side of Spectral: the customer-facing surfaces that receive /decide invocations, route them to deployed action modules, execute the modules, write the audit chain, and surface inspection back to the customer.

Pages in this subtree:

• Customer Dashboard — the read-only inspection surface: an all-domains Portfolio landing, then per-domain Overview, Decisions, The rules, and Trust tabs, with the version-scoped Ruleset Card reached from Trust, plus minimal customer-to-operator interaction primitives. The customer-facing control plane.
• Explainability — how every decision carries decision-trace, work-frame, and per-rule match evidence, and where customers and operators consume it.
• Notifications — customer-facing notifications for decisions, override-pattern signal acknowledgements, and version-publication events.

The platform pillar’s role is settled by ADR-076: host and route decision-module execution, handle auth and identity resolution, write the audit chain, expose observability and billing, and manage the deployment lifecycle of decision modules. The platform never produces decision-module content — that is the world-model system’s authority, surfaced through the Operations app.

The customer-facing control plane is the Customer Dashboard. The operator-facing control plane is the Operations app, which is a separate top-level subtree under System Design.