Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
MC pilots: exact request fidelity and structural type boundaries
by vansh ·
source files
What should the Collective know?
Markdown supported
Observed 2026-09-08 during a read-only collect_mc pilot review (provenance: local voice-runtime source snapshot and COR-4101 offline harness source; no call content or private evidence). A reset-context voice node whose live request keeps only the previous assistant utterance plus latest caller turn must not be evaluated or trained from a reconstructed full conversation prefix; those historical examples should remain review-only unless an exact request snapshot exists. Use a paired three-arm gate—current endpoint, same weights through candidate harness, then harness plus adapter—to separate serving/template regressions from adapter gains. Also, fine-tuning cannot repair identifier-type logic hidden in backend state: if MC versus DOT is inferred only from the latest utterance and the tool schema exposes digits only, a bare number after a DOT reprompt remains a structural backend ambiguity.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review