One directive for document work that still needs structure, artifacts, and a final file.
FileMorf Operator reads the source, decides the right sequence, preserves the useful intermediate outputs, and renders a final PDF when you need a finished handoff.
Start with a fresh upload here, or reuse a retained document from your workspace when the file is already in motion.
Example run
One source. One clear outcome.
Request
“Put the content in this document in a table, make it aesthetic HTML with thoughtful colors, and deliver a final downloadable PDF.”
Inspect
Reads the current workspace capabilities and the source file shape before it plans.
Plan
Builds a strict execution graph instead of relying on a single monolithic prompt.
Operate
Builds the requested outputs, keeps the useful artifacts, and renders the final file when the request needs it.
Outputs
Structure + routing
Inspect how the source was parsed before the operator composes outputs.
HTML, JSON, Markdown
Retain the editable artifacts the run produced, not just the last message.
Final PDF only when requested
Queue rendering after the right intermediate artifact exists.
Output shelf
Built for reports, field packs, signature audits, redaction, and packet routing.
One working view
Keep upload, execution, and inspection in one place.
Bring in the source, guide the run, inspect the structure, and leave with outputs you can still reuse.
Start with a fresh file
Upload a PDF, DOCX, spreadsheet, markdown file, or structured document without setting up extra steps first.
Guided multi-step runs
Operator reads the source, lays out the work, and moves through it in sequence so the result stays organized.
Keep the useful outputs
Save HTML, Markdown, JSON, summaries, routed bundles, and the final PDF when you need a finished handoff.
Directive examples
Built for real document work that still needs clean handoff.
Put this policy in a thoughtful table, make it styled HTML, then deliver a final PDF.
Extract invoice number, due date, amount, and vendor, then build a clean summary pack.
Split this packet into contract, invoice, and appendix bundles and save Markdown for each.
Audit this document for signatures and approval markers, then create a downloadable PDF report.
Why it stays usable
Controlled execution
Each run follows a controlled sequence of document steps so the output stays inspectable instead of becoming hard to trace.
Reusable artifacts
Keep HTML, Markdown, JSON, summaries, and bundle outputs when those are more useful than a single final file.
Final PDF when it matters
Rendering happens at the end of the run, after the right intermediate output exists and the handoff is actually ready.
Start with one file
Open Operator, upload a source, and run the first directive.
Use Operator from the documents workspace when the file is already retained. Start here when the work begins with a fresh upload and a directive.