Reverse spec drafted

Activity timeline

Chronological, filterable record of external touchpoints, internal work and changes.

Observed routeShared componentFuture Spec 16 →

Current maturityWorking chronological projection with audit-boundary ambiguity

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

The Project Opportunity Activity tab provides counts, search, channel/category filters and a chronological timeline for tasks and internal notes; Overview shows a compact recent projection. The component is reusable, but customer-centric copy is too narrow for Designer and Provider touchpoints, and current History surfaces can show the same events instead of a distinct audit ledger.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Summary	Total events, external touchpoints and record changes.	Verified
Filters	Search, channel and category filters.	Verified
Timeline	Dated event cards with actor, time, visibility and type.	Verified
Overview projection	Recent event subset links to full history.	Verified
History boundary	Separate History tab may duplicate Activity.	Verified conflict

User journeys

Current flows

Review record Activity

Open Activity
Review counts
Filter by type/channel/date
Open event context
Follow authorized linked record
Distinguish audit-only changes in History

State model

Current and expected states

No events

Expected; not captured.

Populated

Task and Note events shown.

Filtered

Controls exist.

Redacted

Not explicitly evidenced.

Product rules

Non-negotiable boundaries

Activity contains participant-readable operational events.
History contains immutable audit changes and security-relevant actions.
Visibility is stored per event and never inferred only in UI.
Event payloads reference canonical records and safe snapshots.
External touchpoint replaces ambiguous customer touchpoint.

Dependencies

Spec 14Domain EventsAudit ledgerCommunicationsPermissionsSearch/indexing

Known current limitations · 4 mapped

What is missing, broken or unverified

Future Spec 16 owns closure →

Activity and History overlap.
External participant language is inconsistent.
Redaction, retention and export are unverified.
No communication events exist yet.

Future alignment

Required evolution

01Separate Activity projection from audit ledger.
02Add Project, Provider, commercial, receiving, delivery and communication events.
03Define retention and privacy behavior.

Current baseline

Acceptance record

Every event has stable type, actor, timestamp, visibility and canonical link.
Activity and History are never interchangeable.
Counts follow the same filtered authorized dataset.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented