Record History
Audit-oriented history of state, ownership and field changes.
/admin/leads/:id?tab=historyFuture Spec 14 →Current-state summary
History appears as the final record tab but is now disabled and labeled Coming soon, correcting the earlier Overview fallback. There is still no dedicated audit-oriented list of state, ownership, field, automation or conversion changes. Activity is a separate working tab, and the Overview action labeled View complete history currently opens Activity, so the language boundary between operational Activity and immutable History remains unresolved.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Tab | History is visible, disabled and labeled Coming soon. | Verified live |
| Interaction | Cannot be selected and no longer replaces the body with Overview. | Verified live |
| History list | No dedicated content exists. | Absent live |
| Change detail | Before/after values, actor and source are not exposed. | Absent live |
| Filters/export | Not implemented on this surface. | Absent live |
User journeys
Current flows
Encounter planned History
- Review record tabs
- See History marked Coming soon
- Use Activity for current operational events
Investigate conversion
- Open History
- Locate conversion event
- Follow source opportunity and created Project
- Verify idempotency and actor
State model
Current and expected states
Visible and disabled.
No dedicated empty state.
Not implemented.
Redaction behavior not implemented or visible.
Product rules
Non-negotiable boundaries
- Audit history is append-only and server-authored.
- Critical changes retain actor, timestamp, source, before/after meaning and correlation ID.
- Sensitive values are redacted without erasing the fact of change.
- Activity may summarize work; History preserves audit detail.
- Automations and integrations are identified as non-human actors.
Known current limitations · 4 mapped
What is missing, broken or unverified
Future Spec 14 owns closure →- Dedicated History content is missing.
- Activity/History boundaries and the View complete history label are inconsistent.
- No before/after, actor, correlation, export or retention behavior is evidenced.
- Coming soon provides no alternate audit access for authorized operators.
Future alignment
Required evolution
- 01Define the Activity versus Audit History contract in Spec 14.
- 02Create normalized human-readable event copy backed by immutable data.
- 03Add critical-change filters, correlation and authorized export.
- 04Replace the disabled placeholder only when dedicated empty, populated, restricted and failure states exist.
Current baseline
Acceptance record
- History is visibly disabled and labeled Coming soon.
- History is not conflated with the working Activity timeline.
- Audit integrity and redaction rules are recorded.
- A functional release requires dedicated empty, populated and restricted states.
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