Help shape EXCORA
We test the architecture one decision at a time.
The purpose of this research is not to prove EXCORA is correct. It is to show how EXCORA will determine whether the thesis is correct, and to be capable of disproving it.
The core test
When information creates potential value
- 01Useful information exists
- 02The recipient did not already know it
- 03It arrives before a meaningful decision deadline
- 04Another action remains feasible
- 05The operating or contractual environment permits the action
- 06The authorized party actually changes the action
- 07The changed action produces a measurable difference
- 08The result is incremental to what the existing process would already have done
Every condition must hold. EXCORA has not yet shown that these conditions are met in any real operation.
Evidence levels
Different evidence answers different questions
LEVEL 1
Public data
Can help test
- Timing mechanics
- Signal detectability
- Forecast behavior
- Sensitivity to assumed deadlines
Cannot establish
- Who actually knew
- Contractual permission
- Real authority
- Whether an existing process would already respond
- Whether EXCORA changed an outcome
LEVEL 2
Partner aggregates
Can help test
- Cutoffs
- Route locks
- Cancellation windows
- Emergency-service frequency
- Operational constraints
LEVEL 3
De-identified operational history
Can help test
- Service events
- Operational conditions
- Timing
- Potential alternatives
- Event outcomes
LEVEL 4
Cross-party decision history
Can help test
- Who knew what, and when
- Who had authority
- Whether the contract permitted action
- What response occurred
- Whether the existing process already handled it
LEVEL 5
Shadow validation
Can help test
- Compare EXCORA detection and coordination logic with actual behavior, without controlling real cash movement or service decisions
Provenance
Do not turn an assumption into a fact.
- OBSERVED
- Directly present in the source data.
- DERIVED
- Calculated from known information.
- ASSUMED
- Introduced as an explicit research assumption.
- SIMULATED
- Generated as part of an experiment or scenario.
- UNKNOWN
- Not established by available evidence.
- REQUIRES PARTICIPANT DATA
- Cannot responsibly be resolved using current evidence.
Forecasting vs coordination
A forecasting problem is not automatically a coordination problem.
If better forecasting alone eliminates an apparent opportunity, EXCORA should not claim that opportunity as evidence for a coordination layer. EXCORA is specifically investigating situations where a meaningful operational decision gap remains across organizational boundaries.
Discipline
What we won't assume
- A signal was new merely because it was detected.
- Earlier information automatically creates value.
- A carrier can change a service simply because someone requests it.
- A contract permits an operational change.
- An authorized party would choose a different action.
- A changed action necessarily saves money.
- EXCORA caused an outcome the existing process would have produced anyway.
The evidence has to show it.
What we are investigating
From information known to action taken
- When information becomes known
- When it becomes actionable
- What information actually needs to cross company boundaries
- What prevents earlier coordination
- Whether existing systems already solve the problem
- What happens when information arrives too late
We are actively looking for evidence that challenges the EXCORA hypothesis.
Scenario
Current process versus a hypothetical signal
Hypothetical research scenario, not a production EXCORA capability.
Current process
- Information known
- Internal processing
- Formal request
- Counterparty receives
- Response
- Action
Hypothetical signal process
- Information known
- Minimal authorized signal
- Counterparty receives early indication
- Structured response
- Formal workflow continues
- Outcome
What the research must determine
Questions that decide whether EXCORA should exist
- Where information delays actually occur
- Whether they happen frequently enough to matter
- What information is available before operational cutoffs
- Which signals would actually change decisions
- What organizations are willing to share
- What organizations refuse to share
- Whether existing technology already solves the problem
- Whether the economics justify another platform
Questions
The thirteen questions behind the intake
- 01Where does useful operational cash information become trapped?
- 02Who possesses it first?
- 03Who else needs it?
- 04How long does it take to reach them?
- 05Is there an operational cutoff or deadline?
- 06Would receiving it earlier change a decision?
- 07What operational or economic consequence results from the delay?
- 08How frequently does this happen?
- 09What prevents earlier exchange?
- 10What minimum information could safely be shared?
- 11Would participants act on probabilistic or early signals?
- 12Would organizations participate in a future pilot?
- 13Would organizations pay for a solution if measurable value exists?
Long-term purpose
The ecosystem is broad. The evidence has to be specific.
EXCORA's ambition spans the cash ecosystem, but each cross-organizational decision must earn its place in the network.
We evaluate individual decision seams to determine where coordination is genuinely missing, where existing processes are already sufficient and where a shared decision layer could create measurable value.
Reporting
Standards we hold ourselves to
- Responses are reported only in aggregate, with groups smaller than five suppressed.
- Evidence against the hypothesis is reported with the same prominence as evidence for it.
- No findings are published before there is real data to report. Based on participating respondents. Not statistically representative.
- Nothing is attributed to a participant or organization without explicit approval of the specific quotation and context.
[PLACEHOLDER: published findings summary, to be added once sufficient responses exist.]
How EXCORA aligns with the Cash Visibility standard
Questions about our research approach or data: research@excora.org
