Report which readiness stage each table currently sits in.

Use when: you need the overall readiness picture, or one table's stage, evidence and blocker list. Not for: why a stage is blocked (use seshat_explain_blockers) or what may be done next (use seshat_get_next_action). Returns: a projection listing each table with its current stage of the seven (source_ready .. publish_ready), evidence and blockers. Outcome is 'ok' unless an input is malformed. Read-only: reads committed files under the workspace and writes nothing.

Return the one action readiness allows now, and refuse anything past it.

Use when: you need the single permitted next step, or want to check an intended action is allowed before starting it. Not for: the full stage picture (use seshat_get_status) or blocker detail (use seshat_explain_blockers). Returns: one allowed action plus forbidden scope, the stop point and the authority required to go further. Outcome is 'blocked' when requested_scope is forbidden or a named-human decision is outstanding. Read-only: names the action but never performs it, and grants no approval.

Explain what blocks one table's next stage, and who can clear it.

Use when: a table is not advancing and you need the concrete reason, the missing evidence, the owner, and the recovery action. Not for: an all-table overview (use seshat_get_status) or picking the next step (use seshat_get_next_action). Returns: one entry per blocker for the named table. Outcome is 'blocked' when blockers exist and 'ok' when none do. Read-only: reports blockers and never clears, waives or overrides one.

Draft the request a named human must rule on, approving nothing.

Use when: readiness needs a human ruling and you want the request assembled with its supporting issue and the authority required. Not for: granting, recording or standing in for an approval -- no tool here can do that, and a human signs off outside this server. Returns: a request with status 'prepared_not_approved', the requested authority and the supporting issue. Outcome is always 'blocked', by design, because preparing a request advances nothing. Read-only: writes no approval receipt and grants no readiness.

Run the static governance rules and state what was not checked.

Use when: you want committed SQL, TMDL, PBIR and readiness artifacts checked against the shipped rule set without any database. Not for: live data validation -- that needs a database connection and stays a separate CLI operation this server never performs. Returns: the findings, plus a boundary object recording that live_validation was 'not_run' and that semantic correctness is not claimed. Outcome is 'blocked' when any finding is error severity. Read-only: opens no database connection and writes no file.

Assemble one table's evidence pack in memory and return it as data.

Use when: you need a table's collected readiness evidence to review or hand off, as a structured response rather than a file. Not for: writing the pack to disk -- despite the name nothing is exported, and file export stays an explicit CLI operation. Returns: the evidence-pack projection for the named table with any blockers. Outcome is 'input_defect' when the table cannot be resolved. Read-only: creates nothing on disk.