Four surfaces. One path: Nox proposes → Okren decides (with a reason) → North Star records and paper-executes → you measure payback.
What: The operator home — single source of truth for accounts, bots, deals, and the North Star metric (payback per bot).
How / where: Served by the API on this host :4000. Reads Postgres. Does not fire broker orders by itself.
What: The AI proposal desk. Nox never talks to the broker — it only proposes, with a plain-language why.
submitted means it was handed to execution → OkrenHow / where: Nox worker on this staging box writes nox_signals, then POSTs confident ones to execution (source=nox). UI at :4000/nox.
What: Every controlled-path action and Okren’s verdict + reason, stored in North Star’s action ledger.
decision_id + trace_id for auditHow / where: Execution calls Okren, then saves the decision JSON on the actions row. This page reads that ledger at :4000/decisions — not Okren’s internal DB.
What: Okren itself — policy pilot_v1.0, 16 deterministic rules, live evaluation feed.
How / where: Separate Okren process on this box at :3000/tower (Console: :3000/console). Staging runs Okren in observe from North Star’s side. Use Tower for the deep “which rule fired?” story; use the ledger for “what did our platform do?”