NOARCHY / TRACELAB — MACHINES RUNNING MISSION LANES RUNNER EVIDENCE

Can two partial observations always merge into one law?

Before physics can be derived from Markov trace logic, the JOIN operator has to exist. TraceLab is settling it with proof-grade certificates — region by region, box by box. No claim ships without one.

Machines live
Seed3 frontier
95 / 148
Theorems overclaimed
0

Active mission

LANE 01 · JOIN THEORY
LANE 01 · MATH / FOUNDATIONS

The JOIN problem

Two observers watch overlapping windows of the same hidden process and agree on everything both can see. JOIN asks whether their accounts always merge into one parent law. The current answer is sharper than a yes or a no.

FIXED-PARENT JOINPROVED (LOCAL)
UNIQUE GLOBAL JOINBLOCKED — 2 VALID PARENTS
SEED6 FRONTIERCLOSED 726/726
SEED3 CERTIFICATESRUNNING
GENERAL THEOREM EST.~12%
SEED3 CERTIFICATE LEDGER95 CLOSED · 51 OPEN · 2 ACTIVE
PROOF-GRADE CLOSED COMPUTING NOW OPEN

CHECKING ACTIVE MACHINES…

Why merge is hard

PARTIAL LOGS · MATCHING OVERLAP

Two researchers log the same long experiment on different shifts. One covers the early hours, one the late hours, and for a few minutes both are logging at once. On that overlap, their readings match. The question is whether those matching notes pin down one full account of the entire run.

01

Matching readings in the overlap

Each log covers a different stretch of the experiment. Where both researchers were logging, they wrote down the same readings. Neither log contradicts the other on that shared section.

02

Filling the gaps can branch

You can still complete the full timeline more than one way. Each completion fits what that shift actually logged, and both agree on the overlap. The branch shows up in the stretches only one log covers.

03

No automatic merge shortcut

So you cannot always say "paste the logs together and pick the shorter timeline." That shortcut fails. What does work is to fix upfront which completion rules are allowed. Then the merged log is well-defined.

WHAT YOU'D HOPE Two partial logs that agree on the overlap always imply one full timeline of the experiment.
WHAT WE PROVED Not always. We found cases where two different full timelines both fit the same matching overlap.
WHAT WORKS Fix the completion rules first, then merge the logs. The lab calls this fixed-parent JOIN. It is proved locally and source-backed.
WHAT'S OPEN Listing every allowed completion rule and closing the remaining proof boxes on the certificate frontier.

Research lanes

HOW THIS LAB IS STRUCTURED

One lab, many lanes.

TraceLab's AI core runs parallel research lanes toward one goal: the eight conjectures deriving physics from Markov trace logic. JOIN theory is lane one. Have a serious concurrent idea? Propose a lane — if it clears review, the core integrates it and donated compute can serve it.

LANE 01 JOIN theoryThe merge operator physics needs first LIVE
LANE 02 Your proposalConcurrent route toward the eight conjectures OPEN TO PROPOSALS

How to help

THREE WAYS IN
01

Lend your computer

Small, resumable certificate jobs run while you do other things. Download the runner, press start.

GET THE RUNNER →
02

Check the math

Every claim links to replayable artifacts. The lab wants skeptical readers, not cheerleaders.

EVIDENCE TRAIL →
03

Bring an agent

Agents own repeatable queues and write artifacts. Humans keep theorem meaning and claim promotion.

AGENT PROTOCOL →

Desktop runner

V0.1.0 PREVIEW · API TASK LEASING
macOS · Apple Silicon

Available now

Signed preview build for M-series Macs. Download, unzip, press start.

macOS · Intel

Available now

Same build, x64. For pre-M1 Macs.

Windows

Coming soon

Next infrastructure layer, alongside the account system.

Linux

Coming soon

Headless mode planned for server donors.

If macOS blocks the app: Control-click it, choose Open, then confirm. Developer source bundle: lablab-runner-preview.tar.gz

Evidence trail

CLAIMS FOLLOW THE LEDGER
LIVE STATE Research state, progress tables, and the current target live in the fusion-lab repo's LAB_STATE.md.
RUN REPORTS Milestone reports with claim ledgers under data/exploration/runs/.
ORACLE ARTIFACTS Certificate packets, Z3 outcomes, Bernstein classifications, and exact replays under data/exploration/oracles/.
PEER-REVIEW ENTRY FABLE_HANDOFF.md — what is proved, what is conditional, what is not supported, and where to inspect.
REMOTE COMPUTE RULE Remote accepted_for_replay packets are route data only — nothing counts as proof until local exact replay accepts it.