Work, expressed.

What the substrate produces A tabular data artifact, a data fidelity report, a cleaned dataset, an analysis brief, a deliverable plan, and a rendered downloadable presentation. A supervisor pause exists before the manager-visible deliverable is generated.

Governance boundary The v1 output is a downloadable deck artifact. External delivery to board portals, mailing lists, or shared drives is outside the current proof boundary.

Why this proves the claim The substrate handles work that begins with messy structured input and ends in an executive-ready artifact — turning data into a deliverable, not just text into more text.

What the substrate produces A questionnaire item set, an evidence bundle, drafted answers, and a completed internal package with coverage summary, unresolved items, and confidence indicators.

Governance boundary The v1 terminal boundary is a human-ready internal package. External customer submission, portal upload, email delivery, and connector-specific export are deferred.

Why this proves the claim The substrate completes knowledge work honestly — surfacing gaps and confidence rather than fabricating answers, and stopping at a human-ready boundary instead of pretending submission is automatic.

What the substrate produces A document ingestion bundle, a clause set, a playbook risk evaluation, a redline suggestion package with suggestion counts and high-risk items, and a drafting log.

Governance boundary The v1 terminal boundary is a human-ready internal package. Source-document mutation is not performed. Export, upload, email, and external delivery are deferred.

Why this proves the claim The substrate handles legal-sensitive review work without crossing into document mutation — analysis and suggestions are produced; the source remains the human's responsibility.

What the substrate produces An incident request, a postmortem plan, an evidence bundle, a reconstructed timeline, an analysis summary, a postmortem document, and a publication record. Failed publication produces an explicit failed publication record.

Governance boundary Confluence publication runs as a governed side effect after approval, when configured. Other publication targets are deferred.

Why this proves the claim The substrate connects evidence, sequence, analysis, writing, and governed external publication into one coherent flow — not just a write-up, but a record of what happened and where it was published.

What the substrate produces An onboarding request, an identity plan, a provisioning action log, a credential activation handoff where activation must be handled manually, and an access manifest.

Governance boundary Google Workspace account creation and Slack provisioning run through governed paths when configured. Connector coverage beyond Google Workspace and Slack, and provider-native passwordless activation invites, are bounded.

Why this proves the claim The substrate carries work where the output is not a document but a controlled change to organizational systems — and where unsupported automation produces an honest handoff rather than a fabricated path.

What the substrate produces A spend audit plan, a usage and spend evidence bundle, a waste analysis, license action drafts, and execution records. Failed execution produces explicit records.

Governance boundary Okta-style license revokes, downgrades, and user notifications run as governed side effects after approval, when configured. SSO and spend connector coverage beyond the v1 set is deferred.

Why this proves the claim The substrate separates "we found waste" from "we changed access" — exactly the boundary where real operational risk lives.

What the substrate produces An expense review plan, an evidence bundle, a policy evaluation, action drafts, and execution records. Unsupported paths fail closed with detailed records.

Governance boundary Expensify-style provider writeback and clarification email send run as governed side effects after approval, when configured. OCR, broader provider coverage, and finance-system reconciliation are deferred.

Why this proves the claim The substrate drafts actions without prematurely executing them, and fails visibly rather than silently when a path is unsupported.

What the substrate produces A screening request, an evaluation plan, candidate evidence bundles, resume evaluations, voice-screen bundles, voice-screen evaluations, a final shortlist, and a calendar scheduling record.

Governance boundary Candidate outreach and Google Workspace calendar scheduling run as governed side effects after approval, when configured. Hiring decisions, actual interviews, and ATS-of-record updates are outside the v1 boundary.

Why this proves the claim The substrate carries multi-stage evaluation work without collapsing the stages — evidence, scoring, screening, shortlisting, and scheduling each remain distinct and inspectable.

What the substrate produces A churn investigation plan, a churn evidence bundle, a root-cause analysis, a manager summary, and a delivery record. Invalid delivery targets produce explicit failed delivery status.

Governance boundary Slack delivery runs as a governed side effect after approval, when configured. Customer-facing remediation, CRM writes, and billing actions are deferred.

Why this proves the claim The substrate investigates operational signals while preserving confidence and gaps — internal diagnostic, not authoritative causality.

What the substrate produces A pricing monitor request, current and prior pricing snapshots, a change diff, an analysis summary, a delivery brief when a material change exists, and a delivery record. Baseline runs intentionally do not notify.

Governance boundary Slack delivery runs as a governed side effect after approval, when material changes warrant notification. Delivery channels beyond Slack and broader market-research synthesis are deferred.

Why this proves the claim The substrate distinguishes work that needs human attention from work that should resolve quietly — discipline about not notifying is a feature, not a gap.