Carrier / Handoff Desk
Unified State · Carrier update
Carrier Handoff Desk: keep the finding and its limits together
A new local working tool gives Carrier a practical role in project handoffs: carrying exact meanings alongside claims, evidence, conditions and unanswered questions.
The release follows three published retrieval and communication studies. R01 did not establish a reliable benefit from its tested graph blend. R02 did not establish an advantage for its selected typed method on either primary endpoint. R03 recorded a negative ranking result and equal success across four formats on a small, deliberately simple handoff task. Those outcomes remain public with their methods and limitations.
The desk is a workflow tool, not another performance claim. It opens with a source-backed draft about R03. That example keeps “768 scored fields matched the keys” beside the qualification that the test demonstrated no Carrier-specific advantage.
Users can edit records as results, limitations, proposals, unknowns or claimed decisions; attach definitions from a frozen catalog of 6,257 concepts; and retain source excerpts, scope and conditions. A JSON export preserves project data and saved checkpoints. A readable text export includes selected definitions and carried sources for an AI that cannot browse.
Returned JSON can be compared without replacing the current draft. The comparison exposes field changes, including removed conditions and changes from proposal to claimed decision. It does not judge whether a rewritten sentence means the same thing or whether an amendment is justified.
The application makes no background request to update its dictionary or send draft contents. Work stays in the current tab until downloaded; closing without exporting loses edits. Importing a project is a separate action that replaces the draft.
Exact source-excerpt checks, definition matching and required fields help make a record inspectable. They cannot authenticate approval, establish truth or guarantee that a source supports a statement. The JSON and text formats are experimental and are separate from USL1/CVP2 transport.
The immediate purpose is useful and testable in ordinary work: make it easier to see what the next reader has been asked to carry forward.