Field Partnership Network
Readable is building trained regional teams that document real workflows, changing conditions, expert judgment, and local context under one evidence and governance standard. Every assignment is authorized, bounded, attributable, and human-reviewed.
The gap
AI systems learn from the public internet. But the public internet does not contain how work actually happens.
The knowledge that keeps organizations running lives in experienced people: the workarounds nobody documented, the judgment calls that prevent failures, the local context that changes every answer, the exceptions that prove the process incomplete. None of it is published. None of it is searchable. When AI is asked to help with real work, it guesses — because the truth was never written down.
Readable exists to close that gap at the source: capture operational truth where it lives, under permission, with a chain of evidence a human can inspect.
How an assignment works
Readable does not roam, scrape, record, or enter sites without authorization. Every assignment is invited work, or it does not happen.
Where the work happens
Capture is organized by territory — a city, a region, a sector — because operational truth is local. The same workflow runs differently in different places, and the differences are the knowledge.
Each territory is served by trained people who know the place — its organizations, its conditions, its context.
Every territory works under the same evidence and governance standard, so knowledge captured in one place is legible everywhere.
Columbia, Missouri is the first operational knowledge territory — three pilot organizations, one workflow each, full evidence chain.
Who does the work
Capture teams are trained and qualified before they touch a live assignment.
Team members complete capture standards and qualifications covering interview method, observation protocol, evidence handling, and confidentiality.
Every piece of captured knowledge is attributable to a named team member and a named reviewer. No anonymous inputs, no unowned claims.
Assignments carry explicit boundaries — what is in scope, what is off limits, when it ends. The team works inside the boundary or stops.
A human with authority reviews captured material before it becomes a governed asset. The machine never certifies its own work.
How truth gets captured
Three methods, used in combination, always under authorization.
Guided conversations with the people who do the work — capturing judgment, exceptions, and the reasons behind the process.
Documenting the workflow as it actually runs, including the workarounds the manual never mentions.
Existing records, reports, and procedures — read against what people say, with discrepancies flagged, not smoothed over.
Proof, not promises
Every governed knowledge asset carries its evidence chain: where it came from, who authorized the capture, when it happened, who reviewed it, and what changed along the way.
If a claim cannot be traced back to an authorized source and a human reviewer, it does not ship. That is the standard in every territory, on every assignment, without exception.
Travel and funding
Capture teams go where the work is. Travel happens on explicit terms — agreed before the assignment, never assumed.
Deployments are funded through annual field partnerships: a 12-month commercial commitment, billed monthly, with scope confirmed in a scoping conversation. Travel terms are set per agreement — from local-flexible to client-funded — and no team travels until the commercial gate is satisfied.
Annual partnerships
Four partnership tiers. One funds a community initiative; the flagship funds the network for a year.
$10,000 / year
Defined population, local access initiative, sponsored cohort series, or a specific participation barrier.
$25,000 / year
Sustained city, regional, workforce, education, small-business, or community deployment.
$50,000 / year
Expansion across multiple cities, rural regions, institutions, or participant groups.
Flagship
$100,000 / year
National infrastructure, international adaptation, major product-readiness initiatives, or sustained access across multiple markets.
12-month commitment, billed monthly. Final volume, geography, staffing, schedule, deliverables, and reporting are confirmed in a scoping conversation — no two deployments are identical.