Notes

A note in BNDRY is a free-text observation written by an operator against a customer record. Notes live in the platform layer and are always attached to either an entity or a workspace. They are the place to record the things that don't fit into structured fields — the reasoning behind a review decision, a phone call summary, a flag for the next reviewer to read.

Why notes exist

Structured data captures what. Notes capture why. A risk rating, a screening outcome, or an identity check tells you the conclusion the platform reached; a note from the operator who made the call tells you the context behind it. Without that context, a later reviewer or auditor is left to reconstruct intent from timestamps and field values, which is both slow and fragile.

BNDRY treats notes as a deliberately lightweight collaboration and audit-trail tool. Anyone with access to the parent record can read the notes attached to it, so the operational story of a customer record is visible to everyone working on it. Authorship is recorded automatically, edits are tracked, and only the original author can change or delete what they wrote — so the note thread reads as a faithful record of who said what and when.

Key properties

A note is intentionally simple:

• Content — the free-text body of the note. There is no length limit beyond a non-empty minimum.
• Author — the user who wrote the note, captured automatically by the platform. Both the author's identifier and their display name are stored, so the note remains attributable even if the user's display name changes later.
• Created and updated timestamps — when the note was first written and when it was most recently changed.
• Edited flag — set automatically when the note has been modified after creation, so readers can tell at a glance whether what they're reading is the original or a revision.

Notes are scoped to their parent. A note against an entity travels with that entity; a note against a workspace belongs to that workspace. The note's resource name always carries the parent in its path, which keeps the access boundary explicit and prevents notes from drifting between unrelated records.

How notes relate

Notes complement documents and files. Where a document holds structured identity data and a file holds the raw upload, a note carries the human commentary around either — why a document was accepted, what was unusual about a file, what to watch for next time. Notes attach to the same entities and workspaces that those structured artefacts hang from, so the operational thread for a record sits next to its data rather than being filed away separately in email or chat.