Intelligence Timeline

What is the Intelligence Timeline?

The Intelligence Timeline is the shared history layer for every entity in your organization. Whenever structured context is added, updated, verified, questioned, or corrected — on a person, business, file, idea, or any other entity type — the timeline records what happened, who did it, and when. Think of it as the memory of your Intelligent Registries: not just the current snapshot of data, but the full story of how that data got there.

Screenshot placeholder Knowledge Timeline or entity detail timeline view — chronological events with contributor avatars, event labels (added context, verified, updated), and expandable event cards.

One timeline per entity, scoped to your organization

Every instance (one specific contact, business, document, etc.) has its own Intelligence Timeline. Events on that timeline are scoped to your organization — other organizations never see your facility’s history.

Scope	Meaning
Organization	Timeline events belong to your org’s facility — the audit trail your team shares
Entity instance	One timeline stream per record — all context types on that entity feed the same history
Workspace (when applicable)	Some events may also carry workspace context for multi-workspace setups

When an agent or teammate enriches a contact in Contact Book, adds context in Entity Manager, or an Action ingests data through a context operation, the timeline captures that moment for your organization.

Intelligent Registries unify what used to be scattered per-entity histories. Whether you work on people, businesses, or custom entity types, the same timeline model applies.

How it brings data together

Context in Intelligent Registries lives in many shapes — contact information, work history, notes, custom JSON payloads, and more. The Intelligence Timeline stitches those changes into one ordered stream instead of leaving silent edits across disconnected tables.

  Add context          Update field          Verify record
       │                    │                      │
       ▼                    ▼                      ▼
  ────●────────────────────●──────────────────────●────► time
       │                    │                      │
   Event 1              Event 2                Event 3
   (sequence)           (sequence)             (sequence)

Each event knows:

Which context was affected (work history, a note, primary contact fields, etc.).
What changed — new values and, when relevant, what they replaced.
Why it matters — optional context messages explaining the change.
Where it came from — a team member, an automated system step, or an integration.

That is how disparate context types become a coherent narrative on one entity.

Diagram placeholder Center: one entity (e.g. “Jane Doe”). Orbiting context type chips (Contact info, Work history, Notes) each with arrows into a vertical timeline spine on the right. User-facing labels only.

Audit trail you can trust

The timeline is designed for accountability, not just display.

Sequential ordering

Events receive an ordered sequence number per entity within your organization. That ordering is stable — you can reconstruct exactly what happened after what, even when multiple people edit the same record.

Contributors

Every event records who contributed:

Contributor	Examples
Human	Team member added context, verified a field, flagged an issue
System	Automated ingest, action pipeline, background enrichment

You always know whether a change came from a person or an automated step.

Before and after

Update and correction events can carry previous and new values. That makes audits and dispute resolution practical — you are not guessing what changed; the timeline shows it.

Verification and flags

Event style	What it means
Verified	Someone attested that information is accurate
Flagged	Someone marked data for review (with severity when configured)
Corrected	A deliberate fix to earlier information

Verification status travels with intelligence records so unverified data can be filtered or highlighted in the UI.

Video placeholder (Screen Studio) Walkthrough: open a contact → Knowledge Timeline → expand an event → show verify action → filter to verified-only records on an experience tab.

Flow of information — branches, questions, and lineage

Not every change is a straight line. The Intelligence Timeline supports richer flows:

Parent and root events

Some events link to earlier events — for example, a structured record extracted from a note references the note event that spawned it. Root events anchor whole chains so you can trace intelligence back to its origin.

Branches

When conflicting or alternative versions of information exist, events can branch — parallel lineages with names (like git branches for context). Teams compare alternatives without overwriting history silently.

Questions and responses

The timeline supports questions asked about data and responses that resolve them — useful when an agent or teammate needs clarification before committing structured context.

Archive and merge

Lifecycle events — archiving outdated context, merging duplicates, setting primary when multiple versions exist — all land on the timeline so nothing disappears without a trace.

Screenshot placeholder Branch timeline graph view — multiple lanes or branches showing parallel event chains converging or diverging. Include legend for branch names.

What creates timeline events?

You do not manage the timeline manually event-by-event in normal use. Events are created automatically when work happens:

Source	Examples
Add context	Agent chat extracts work history; manual form saves a note
Context operations	Ingest, update, or upsert through saved operations
Contact Book workflows	Add Context chat, intelligence enrichment, profile updates
Entity Manager	Creating instances, attaching context types
Integrations & Actions	Pipelines that write registry data on triggers

Common event categories you may see labeled in the UI:

Context added — new structured information captured
Intelligence created — a derived record (experience, skill, etc.) linked to source context
Updated / corrected — field or record changes
Verified — attestation of accuracy
Flagged — review requested
Question / response — clarification loop
Archived — information retired but preserved in history

If data looks wrong, check the timeline first — the correction event tells you when it changed and often who changed it.

Where you see the timeline

Contact Book — Knowledge Timeline

For people entities, the Knowledge Timeline tab on a contact’s detail view is the richest timeline experience — searchable, filterable, with branch graph visualization and contributor highlighting. Individual context tabs (Experience, Education, Skills, etc.) also show intelligence cards tied to timeline-backed records, including verification badges.

Screenshot placeholder Contact Book → contact detail → Knowledge Timeline tab with header filters and event list.

Entity Manager

When viewing an entity in Entity Manager, unified timeline events appear alongside structured context — the same audit trail, oriented toward registry administration.

Registry pages — Mapped timeline

Registry components such as Mapped timeline render chronological context on composed pages — useful on detail shells and dashboards.