Educational workflow guide
Hermes Agent resources / Office review
This guide presents reviewable Excel, Word, and presentation workflows as an educational planning exercise. It explains inputs, proposed changes, verification, and undo boundaries; it is not hands-on testing and not evidence of released capabilities.
// A four-part review loop
A good Office workflow separates what the agent is allowed to see from what it is being asked to change. The sequence below is an educational pattern for planning and review, not a report that a particular product route has completed it.
Identify the host, file or document copy, selected sheet/range or text selection, intended audience, and the exact source material. Keep sensitive data out until the provider and destination are understood.
Describe the named range, paragraph, slide, formula, style, or structure to change. Prefer a small proposal that states the target, expected result, and whether the action is a read, suggestion, or mutation.
Compare the changed values, formulas, tracked edits, formatting, slide order, and notes with the original intent. Re-read the affected context and record anything that needs human correction before proceeding.
Use an explicit copy, version, host undo history, or other documented restore path. If you cannot explain how to reverse the change, do not treat a preview or educational example as ready for real work.
// Spreadsheet example
An educational spreadsheet pass might begin with a named worksheet and small range, ask for a formula or formatting proposal, and verify the resulting values and formulas before anyone accepts the change. A copy of the workbook and the host’s undo or version history provide the restore boundary.
// Document example
For a document, define the selected passage or bounded section, ask for a proposed revision or proofreading review, and inspect the diff, tracked changes, comments, or equivalent host evidence. Accept only the intended edits and preserve a document version or undo path before applying a wider change.
// Presentation planning
For a presentation, the inputs could be an outline, selected slides, speaker notes, or a brief. Proposed changes should identify the target slide and content, verification should be slide-by-slide, and undo should rely on the host’s own version or restore controls. The AtlasOmnia PowerPoint page is marked Coming soon; this guide does not expand its claims.
// Before any real document
