Evidence
Real deliverables, redacted.
Examples follow the same frame: request, inputs, outputs, iteration, and result. Identifying details are removed. The workflow shape is not. No mockups.
Example 01 · Legal
Demand letter draft with source binding.
A litigation team uses unikode to assemble first-pass demand letters under playbook. The reviewing attorney approves before anything sends.
01Request · Inputs · Outputs · Iteration · ResultDemand letter · Matter #4821 · Sample · Redacted
Request
Draft a demand letter under the breach-of-contract playbook for Matter #4821. Cite claim basis, quantify damages from the invoices, and prepare the draft for attorney review by end of day.
Inputs
Engagement letter, eight invoice PDFs, a counterparty correspondence thread, the internal playbook, and the firm's exemplar set. Sources carry through as bound references.
Scope captured
Matter, playbook, reviewer, and deadline are confirmed before drafting starts.
Sources parsed
Invoices are tabulated, damages are computed, and the correspondence is sorted under the playbook headings.
Draft assembled
The letter surfaces with source references and one flagged figure for review.
Iteration
The reviewer tightens claim language. The affected section is re-drafted without losing provenance.
Approved
Attorney approval is recorded and the letter routes through the firm's existing dispatch path.
Typical time from request to approved draft in this engagement: 2.3 hours. Attorney review averaged 14 minutes.
Example 02 · Engineering
Technical report with calc-package cross-reference.
A specialist engineering consultancy uses the same evidence frame for a report that cross-references a calc package and a governing specification. The signing engineer reviews before release.
02Request · Inputs · Outputs · Iteration · ResultTechnical report · Project Lattice · Sample · Redacted
Request
Assemble a technical report for Project Lattice against the approved calc package and the governing specification. Flag mismatches for engineer review.
Inputs
Approved calc package, the governing specification, prior-phase report, site drawings, and the firm's report template. References stay attached to the draft.
Scope captured
Revision, specification set, deliverable structure, and review deadline are confirmed up front.
Sources parsed
Calc-package values are indexed and specification clauses are tagged for cross-reference.
Draft assembled
The report surfaces with 47 cross-references and two mismatches flagged for review.
Iteration
One mismatch resolves through an errata update and another returns for clause clarification.
Approved
Engineer approval is recorded before release through the firm's normal delivery path.
Typical time from request to approved draft in this engagement: half a working day compared with a prior median of three.
End-to-end timeline
One engagement, day level.
An anonymized pilot from intake to approved deliverable. Day 0 is the scoping conversation. Everything after runs under the agreed review posture.
Scoping conversation
Objective, deliverable, reviewer, and time box are agreed in a short kickoff call.
Workflow wired
Templates connect to the source repository and reviewer roles are configured under a dry-run check.
First draft produced
The workflow runs on a live request and surfaces a draft with bound references.
Review and revision
Reviewer notes return, affected sections are revised, and the change history stays attached to the draft.
Approved deliverable
Reviewer approval is recorded and the deliverable routes through the firm's existing release workflow.