Used only when a request is marked to save. If left blank, the server will fall
back to its `DATABASE_URL` environment variable.
Tip: place-name resolution needs network access. If the timezone field is wrong, the
resolver will now ignore it and try to derive the timezone from coordinates.
No request yet
Run a request to inspect the service output.
No context loaded
Load a saved context bundle to inspect what the Oracle layer would receive.
Chat Loop
Chat flow inspector
This uses the backend `chat-turn` endpoint, which logs the user turn, builds Oracle
context, runs the Oracle path, and logs the assistant reply.
System
Run a chat turn to test the local Oracle loop.
Transit Lab
Today transit JSON + Oracle read + follow-up chat
This panel resolves the subject, fetches today's transit via `/transits`, saves it,
then runs a transit-mode Oracle read against the saved context.
You can enter either a backend subject id or a display name. If only display name is
provided, the panel will search for the subject first.
Transit Lab ready
Run the transit stack to inspect today's transit JSON.
Transit Oracle Reading
Run a transit reading to inspect the AI description of today's transit.
System
Run the transit stack, then ask follow-up questions here.
Subject Inspector
Use this to inspect one subject's current backend state: chart counts, sessions,
recent turns, saved context, memory artifacts, and stored thread continuity.
`Subject ID` here means the saved backend user/profile key (`subject_external_key`).
If you do not remember it, use the User Search panel to find it by subject id or display name.
Run a subject inspection to see how this person is represented in the backend.
People
Build a subject’s people list here first. If this person already exists as a saved subject,
include their subject id so their chart can be pulled into relationship views later.
No people loaded
Run a subject inspection to load this subject’s people list.
Transit Readings
These are saved AI transit readings for this subject, including model, token usage, and estimated cost.
No transit readings loaded
Run a subject inspection to load saved transit readings.
Prompt Lab
This panel helps you see exactly what the backend is sending into the Oracle layer,
including the built prompt package, the final API request payload, and the live or
stubbed response.
Tone guidance: `0-20` Homeric, `40-60` Balanced, `80-100` Aristotelian. This changes
the Oracle's register, not the chart data.
`Subject ID` here means the saved backend user/profile key (`subject_external_key`).
Use User Search if you want to find someone by subject id or display name first.
Build a prompt package or Oracle request to inspect the reading pipeline.
DB Overview
Use the quick templates to learn the schema and inspect live records. Custom SQL is
limited to read-only statements.
Run a template query or custom SELECT to inspect database contents.
API Debug
Status: Checking…
Ready to check API health.
User Search
Search by backend subject id or display name, then load the result into another panel.