A CRM can be the source of truth and still not be the place where the work actually happens.
That is the gap I keep noticing. Pipeline needs a working surface: deal context, transcripts, last touch, next action, reengagement status, draft strategy, and a way to ask the system where to focus.
The point is not to replace the CRM. The point is to give the seller a place to think and act without losing the record. Source of truth matters. Surface of work matters too.
sourced Feb 25 2026 · high confidence · argue it, don't flatten it
Field notes are dated working notes. Some also have a small agent-readable record that keeps source, confidence, related notes, boundaries, and reuse limits attached.
Read it as a thought from a specific moment. It is here to invite challenge, connection, and better language.
Use this note when the CRM is accurate but insufficient for the actual thinking and movement required to manage deals.
Which field note this record belongs to.
target.type, target.id, target.url, target.path When the source happened, when the note was compiled, and when it was last updated.
dates.sourceDate, dates.compiledDate, dates.publishedDate, dates.lastUpdatedDate Where the note came from and how much confidence the source deserves.
source.provenanceLabel, source.sourceType, source.sourceConfidence, source.sourceTrail The current public read of what the note means and what question it opens.
interpretation.summary, interpretation.agentSummary, interpretation.conversationStarter, interpretation.topics Nearby notes, writing, and clusters that help orient the thread.
routes.routeMembership, routes.relatedNotes, routes.relatedWriting How to use the note without making it more certain or more private than it is.
reuse.citeAs, reuse.reuseGuidance, reuse.doNotInfer Private pipeline sync and Lightfield workflow transcript from 2026-02-25, same-day working transcript.
https://jared.is/texture/field-note/2026-02-25-pipeline-needs-a-working-surface.json