Pathfinder · Version 0.3 Working Paper
An Open Methodology for Managing Adoption Pathways Under Uncertainty
Pathfinder helps teams structure evidence, identify decision actors, classify readiness blockers, document choices, and convert uncertainty into useful work.
Executive summary
The missing layer is the structured handoff between evidence and the next actor who must decide.
Promising interventions often fail in the middle. A pilot works, but does not spread. A research finding is credible, but does not reach the institution that can act on it. A funder wants impact, but cannot tell which opportunity is ready.
Pathfinder v0.3 reframes TCUS’ earlier alignment architecture into a narrower, more testable methodology for observing and improving adoption pathways under uncertainty.
The central question: Who must say yes next, and what would make that yes responsible?
Contents
Abstract
Pathfinder is an open methodology for managing adoption pathways under uncertainty.
Promising interventions often fail in the middle. A pilot works, but does not spread. A research finding is credible, but does not reach the institution that can act on it. A funder wants impact, but cannot tell which opportunity is ready. A volunteer wants to contribute, but cannot find the right work. A community need is visible, but the pathway from evidence to implementation is unclear.
Pathfinder helps teams structure evidence, identify decision actors, classify readiness blockers, document choices, and convert uncertainty into useful work.
The central unit in Pathfinder is the next responsible commitment. A project does not become an adoption pathway merely because it is promising. It becomes an adoption pathway when evidence from one stage helps another actor make a meaningful next decision.
Pathfinder is not a prediction engine, a top-down coordination system, or a claim that evidence alone causes adoption. It is a structured artifact system for making adoption chains more observable.
1. Why Pathfinder changed since v0.1
From broad alignment architecture to adoption-pathway methodology.
The original Pathfinder v0.1 frame described an “alignment engine” for a livable future. It was motivated by a real concern: humanity has many solutions, but lacks the coordination infrastructure to move them toward shared long-term goals.
That frame remains morally important, but it was too broad as an operational model. It risked sounding like a planetary operating system, a general coordination theory, or a software stack in search of a method.
Since then, TCUS has learned from concrete work: building Libelle, supporting education infrastructure funding in Ethiopia, and researching how construction innovations move from demonstration to adoption.
The sharper mechanism is this: good ideas often fail because evidence does not travel in a form that reduces uncertainty for the next actor who controls the next decision.
2. The problem
The missing middle between evidence and action.
Many fields are rich with ideas, pilots, reports, prototypes, and local successes. Yet many promising interventions still fail to move forward.
A project may have enough evidence to interest its original sponsor, but not enough evidence for a second funder. A technology may work in a demonstration, but not be trusted by contractors. A research finding may be credible to specialists, but not actionable for public agencies.
Pathfinder exists because blockers are often collapsed into vague phrases: “not ready,” “needs more research,” “hard to scale,” “lacks buy-in,” “needs funding,” or “implementation problem.”
Those phrases may be true, but they are not specific enough to guide action.
3. Core thesis
The key unit is not the first pilot. It is the next responsible commitment.
A first pilot can prove that something is possible. But an adoption pathway begins to form only when another actor, not merely the original inventor, donor, researcher, or sponsor, makes a meaningful follow-on commitment.
This is the second decision concept.
A second decision may include a second funder supporting continuation, a contractor agreeing to build again, a local engineer signing off, a school hosting a follow-on implementation, a procurement office accepting the approach, or a standards body reviewing the method.
Who must say yes next, and what would make that yes responsible?
4. System boundary
What Pathfinder is and is not.
Pathfinder is
- a methodology for managing adoption pathways under uncertainty
- a structured way to identify actors, map decisions, and classify uncertainty
- an artifact system for evidence, pathways, readiness, decisions, and work
- a way to learn from continuation, revision, refusal, boundedness, and abandonment
Pathfinder is not
- a guarantee of adoption
- a general AI decision-maker
- a prediction engine
- a universal theory of institutional change
- a replacement for local judgment
- a claim that better evidence always wins
Pathfinder’s narrower claim is that when decision-relevant evidence is structured for the actor who controls the next transition, one important class of adoption failure becomes more visible and potentially more addressable.
5. Actor model
Adoption happens when specific actors make specific decisions.
Actors are the central unit of Pathfinder because adoption does not happen in the abstract. It happens when specific actors, with specific authority, incentives, constraints, and risks, make decisions.
If these cannot be named, the adoption pathway is not yet well-defined.
6. Uncertainty taxonomy
Different actors tolerate different types of uncertainty.
A contractor may care most about implementation uncertainty. An engineer may care most about technical and liability uncertainty. A donor may care about financial and reputational uncertainty. A community may care about agency, trust, and long-term effects.
Technical
Does the intervention work safely and reliably?
Implementation
Can the intervention be delivered in real conditions?
Institutional
Can it pass through formal or informal institutional gates?
Financial
Can it be paid for, sustained, and justified against alternatives?
Reputational / Political
What social or institutional risk does the actor face?
Maintenance / Durability
What happens after the first implementation?
Ethical / Community
Does it respect local agency, consent, equity, and long-term well-being?
An Evidence Pack should identify which uncertainty category is blocking which actor from which decision.
7. Adoption states
A pilot, a replication, an institutional commitment, and routine use are not the same outcome.
Concept
The idea is proposed but not yet tested.
Validated
The idea has some evidence of technical or practical viability.
Piloted
The idea has been tried in a bounded setting.
Second Decision
A new actor makes an independent follow-on commitment.
Replicated
The intervention is implemented again in a new site, by a new actor, or under meaningfully different conditions.
Institutionally Adopted
The intervention becomes part of a formal or semi-formal institutional pathway.
Standardized or Routinely Used
The intervention becomes repeatable without exceptional sponsorship.
Abandoned, Deprecated, or Bounded
The intervention does not continue, is intentionally discontinued, or remains useful only under narrow conditions.
8. Evidence quality levels
Pathfinder distinguishes between the existence of evidence and the strength of evidence.
Assertion
A claim is stated but not supported by traceable evidence.
Anecdotal or Single-Source
A claim is supported by one source, observation, interview, report, or direct account.
Documented Case
A claim is supported by records, reports, calculations, photos, notes, or partner confirmation from a specific case.
Multi-Source Corroborated
A claim is supported by multiple independent or semi-independent sources.
Comparative or Replication
A claim is supported across multiple cases, sites, implementations, or time periods.
Institutionalized or Routinely Verified
A claim is supported by routine use, formal standards, repeated procurement, curriculum inclusion, or durable practice.
9. Core artifacts
Pathfinder becomes useful through artifacts.
Evidence Packs
What is known, how it is known, what remains uncertain, and which decision the evidence supports.
What does the next actor need to know before deciding?
Adoption Pathway Maps
How a promising intervention would need to move through real-world actors and gates.
Who must say yes next, and what would make that yes responsible?
Readiness Lanes
Where progress is blocked: technology, implementation, institutions, or mobilization.
Where is the adoption pathway actually failing?
Decision Ledgers
Why a choice was made, what evidence was reviewed, and what uncertainty remained.
Why did we choose this path, and what did we know at the time?
Work Graphs
The work required to move the pathway forward, including tasks, roles, dependencies, and review points.
What work must be completed before the next responsible commitment can happen?
10. Artifact loop
The system is only useful if the loop closes.
Pathfinder artifacts should not exist as isolated documents. Evidence Packs identify what is known and uncertain. Adoption Pathway Maps identify who needs that evidence and what decision comes next. Readiness Lanes classify the blocker. Decision Ledgers record what choice was made and why. Work Graphs turn blockers and next steps into executable work. New outcomes update the evidence base.
11. Failure semantics
Pathfinder is not designed to force adoption.
A failed transfer can still produce valuable knowledge if the blocker is documented.
Continue
Evidence supports the next responsible commitment.
Revise
The pathway remains promising but needs redesign.
Pause
Uncertainty or capacity gaps are too large for continuation.
Bound
The idea works only under narrow conditions.
Stop
Evidence, risk, incentives, or institutional constraints make continuation unjustified.
12. The TCUS Superstack
The Superstack is the reference implementation environment for Pathfinder.
The Superstack is not the point by itself. The point is the artifact loop.
Quasar
Supports Evidence Packs through source ingestion, provenance, dataset structure, versioning, and evidence traceability.
Sentinel
Supports analysis of gaps, contradictions, uncertainty, and possible next questions.
Lodestar
Supports Decision Ledgers, consent, ethics, governance, conflicts checks, and accountability workflows.
Libelle
Supports Work Graphs and mobilization through contributor intake, matching, onboarding, and contribution tracking.
13. Example walkthrough
How Pathfinder analyzes a stalled construction innovation.
Imagine a low-cost building method has been demonstrated once, but has not been adopted by additional builders, funders, or institutions.
Map the pathway
Identify the next actor who must decide: engineer, contractor, ministry, school, donor, procurement office, or local implementation partner.
Classify the blocker
Determine whether the pathway is blocked by technical, implementation, institutional, financial, maintenance, political, or mobilization uncertainty.
Create the Evidence Pack
Structure the evidence for the relevant actor, such as calculations for an engineer or lifecycle costs for a donor.
Record the decision
If the actor continues, revises, pauses, rejects, or replicates the method, record why.
Convert learning into work
Create tasks such as expert review, field documentation, cost comparison, training materials, or partner outreach.
14. Measurement model
Pathfinder should be evaluated at the level of adoption-chain observability and decision-transition improvement.
Evidence metrics
Provenance, evidence quality level, uncertainty category, named next actor, evidence updates, contradictory findings.
Actor and pathway metrics
Named next actors, decision rights, risk exposure, incentives, constraints, readiness blockers, pathway updates.
Decision metrics
Recorded decisions, alternatives considered, uncertainty recorded, conflicts reviewed, decisions revised after new evidence.
Second-decision metrics
Observed second decisions, actor independence, evidence used, time from pilot to second decision, outcome type.
Mobilization metrics
Time from intake to placement, active contributors, active Work Graphs, blocker-linked tasks, retention, completion rates.
Learning metrics
Assumptions revised, abandoned pathways documented, failed predictions captured, artifacts reused by external actors.
15. Falsifiability
Pathfinder can fail.
Pathfinder should be revised if its artifacts do not improve real decision-making.
- Evidence Packs are created but not used by decision-makers.
- Adoption Pathway Maps fail to identify actual gatekeepers.
- Readiness Lanes do not predict where projects stall.
- Second decisions occur without reference to structured evidence.
- Decision Ledgers become performative documentation rather than accountability tools.
- Local partners experience Pathfinder artifacts as burdensome or extractive.
- The methodology becomes too abstract to guide real action.
The test is not whether Pathfinder explains everything. The test is whether it helps teams observe adoption chains, reduce avoidable uncertainty, and improve specific decision transitions.
16. Relationship to TCUS’ livable future mission
Pathfinder remains connected to TCUS’ broader mission, but v0.3 narrows the operational claim.
TCUS is concerned with long-term human flourishing, sustainability, equity, cooperation, and durable institutions. Pathfinder supports that mission by helping promising work move more responsibly from evidence to action.
In Pathfinder v0.3, “livable future” is a directional value frame, not a measured outcome claim. Specific projects should not claim to advance a livable future unless they define the measurable pathway by which they do so.
17. What Pathfinder can reasonably claim now
Disciplined observation before broad claims.
Pathfinder can reasonably claim to help teams:
- observe adoption chains
- identify decision actors
- classify uncertainty
- document evidence quality
- make readiness blockers visible
- convert blockers into work
- record decisions and trade-offs
- track second decisions
- learn from abandonment or bounded adoption
Pathfinder should not yet claim to:
- solve coordination failure generally
- predict adoption reliably
- guarantee scaling
- optimize institutional behavior
- align humanity
- replace local judgment
18. Current TCUS work relevant to Pathfinder
Pathfinder is being developed through active TCUS workstreams.
Libelle
The people and mobilization layer for intake, matching, onboarding, contribution tracking, and Work Graphs.
Education infrastructure funding
Clarifies the importance of targeted commitments that unlock larger pathways or enable another actor to proceed.
Construction innovation research
Sharpens the adoption side of Pathfinder by examining how innovations move from technical possibility to institutional use.
Superstack development
Supports the artifact loop: Evidence → Pathway → Blocker → Decision → Work → Outcome → Updated Evidence.
19. Roadmap
From working draft to reusable methodology.
Phase 1: v0.3 Working Draft
Publish framework page and working paper; define core artifacts, actor model, uncertainty taxonomy, states, and measurement concepts.
Phase 2: Artifact Templates
Release Evidence Pack, Adoption Pathway Map, Decision Ledger, Work Graph, readiness blocker, and second-decision templates.
Phase 3: Case Applications
Apply Pathfinder to Libelle, education infrastructure funding, construction innovation, and partner-supplied stalled pilots.
Phase 4: Tool Integration
Connect artifacts through Quasar, Sentinel, Lodestar, and Libelle.
Phase 5: Public Review
Move toward public RFCs, GitHub documentation, external use cases, and revision toward v0.4 and v1.0.
20. Invitation
Bring a problem that deserves more than another report.
Pathfinder exists to help good work move from evidence to trust, from trust to commitment, from commitment to implementation, and from implementation to learning.
The goal is not to force scale. The goal is to make the next responsible commitment possible.