Track time

nightwright’s primary time signal is passive: Claude Code and Cursor transcripts (plus Outlook meetings). You do not start a timer for that. Org clock-in / clock-out is supplemental wall-time on an idea while you build a slice — see Clock.

Weekly loop

1. See what landed

nw                               # dashboard
nw report --week        # this week by topic
nw report --week --by project

1. Name the unknowns

nw topics --unmapped
nw map <raw-topic> project=Name area=…

Facets (project=, area=, …) are how reports group. Bare nw map topic value sets bucket=.

1. Sanity-check segments

nw review --week        # timeline + unclassified; --fix maps interactively

1. Keep history

Claude Code deletes old transcripts. Archive before they vanish:

nw snapshot             # through yesterday by default

1. Meetings (optional)

nw refresh-meetings --week

Date scopes

Same pattern on report, review, agenda, digest, refresh-meetings:

nw report                 # today
nw report --week          # this week
nw report 2026-06-01      # that day
nw report -w 2026-06-01   # week containing that date
nw report --last 7

Export / share

nw export --week --format csv -o week.csv

What “hours” mean

• Engagement wall-clock per topic (generation + your reading/typing fused).
• Concurrent sessions can make billed topic hours exceed real wall-clock; the report also shows de-duplicated wall-clock and a parallelism ratio.

Deep background: Time model & retention.

Next: Idea → ship when a time topic becomes work to govern.