Product · Revise
Edit by voice. Hold every change in diff.
Revise is the surface where the engineer's licensed judgment lands on the draft. Voice or keyboard, every change is highlighted, nothing auto-submits, nothing auto-seals — and the destructive paths step out of the way until the engineer has decided.
The review surface is where Fermito earns the word assistant. The engineer is always the author.
What revise does
Four guarantees the review surface enforces.
Each one exists because a generic AI tool would skip it — and because skipping any of them would compromise the practitioner's authorship of the report.
01 · Voice review
Edit in plain language. The engineer talks; Fermito moves the words.
An engineer reads the draft and says "change three plies to two plies in the LVL beam observation, and add that the hold-down at gridline C is still outstanding." Fermito interprets the instruction, locates the right places in the draft, and stages the edits. The mic disables itself the moment the engineer focuses an inline field — no accidental double-edits.
Whisper transcription · Claude-interpreted change set · focus-aware mic gating
02 · Diff in the document
Every change is highlighted in copper. Nothing moves silently.
Edits land as proposed changes — a copper wash on the words that moved, an underline beneath the runs Fermito wants to add. The engineer sees the entire surface area of the change before deciding. Approve commits the diff; Undo discards it. There is no third option that quietly partially applies.
Copper-wash diff · Approve / Undo · ancestor-aware path highlighting
03 · Inline correction
Every field is editable. Keyboard never loses to the voice path.
Voice is the differentiator, not the only path. Any text in the draft can be clicked and rewritten directly. The two paths interleave freely in a review session — voice for sweeping changes, keyboard for the surgical word a senior wants to swap. Both write to the same diff stream the engineer is reviewing.
Inline EditableText · keyboard + voice into one revision history
04 · Held until decided
Save, regenerate, and export are blocked while a revision is pending.
When changes are staged but not yet approved, the destructive surfaces of the product step out of the way. Save, regenerate, and export refuse to run. The engineer cannot accidentally export a draft that contains an un-reviewed Fermito edit. The product surface enforces the review gate; the engineer does not have to remember to.
Pending-changes banner · save/regenerate/export gated · explicit Approve required
Authorship, in practice
The engineer is the author of the report. The product enforces it.
Under PEO Practice Bulletin — Use of AI Tools, a practitioner is responsible for every word in a sealed document regardless of how it was drafted. Fermito’s review surface is designed so that responsibility is exercisable: every change is visible, no edit moves silently, and the engineer cannot reach the export surface with un-reviewed AI changes still on the page.
Revisions are kept in memory as a pending change set against the previous state of the draft. Approve commits the change set in one step. Undo discards it. The model used for the revision pass is recorded against the change set for the firm’s own audit purposes — Fermito does not pretend the AI was not involved, and it does not let the involvement disappear into the document.
Voice instructions stop the moment an inline field takes focus, so a keyboard correction cannot be misheard as a new voice instruction. The two input paths share one revision history but never collide.
Next surface
The draft is approved. The export is in the firm's hand.
Export delivers a DOCX in the firm's house format — header, footer, signature block, distribution list — ready for a PE to seal.