Notes

A note says what a team needs to know about a dependency: why it is here, what must not change, what to check before an upgrade. In Depos a package has one note for the whole organization. The same note is what you see in the editor extension once you sign in, and what AI agents read over MCP.

A note has a human part (free text) and agent fields (a fixed field vocabulary, for tools and AI agents).

Writing a note

Write one from a package on Dependencies: open the package and use Add note in its Note card. Choose its scope: all repositories or selected repositories only. A note scoped to some repositories says nothing about the others.

Notes → All notes lists every note; editing and deleting are there as well.

Signed in from the editor extension, you read and (as an admin) edit the same notes in your editor; changes sync both ways. See Editor extension. AI agents read them over MCP: see AI agents.

Importing notes written offline

Without signing in, the editor extension writes notes into Markdown files committed beside the manifest (.depos/…/DEPENDENCY-NOTES.md, or .pacmon/… in older repositories). Depos reads those files when it scans a repository and offers what it finds for import in Notes → Review. It never writes to them.

• Only packages that have no note in Depos yet are offered. Once a package has a note, the note in Depos is the one that counts.
• One version: every repository that has a note for the package says the same thing. Admins can import all of these at once with Import N notes without conflicts.
• Conflict: repositories say different things. The queue shows each version with the repositories that hold it, the most common first. An admin picks one, or edits it, and saves it as the package's note.

A package leaves the queue the moment it gets a note. A note written into a repository later shows up after that repository's next scan. A repository's page lists its notes files, with any problems found in them.