approval-console

Packages raised judgment calls into decision requests and transcribes named human approvals into readiness artifacts.

2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Kemetra/Seshat-BI --skill approval-console-kemetra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: approval-console
Source: https://github.com/Kemetra/Seshat-BI/tree/main/.claude/skills/approval-console
Command: npx skills add https://github.com/Kemetra/Seshat-BI --skill approval-console-kemetra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Data readiness workflows stop at judgment calls (grain, PII, rollups, publish safety), but approvals given in chat are lost and cannot advance gates or be audited. This Skill closes the loop between a raised question and a recorded, committed human decision. ## Core Features & Use Cases - Decision Packaging: Renders a raised judgment call from unresolved-questions.md into a reviewable approval request with evidence, options, impact, and the required authority class, without ever answering it. - Decision Transcription: Writes a named human's answer into unresolved-questions.md (Resolution + status flip) and readiness-status.yaml (approvals[] entry with owner name and authority class), flipping a stage to pass only when required evidence already exists. - Refusal & Conflict Handling: Declines self-approval, wrong authority classes, phantom question IDs, duplicate requests, and silently overwriting prior approvals. - Use Case: A grain-confidence stop blocks a table's Gold Ready stage; the console packages the question for the data owner, then records their named answer so the gate can advance with auditable evidence. ## Quick Start Ask the agent to package the open judgment call in mappings/<table>/unresolved-questions.md into an approval request, then record the named human's decision back into the readiness artifacts.

Frequently Asked Questions about approval-console

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record a human approval in a data readiness workflow?▼

Package the open judgment call into an approval request, then have a named human supply their decision. The console transcribes it into unresolved-questions.md and appends an approvals[] entry with owner name, authority class, and date to readiness-status.yaml.

What is an approval console for data pipeline gates?▼

It is the loop between a raised judgment call and its recorded answer. It renders decision packages from open questions and writes the named human's answer back into committed readiness artifacts so gates can advance with auditable evidence.

Can the approval console approve a decision automatically?▼

No. It only transcribes decisions a named human supplies and refuses to pick options, supply owners, accept recommended defaults, or flip a stage to pass without both the approval and the stage's required evidence.

What authority classes are required for data readiness sign-off?▼

Four classes exist: analyst for business meaning and grain, governance for PII and publish safety, data-owner for source semantics, and metric-owner for metric contracts. A decision recorded under the wrong class is refused.

Why does a stage not flip to pass after an approval is recorded?▼

A pass flip requires both the named human approval and the stage's own required evidence, such as a live validation result. If evidence is missing, the decision is recorded and the gap is listed as a remaining blocker.