bino-cli

Map raw source columns onto IBCS scenario slots (ac/pp/fc/pl), derive variances (d_/dr_), choose the grain, and write disciplined typed DataSet SQL for a bino report. Use when the bino-data autopilot phase models a source into datasets, or when co-authoring a DataSet. Owns the honest "the data can't satisfy this" — populate unmet[] rather than fabricate a column.

The IBCS rubric for bino reports — the semantics the schema can't carry. The SUCCESS rules (SAY · UNIFY · CONDENSE · CHECK · EXPRESS · SIMPLIFY · STRUCTURE), scenarios (ac/pp/fc/pl), variances (d_/dr_ … pos/neg/neu), analysis notations (_ ~ Ø ..), choosing between Table / ChartTime / ChartStructure / Tree, and data-aware narrative Text. Use when modeling a report's scenarios and variances, picking a visualization, writing commentary, or auditing IBCS compliance.

Elicit report requirements from the human and produce the REPORT BRIEF — the structured contract (audience, primary message, scenarios, variance, granularity, visualization intent, acceptance criteria) that the bino autopilot subagents consume. Use during /bino:autopilot phase 1 to turn a free-text goal into a brief. Runs on the main thread (it asks the human).

The four-layer VERDICT check (schema, IBCS, build-readiness, acceptance) and the bounded fix-loop policy for bino autopilot — diagnostic routing, the 2-iteration cap, and the stop-on-repeat rule. Used by the bino-validation subagent (to produce the VERDICT) and by the orchestrator (to drive the fix loop). Diagnose, never edit; PASS means "ready for sign-off," never "done."

The disciplined loop for authoring bino report manifests (YAML + SQL) through the bino MCP server — read the live schema, learn a dataset's columns, draft, validate_draft, write, then validate_project and build. Use whenever creating, editing, or wiring bino manifests (DataSource, DataSet, Table, Text, Tree, ChartTime, ChartStructure, LayoutPage, ReportArtefact, …) or fixing validation diagnostics. Pairs with bino-ibcs for the report semantics.

The bino autopilot policy — the phase sequence, the autonomy tiers, the four checkpoint gates, the eight hard safety gates, the run-start preflight, the subagent-spawn contract, and the fix-loop policy. Used by /bino:autopilot on the main thread to sequence the bino subagents and hold the gates. The orchestrator never authors or edits manifests — it routes.