Professional artifacts
Professional artifacts
Holaryn can create polished Word documents (.docx), Excel workbooks (.xlsx),
PowerPoint presentations (.pptx), and PDF files as durable, reviewable artifacts. Ask in
ordinary language, for example:
Create a two-page launch brief as a Word document. Include an executive summary,
milestones, risks, and a table whose nonvisual description says it lists the release
owners and dates.
The agent uses a typed document specification rather than writing arbitrary Office XML. A
separate, resource-bounded worker creates the file, reads it back structurally, produces
deterministic previews, and records validation evidence. The binary file is never placed back
into the model conversation.
Review an artifact
Open Artifacts in the Chat sidebar, open an artifact's menu, and choose Review
versions…. The workspace shows:
- the target format, current immutable version, status, and validation summary;
- every current and prior version with byte size, semantic summary, and exact download;
- one preview for each document section, workbook sheet, presentation slide, or PDF page;
- structural, visual, and accessibility results, including the exact page, slide, sheet,
cell, or section affected by a warning; - the operation and actor that produced each revision; and
- a semantic comparison between any two versions.
A generated preview is evidence, not a promise that the file looks correct in every
third-party application. Review the current version's previews before relying on its layout.
For high-impact distribution, also open the downloaded file in the target Office or PDF
application.
Revise without losing history
Ask for a change and name the artifact when several are present:
In the Launch brief artifact, version v2, add a Verification section stating that the
Windows, macOS, and Linux package checks passed.
Revisions name their exact base version. If somebody has already created a newer version, the
stale revision is refused instead of overwriting it. Supported high-level changes include
replacing a semantic specification, appending a document section or PDF page, updating
workbook cells or charts, and adding or updating presentation slides. Earlier versions remain
downloadable and comparable.
Canvas can display a professional-artifact card pinned to an exact version, with an optional
validated preview and exact download. Code and chat sessions use the same artifact tools and
version store. The public automation API returns the current format, status, version id,
version count, validation summary, content digest, and authorized download.
Format behavior
Word
Documents support a title, subtitle, author, language, heading hierarchy, paragraphs, tables,
captions, nonvisual table descriptions, and review comments. Missing table descriptions are
reported as accessibility warnings.
Excel
Workbooks support named sheets, typed values, formulas beginning with =, number formats,
basic heading/currency/percent/date styles, bar/line/pie charts, chart descriptions, hidden
sheets, and sheet summaries. Preview and validation locations name the sheet and, when
applicable, the cell.
PowerPoint
Presentations support titled slides, subtitles, bullets, speaker notes, and a required visual
description for every slide. The preview list and validation findings use one-based slide
numbers.
PDF creation supports titled pages, paragraphs, annotations, basic form-field descriptions,
author metadata, and required page descriptions. The worker reopens the emitted PDF before
recording structural success.
Templates and repeatable work
For repeatable output, describe the desired structure once and ask the agent to reuse that
structure in later artifacts. A project instruction or skill can hold the headings, required
sheets, slide sequence, field names, tone, and accessibility requirements. Record an approved
artifact version as the visual reference and compare later output against it.
This release does not import arbitrary .dotx, .xltx, .potx, macro-enabled Office files,
remote templates, embedded documents, or external-linked assets. That limit is intentional:
unknown templates can carry macros, hidden data, tracking links, or unsupported relationships.
Convert a trusted template into a plain semantic structure instead.
Privacy and safety
- Artifact content and previews use the same optional encrypted-state protection as other
local artifact payloads. Metadata such as identifiers, formats, sizes, timestamps, status,
and digests can remain visible as documented in Encrypted local state. - The renderer receives a minimal environment without application secrets. It cannot open
network connections or start child processes. - Generated Office packages contain no macros or external relationships. Rendering is bounded
by request, result, preview, node, text, page, slide, sheet, time, and file-size limits. - Artifact routes require the host's normal authorization and serve content with no-sniff,
anti-framing, sandbox, and restrictive content-security headers. - Validation findings and content are untrusted data. Do not put passwords, API keys, signing
material, or regulated personal data into a prompt or template unless your provider and
local retention policy explicitly allow it.
Deleting an artifact removes its version rows and locally managed payloads. Exports or files
you already downloaded are separate copies and are not recalled.
Recovery and troubleshooting
If creation fails, no artifact version is committed. If a revision fails, its staged payload is
removed and all earlier versions remain current and readable. Retry with a smaller document or
correct the named validation problem.
For Python-package installations, install the document adapters:
pip install "holaryn-agent[documents]"
uv tool install "holaryn-agent[web,documents]"
Desktop and official Compose builds already include them. If an artifact remains needs
review, open its version workspace: an empty sheet, missing table/chart description, malformed
range, unsupported operation, or inaccessible structure is reported at the closest available
locator.