Turn system work into decision reports a person can answer.
A report gathers the evidence, citations, and recommendation in one file. A private console puts decision cards on a board where the owner can respond.
Decision card layout
Report
Bottom line + inline citations
Today board
One decision per card
Owner response
Approve · No · Redirect · Comment
- One recommendation per card
- Evidence stays with the report
- Owner chooses the response
A fictional layout based on the report and console structure; no internal decision content is shown.
Turn long activity into a decision record.
The reports and console provide a compact review path for an owner who would otherwise reconstruct events from threads and terminal output.
Write the evidence report
Use a self-contained HTML file with a bottom line, citations, evidence, and a stated recommendation.
Put a decision on Today
Create a card with one recommendation, a summary, confidence, and context links.
Review privately
Use the owner's private connection when reviewing from another device.
Answer and keep the record
The owner responds. The answer is recorded in a ledger and the card is retired or kept for comment.
Keep the record tamper-evident and private.
Edits to the report console records can be detected; they cannot be prevented by this check.
Answer ledger
Each line hashes the prior raw line
Reordering is detectable
Edits, deletions, or reordering break the ledger verifier.
File route
../ path segments
Collapsed before allowlist check
The route checks the requested file against its allowlisted roots.
Reports, review cards, and the answer trail.
Every answer stays with the decision card it settled.
Decision reports
A clear recommendation with citations.
Reports and reviews can include a bottom line, evidence sections, inline citations, and questions a person can resolve.
Private console
A Today board and report library.
The console lists decision cards, reports, queues, and other owner review areas, with an append-only answer ledger.
Keep access on the owner's devices.
The console runs on the owner's machine by default. Other devices need an access key once, then stay signed in for 30 days; access stays private to the owner's devices.
Local files
Map the allowed report folders.
The file route serves allowlisted root folders. Keep private reports, credentials, and customer data out of public samples.
Remote access
Configure the private network path.
Remote use goes through the owner's private network; public cloud hosting is not provided.
Map the projects and decisions to surface.
This preview has no report upload, account connection, or remote access.
- Choose a review scope Name the projects and decisions the owner needs to see.
- Set the report roots Allow only the folders that the private console should serve.
- Keep the answer human The owner chooses Approve, No, Redirect, or Comment for each decision card.