Record Notes
Internal note list and composer with authorship, timestamp, attachments, mentions and AI assistance.
/admin/leads/:id?tab=notesFuture Spec 14 →Current-state summary
The Notes tab is explicitly private team activity. The live record shows an empty state and Add note actions. Earlier product evidence shows authored timestamped notes that can be edited but not deleted, plus a modal composer with mentions, emoji, document attachment and Improve with AI.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Privacy label | Private team activity clearly separates Notes from external communication. | Verified live |
| Permanence statement | States notes can be edited but never deleted. | Verified live |
| List | Populated evidence shows author, timestamp, body and Edit action. | Verified from earlier evidence |
| Composer | Modal supports note text, @ mentions, emoji, attachment and AI improvement. | Verified from earlier evidence; save not retested |
| Empty state | Prompts the user to add context, decisions or follow-up details. | Verified live |
User journeys
Current flows
Add internal note
- Open Notes
- Select Add note
- Write or improve content
- Mention teammates or attach a document
- Save with author and timestamp
Edit note
- Open an authored note
- Select Edit
- Change content
- Save while retaining edit history
State model
Current and expected states
No internal notes with Add note action.
Modal presents author context, editor helpers and Save/Cancel.
Authored timestamped cards appear.
Allowed, but edit marker and revision access are unverified.
Product rules
Non-negotiable boundaries
- Notes are internal by default.
- Notes cannot be hard-deleted through the product.
- Authorship and original timestamp are permanent.
- Edits must create revision/audit evidence.
- AI assistance cannot introduce unreviewed facts or auto-save content.
- Mentions notify only authorized Workspace users.
Known current limitations · 5 mapped
What is missing, broken or unverified
Future Spec 14 owns closure →- Revision history and edited markers were not observed.
- Attachment limits, scanning and preview behavior are unverified.
- Mention autocomplete and notification delivery were not tested.
- There is no observed pinning, categorization or decision-note type.
- Client-visible notes require a separate, explicit model.
Future alignment
Required evolution
- 01Reuse Notes across records and Projects with explicit visibility classes.
- 02Add immutable revisions and source-linked Activity events.
- 03Provide note categories, pins and decision records without weakening simple capture.
- 04Keep AI suggestions reviewable and fact-preserving.
Current baseline
Acceptance record
- Notes are labeled private.
- Empty and populated states are defined.
- Add and Edit are available; delete is not.
- Composer helpers and AI remain user-controlled.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented