bino-report

Probe a CSV / Excel / database source and scaffold a typed DataSource (and optional DataSet).

Autopilot — delegate the full requirements → data → authoring → validation → build pipeline to bino subagents, pausing only at safety gates. Tier 1 (checkpointed).

Render the bino report artefacts to PDF.

Validate the bino project and walk the diagnostics to green.

Scaffold a fresh bino report bundle (bino.toml + sample manifests) ready to build or preview.

Autopilot authoring subagent. Chooses IBCS components, drafts report manifests against the live schema, validates every draft before writing, wires embeddable → LayoutPage → ReportArtefact leaves-first, and authors the data-aware narrative Text tied to the brief's primary message. Sole editor of report-structure manifests. Never touches DataSource / DataSet.

Autopilot data subagent. Locates and profiles sources, maps raw columns to IBCS scenario slots (ac/pp/fc/pl) and variances, authors typed DataSet SQL, runs the single data-validation pass, and produces the DATA PLAN. Sole editor of DataSource / DataSet / ConnectionSecret. Owns the honest "the data can't satisfy this."

Autopilot guardrail subagent. Runs a four-layer check (schema, IBCS C1–C14, build-readiness, acceptance spot-checks) and emits a VERDICT with per-diagnostic routing. Diagnoses, never edits, never builds — a judge that wields the pen is not a guardrail.

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.

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. Scenarios (ac/pp/fc/pl), variances (d_/dr_ … pos/neg/neu), choosing between Table / ChartTime / ChartStructure, and data-aware narrative Text. Use when modeling a report's scenarios and variances, picking a visualization, or writing commentary, so the report is IBCS-compliant.

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.

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).