Practice Chronology

---
name: practice-chronology
description: Build or update sourced matter chronologies, statements of facts and witness timelines while preserving contradictory evidence, privilege limits and source coverage.
---

# Chronology

This manually loaded instruction module is not a new setup module key or native
installed skill. Read [scope and authority](../../workflows/scope-and-authority.md)
and [source verification](../../workflows/source-verification.md).

## Resolve and collect

Use the installed matter workflow to establish the exact matter and applicable
save boundary. Reuse verified context still current for this task. An unresolved
or closed matter may receive conversation-only analysis under that workflow's
policy; do not create or replace canonical memory implicitly.

Use supplied sources first. Expand to the resolved folder or current correspondence
only when the requested chronology needs it. Before expansion read
[intake and lifecycle](../../workflows/intake-and-lifecycle.md), then use
actually available installed intake/extraction routes. Establish the source set,
date range, versions, supported formats and coverage limits. Unreadable material
goes to gaps, not guessed events. Stop dependent analysis when missing text could
change the chronology's material account.

Reuse an explicit privilege posture if one is recorded. Otherwise treat the
collection as mixed and unscreened. Tag sources as confidently usable externally,
potentially privileged or uncertain; uncertainty defaults to internal-only use.
These are working flags, not a legal determination. Disclosure, production,
waiver or a conflicting privilege instruction requires a lawyer decision.

## Extract and reconcile

For each source identify dated communications, meetings, decisions, filings,
transactions, notices and other relevant events. Preserve date/time precision
and timezone only as supported; describe partial or uncertain dates in prose.
Each entry states no more than the source supports and cites a retrievable source
plus locator. Sending, receipt, delivery, filing and service are distinct facts.

Keep four categories separate:

- sourced event;
- attributed allegation or party position;
- expressly labelled case theory;
- inference requiring judgment, kept in open questions rather than adopted as an event.

Combine duplicates into one event with all supporting sources. Preserve material
contradictions, including conflicting dates, as attributed assertions and explain
what remains unresolved. A later timestamp alone does not settle the conflict.
Do not resolve evidence or materially delete an event without controlling support
and the applicable lawyer approval.

When a newly encountered person/entity could be another client or a related
adverse interest, use the installed tracker's read-only screening path across
open and closed records. Record its search limits; raise candidate concerns with
minimum disclosure. Do not open another client's file or copy its particulars
into this chronology solely because a match appeared. Screening does not decide
a conflict or privilege question.

Tag significance against the instructed issues/theory: key, relevant or background.
Explain material theory connections as theory. A label indicates an initial
assessment, not a finding of fact or a deadline determination.

## Output and update

Read [chronology format](references/chronology-format.md) for a canonical artifact
or requested variant. A short conversational answer can omit the full format,
but every event still has a source. Read [dates](../../workflows/dates.md)
when an event suggests a live obligation; flag the candidate separately rather
than promoting an extracted event date to a legal deadline.

An update starts from the current chronology and retains existing source-backed
events, unresolved conflicts, privilege flags and coverage history. Inspect the
complete proposed change, identifying additions, corrections, duplicates and
material removals. Use existing guarded memory or artifact instructions as
appropriate; this module introduces no writer command or special memory schema.
Replacing canonical memory, timeline notes and other records requires exact
current approval. A requested new versioned chronology artifact follows existing
matter save policy. Never rename around a protected target or overwrite newer work.

Read [records and handoffs](../../workflows/records-and-handoffs.md).
Report the sources actually reviewed, entries/changes, verification performed,
remaining contradictions, privilege decisions and coverage gaps. Offer a requested
variant without implying authority for external use. Completion never authorizes
mailbox changes, calendar writes, sending, filing, service or disclosure.