Pathfinder · Version 0.3 Direction

Helping good ideas move from evidence to adoption.

Pathfinder is a methodology for managing adoption pathways under uncertainty. It helps teams make the next responsible commitment more visible.

The full v0.3 Working Paper will include the actor model, uncertainty taxonomy, adoption states, evidence quality levels, metrics, and falsifiability tests.

Working definition

Pathfinder is a methodology. The TCUS Superstack is one implementation environment.

Pathfinder helps teams structure evidence, identify decision actors, classify readiness blockers, document choices, and convert uncertainty into useful work.

The Superstack supports this method with software, data workflows, governance tools, and volunteer coordination systems. But Pathfinder itself is not just software. It is a disciplined way to observe and improve the transitions between evidence, trust, commitment, implementation, and learning.

The problem

Promising ideas 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 help, but cannot find the right work.

Pathfinder focuses on this missing middle: the handoff between evidence and the next actor who must decide.

The core thesis

The key unit is not the first pilot. It 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 asks one central question:

Who must say yes next, and what would make that yes responsible?

Actor

Who controls the next meaningful decision?

Uncertainty

What risk or unknown is blocking commitment?

Evidence

What would make the next step responsible?

Second decision

Adoption begins when a new actor commits.

A second decision happens when a new actor, not merely the original inventor, donor, researcher, or sponsor, makes a meaningful follow-on commitment.

  • a second funder supports continuation
  • a contractor agrees to build again
  • a local engineer signs off
  • a school hosts a follow-on implementation
  • a procurement office accepts the approach
  • a standards body reviews the method

What Pathfinder produces

Structured artifacts that make adoption pathways easier to see.

Pathfinder is not a prediction engine. It produces artifacts that help teams observe adoption chains, identify blockers, and convert uncertainty into useful work.

01

Evidence Packs

What is known, how we know it, what remains uncertain, and which decision the evidence supports.

02

Adoption Pathway Maps

Who must say yes next, what gates exist, what evidence is needed, and where the pathway may fail.

03

Readiness Lanes

A way to identify whether progress is blocked by technology, implementation, institutions, or mobilization.

04

Decision Ledgers

Records of why choices were made, what evidence was reviewed, what trade-offs were accepted, and what uncertainty remained.

05

Work Graphs

Maps of the work required to move the pathway forward, including roles, tasks, dependencies, contributors, and review points.

Together, these artifacts work like trail markers. They do not walk the path for anyone. They make the next step visible.

Readiness and failure

Pathfinder is not designed to force adoption.

It is designed to make adoption pathways visible enough that teams can continue, revise, pause, bound, or stop work responsibly.

Technology readiness

Does it work safely and reliably?

Implementation readiness

Can it be delivered in real conditions?

Institutional readiness

Can it be approved, funded, procured, standardized, or governed?

Mobilization readiness

Can the right people execute the next step?

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.

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.

01

Map the pathway

Identify the next actor who must decide: an engineer, contractor, ministry, school, donor, procurement office, or local implementation partner.

02

Classify the blocker

Determine whether the pathway is blocked by technical, implementation, institutional, financial, maintenance, political, or mobilization uncertainty.

03

Create the evidence packet

Structure the evidence for that actor: calculations for an engineer, lifecycle costs for a donor, training requirements for a contractor, or standards compatibility for a public agency.

04

Record the decision

If the actor continues, revises, pauses, rejects, or replicates the method, record why. The outcome updates the evidence base instead of disappearing into memory.

05

Convert learning into work

If the pathway remains viable, create a Work Graph: expert review, field documentation, cost comparison, training materials, partner outreach, or implementation tasks.

Reference implementation

The TCUS Superstack helps create, maintain, and connect the artifacts.

The Superstack is not the point by itself. The point is the learning loop:

Evidence Pathway Blocker Decision Work Outcome Updated Evidence

Quasar

Evidence

Structures evidence, datasets, provenance, and source history.

Supports: Evidence Packs

Sentinel

Analysis

Surfaces gaps, contradictions, uncertainty, and possible next questions.

Supports: Readiness analysis and option review

Lodestar

Governance

Supports ethical review, decision records, consent, conflicts checks, and accountability.

Supports: Decision Ledgers

Libelle

People

Connects people to meaningful work through skills, availability, roles, onboarding, and contribution tracking.

Supports: Work Graphs

What changed since v0.1

Pathfinder has become more grounded.

Pathfinder began as a broad alignment architecture for a livable future. Since then, TCUS has learned from real work:

  • building Libelle to coordinate volunteer talent
  • supporting education infrastructure funding in Ethiopia
  • researching how construction innovations move from demonstration to adoption
  • studying why promising interventions stall after pilots

That work sharpened the problem. The missing layer is not only data, funding, or awareness. The missing layer is the structured handoff between evidence and the next actor who must decide.

Current status

Pathfinder is in active development.

Libelle MVP

Volunteer intake, parsing, review, matching, and project coordination workflows.

Artifact templates

Evidence Packs, Adoption Pathway Maps, Decision Ledgers, and Work Graphs.

Research cases

Construction innovation adoption, education infrastructure funding, and implementation pathways.

v0.3 Working Paper

A deeper paper is being developed with actor models, uncertainty taxonomy, states, metrics, and falsifiability tests.

Coming next

Pathfinder v0.3 Working Paper

The working paper will provide the deeper model behind this page, including the actor model, uncertainty categories, adoption states, evidence quality levels, and measurement approach.

Invitation

Bring a problem that deserves more than another report.

Bring a stalled pilot. Bring a research finding. Bring a dataset. Bring a volunteer team. Bring a funding question. Bring a promising idea that needs to survive its next decision.

Pathfinder exists to help good work move from evidence to trust, from trust to commitment, from commitment to implementation, and from implementation to learning.