Cases, notes and reviewed drafts

Cases optionally organize customer/device work, findings, notes and useful handback. Assignment, collaboration or closure never grants device access. Use explicit customer/device associations; installed software or enrollment organization strings do not infer a relationship. Preserve observed fact, source, original time, attribution, paragraphs and unknown/partial outcomes.

Customer-draft review

Create/edit a draft, show the human the complete text, exact recipient and revision, then review that exact version. Editing invalidates review. Only still-reviewed text is copied/downloaded for manual use. Browser, agent-relayed and Mech review share human-only authority; Mech consumes the authenticated controller proof, not a model's consent claim. CLI review uses --version and --recipient after human review, then reviewed-text --version --out to a new guarded private file. No automatic sending, attachment delivery or full CRM is implied.

Useful linked work

Original run/device/session IDs keep the result attributable. A failed/uncertain write retains draft and request identity for receipt reconciliation, not automatic retry. Reading stored reports does not collect diagnostics. Mech, diagnostics and API preserve the same authority.

Review and manually export

Only human-reviewed exact recipient/content revision can export. Changing the text invalidates review; no API sends the draft. Keep private guarded exports and original confirmation identity through uncertainty, never substitute a new revision.