Skip to main content
A note is where everything in Driftless starts: a private draft only you can see. From there it can go two ways. It can travel up the trust axis to become team Knowledge, or sideways to a specific teammate’s inbox. The two are independent, and neither one stops anyone from coding.

​
Jotting a note

The fastest way to capture something is a one-liner from the CLI. No anchors, no ceremony:
A note is a topic in its draft state: private to you, excluded from search, and auto-archived after ~14 days if untouched (recoverable). Think here, then decide where it goes.

​
Sideways: sharing with a teammate

Share a note directly with one or more workspace members. It lands in their inbox (“shared with me”) without becoming team-wide Knowledge. This is the right move for “you specifically should see this.” Recipients must be members of the workspace. Share with a non-member and it’s rejected. The dashboard’s Inbox renders this feed, and sharing and reading are both operable over REST for agents.

​
Up: merging into Knowledge

When a note is durable enough for the whole team, it climbs the trust axis: Note → Up for review → Knowledge. Merging is an owner/admin act. An owner or admin merges it, or explicitly asks an agent to run the merge on their behalf. What comes out is the team’s source of truth, the thing agents pull before they edit. See Governance for the full lifecycle and the merge commands. Sharing with a teammate (above) is internal and member-gated. To hand a topic to someone outside the workspace, mint a public read-only link instead: