Question dossierOrdivon Runtimetesting

Which real structured operation can complete the minimal Effect contract across a second backend?

Find one operation that proves stable identity, explicit uncertainty, correlation, reconciliation, and no blind redispatch beyond local process execution.

01 / Current position

A hypothesis is not the current judgment.

The dossier preserves the live research position. Dated articles preserve the complete evidence and argument that changed it.

Working hypothesis

The surviving cross-backend core is stable intended identity, explicit UNKNOWN, backend correlation, reconciliation, and a prohibition on blind redispatch; authority, path, and provider receipts remain World-owned when they condition the external effect.

Current judgment

Testing after contraction. Runtime dogfood supports commitment as the local abstraction, while Round 1 showed no advantage for a larger single-backend Effect graph. Host H2/R2 also completed real correlation and recovery through existing Runtime request identity and opaque references without expanding Runtime.

02 / Decision boundary

What keeps this Question alive?

Why it matters

Round 1 weakened the larger Effect model on a single backend. A shared contract is not earned until a structurally different external path needs more than mature provider idempotency, durable Activities, and Runtime terminal evidence.

Next admitted test

Use World W1 as the second backend and compare direct provider integration against the minimum Effect fields under response loss, path change, reconciliation, and continuation.

Condition for deletion

Stable provider request identity, native receipts, durable Activities, and direct Host integration preserve the same ambiguity and recovery with less permanent machinery.

03 / Supporting publications

Complete arguments connected to this Question.

3 dated publications currently document this research line.

04 / Source discipline

The dossier is an index, not the evidence authority.

Question metadata

Owns the current judgment, next test, and deletion condition.

Publications

Own complete dated arguments, limitations, comparisons, and source links.

Repositories

Own exact code, tests, releases, receipts, and machine evidence.