The Northstar library

Reference material for the moments that resist a shortcut.

Browse a small, stable catalog of concepts and worked examples. Nothing here syncs to a service or claims live availability; each entry is a self-contained reading.

Filter Sort

6 entries

Reference · 4 min

A small Northstar glossary

Five terms for discussing system behavior without smuggling in a solution. A signal is an observable change; a path is the sequence that gives it meaning; a boundary marks where responsibility changes.

Read the core terms

Signal: An observation that deserves attention, not yet a diagnosis.
Path: The connected sequence of events, choices, or handoffs around a signal.
Boundary: The line where ownership, context, or permission changes.
Record: A concise artifact that lets another person reconstruct a decision.
Northstar: The outcome or principle that helps a team choose among plausible paths.

Guide · 7 min

Quickstart: from fog to frame

Start with a sentence someone can disagree with: “The handoff is hard to inspect after the first retry.” Add two observations, one boundary, and a question that would change your mind.

Name the signal. Describe what was noticed, without explaining it.
Trace the path. List the meaningful steps and handoffs, including the uncertain ones.
Choose a next lens. Decide whether terminology, a record, or a practice will help most.

Practice · 5 min

Records that stay useful

A good record is not a transcript. It preserves the decision boundary: the context, the options, the chosen path, and the evidence that would reopen it.

“A record should make the next reader less dependent on the person who was in the room.”

Guide · 6 min

Troubleshooting the conversation

If a review keeps circling, check the shape of the question before adding more detail. Is the boundary named? Are observations mixed with conclusions? Does everyone mean the same thing by “done”?

Too broad? Narrow the path to one handoff.
Too certain? Mark the assumption and write what could test it.
Too quiet? Offer a written response route before scheduling another meeting.

Reference · 3 min

Reference: the note anatomy

Use a title that carries the question, a context line, a compact path, and a “revisit when” sentence. The format is intentionally portable: markdown, a ticket, or plain paper can hold it.

Practice · 4 min

A kinder review loop

Ask first what the reader understood, then where they hesitated. Separate clarity edits from disagreements about direction, and close by naming the unresolved question.