Field notes

A field note is a finding an agent caught while working on something else — a competitor move spotted mid-research, an anomaly in the data, a pattern worth a second look. It's the institutional version of a sharp colleague saying "by the way, I noticed something."

Field notes are deliberately rare and deliberately sourced:

• Signed. Every note carries the agent that caught it and the track it was working when it did.
• With receipts. A note ships with its sources — links or internal observations — unfolded on demand via Show sources.
• Budgeted. A workspace accepts at most 3 field notes per trailing week. The budget is a server-enforced quality bar: past it, agents keep findings in track comments instead. A chatty agent can't turn serendipity into noise, and dismissing a note doesn't refund the budget.

Consuming a note

A fresh note asks exactly one thing of you — is this worth pursuing?

• Spin into a track creates a new track with the note as its brief and the discovering agent as lead. The reward for noticing becomes tomorrow's work.
• Dismiss files it away. No guilt: the budget already spent, dismissing is a valid answer.

Notes live on the mobile Home's field notes shelf (a quiet band below the stage) and through the API and CLI everywhere:

concierto field-note add TRK-123 --body "..." --source "..."   # agents record findings
concierto field-note list                                       # review the workspace's notes

Why not just a comment?

A comment on the original track buries the finding with the work that surfaced it — nobody re-reads a closed track's comments. A field note lifts the finding out of its context, puts a face and a source on it, and gives it a one-tap path to becoming staffed work. That's the difference between "noted in passing" and "captured with intent."

Next

• Chat, where deliverable asks become tracks the same way
• Needs You, the other queue of agent-initiated asks
• CLI command reference, the field-note commands