User notes

Notes record what the analysis cannot know: that a procedure is no longer used, that a rule follows a regulation, who the functional contact for a module is or what the team decided for the migration. They live inside the documentation, so an AI agent reads them too.

Notes are added from the application (Viewer tab). If you open the viewer in a separate browser, they are visible but cannot be created or deleted.

Note on an object

1. Open the object in the Viewer.
2. In User notes, write the note and, if you like, your name in Author.
3. Click Save note.

The note appears on the page straight away, with date and author. Delete removes it.

Note on several objects at once

1. In Objects, filter the list (for example, by folder or by cluster).
2. Tick the boxes in the last column, or the header box to Select visible.
3. In the bar that appears above, write the note and click Add note to selected objects.

Each object receives its own copy of the note. The Notes column of the list marks which objects have notes.

Where they are stored

• In annotations/ inside the project, one JSON file per object. It is the source of truth: copy that folder if you want to take the notes to another machine.
• In the object's Markdown document, User notes section.
• In the object's JSON, user_notes field.

When you run the pipeline again on the same project (for example, with a newer export of the KB), the notes are merged into the regenerated documents again. If an object has disappeared from the KB, its notes file stays in annotations/ but is no longer shown.