Why identity resolution needs a visible contract
A useful record is more than a value. Every result should explain freshness, confidence, provenance, and cost.
Field Notes / FetchSet
Signals worth
following.
Practical notes on identity resolution, contact-data quality, agent infrastructure, and building a clearer contract for every lookup.
issues 001–006updated monthlyno growth-hack theatre
Featured
One useful idea, fully resolved.
Latest notes
For builders who need data to act.
005 / Data quality <30
Freshness is a field, not a promise
Why validation dates should travel with the email instead of hiding behind a quality badge.
004 / Agents MCP
Designing resolution tools for agents
Small, composable calls beat giant enrichment workflows when an agent must choose its next step.
003 / Economics 0
Why an empty result should cost zero
Charge-on-success is not merely pricing. It changes how safely automated workflows can explore.
002 / Trust P
Provenance belongs in the record
How source class, acquisition date, and suppression checks turn contact data into accountable infrastructure.
001 / Infrastructure →
The shortest reliable path to a person
A look at the five decisions behind one resolution: normalize, cache, waterfall, verify, and return.
000 / Company F
Why we’re building FetchSet
Contact data should behave like a well-designed primitive: callable, inspectable, and candid about cost.
Stay in the loop
One useful signal in your inbox.
A concise monthly note on data quality, identity infrastructure, and building tools for agents. No growth-hack theatre.