Annotations

Annotations

Annotations are review threads attached to an exact piece of Holaryn work. Open Annotations in
the main navigation to review all notes in a list that works without locating a visual marker.

Create a review note

Under Anchor a review note, choose:

• Message text for an exact range of a chat message;
• Plan step for a plan and node;
• Diff lines for a file range between exact revisions;
• Artifact region for a sheet cell, slide region, document section, or other named region.

Enter stable target identifiers and the target version or revision. Add the selected quote when
text exists; it makes safe remapping more reliable. The review note is required. You can assign it
and choose private, session, project, or workspace visibility.

Example review note:

Keep the word “Nightly” in the release heading and show prerelease status before the download
action. @release-owner

The created card shows its full target identifier, version, selected quote, anchor state, author,
assignment, and replies. These states are always written as text; color is only supplemental.

Review and lifecycle

Use Reply, Edit, Delete, Resolve, and Reopen on each thread. Each mutation uses
the version you are viewing. If another reviewer changed the thread first, Holaryn reports a version
conflict instead of overwriting their work; refresh and reconcile the newer version.

Press Alt+Down Arrow or Alt+Up Arrow to move between annotation cards. Previous and
Next provide the same operation. The page announces create, reply, edit, resolution, remap,
and action results, and returns focus to the changed thread.

Filter the list by lifecycle state, anchor kind, or exact target identifier. This list-first
workflow is the accessible fallback for every surface, including content that has no inline
marker.

Changed targets and orphaned notes

Choose Check a newer target version when the message, plan, diff, or artifact changed. Supply
the new exact version and its current text. Holaryn first tries a unique exact quote and context,
then a conservative high-confidence match. The card shows the method and confidence.

When the match is absent or ambiguous, the note becomes Orphaned and stays at its original
location. Holaryn never guesses silently. Update the target data and try again, or resolve the note
after manual review.

Ask the agent to act

Under Queue scoped agent work, name the existing chat session, say what to do, and state the
acceptance check. For example:

Prompt:

Update only the selected release heading to preserve the Nightly qualifier.

Acceptance request:

Show the final heading and confirm no stable-channel wording changed.

The queued turn includes the exact annotation and target version as untrusted review context. It
still uses the selected model, context limits, organization policy, and normal approvals.
Annotation text cannot grant permission or override instructions.

Privacy, export, and deletion

Target access and annotation visibility are checked independently. A workspace-visible note does
not reveal a target from another workspace, and a private note is visible only to its author,
assignee, or an authorized administrator.

Deletion redacts the live body while keeping a versioned audit event. Authenticated exports contain
only threads and audit events the caller may view. Annotation records live in the local Holaryn state
directory and follow its backup and filesystem-security boundary.