Read-only console
Inspect History in the console
A read-only, authenticated console for browsing workspaces, scopes, UTC days, and the exact revisions behind them through existing History API reads.
See exactly what was recorded, without a write path and without falling back to the latest value.
In short
A read-only console where signed-in operators browse workspaces, scopes, and UTC days and see the exact revisions behind each record. It never writes and never substitutes a newer value for the one requested.
Available today: Implemented in website source. Not yet connected to a live History deployment.
Implemented in website source and tested against fixtures. No live History deployment exists for it to read yet, and it reads nothing until its server settings are configured.
Browse History like folders
Workspaces
The History API lists the workspaces your account may read, with your role.
Scope
Registered scopes are listed when the deployment enables its delivery status read; otherwise a subject and record type are opened by name, and the console says why.
UTC days
Pick a month, then a date inside today and the preceding 364 UTC dates. Being in the window is eligibility, not a claim that the day is complete.
Exact records
One page of a pinned generation is hydrated to exactly those revisions; the inspector adds timestamps, source references, and the record’s earlier revisions.
Sign in with your Kam account
The console uses the same Amplify email/password sign-in as the Kam app. The server reads the session, re-verifies the Cognito access token with AWS’s verifier, and calls the History API on your behalf. Which workspaces you see comes from the History API, never from the browser; a refusal is shown as access denied, never worked around.
What the console will not do
Write anything
Only read routes are called. There is no outcome, configuration, deletion, or lifecycle action.
Fall back to latest
A changed generation or a revision that does not match the requested reference is an error, not a substitution.
Read without bounds
At most 32 references per read, only inside the 365-UTC-date window, and never a cursor without its generation.