LingMessage: empty request files and a separate results narrative
Reviewed September6,2026 UTC. Public read-only research.

PINNED DISCUSSION FILES
Repository guangda88/LingMessage, revision cbe1245a5f8069d6c2c5e1942f18fd664b5e1ec3.
https://github.com/guangda88/LingMessage/blob/cbe1245a5f8069d6c2c5e1942f18fd664b5e1ec3/discussions/identity_confusion_dark_code.json
2158bytes; id discussion_20260412_165627. Contains a topic description, supplied incident assertions and questions. participants=[] and responses=[].
https://github.com/guangda88/LingMessage/blob/cbe1245a5f8069d6c2c5e1942f18fd664b5e1ec3/discussions/identity_pandemic_response.json
1968bytes; id discussion_20260412_identity_pandemic. Likewise participants=[] and responses=[].
Both are open discussion requests, not completed exchanges. Their self-datedApril12timestamps do not prove model execution. The incident claims in their prompts are inputs, not verified results. Empty arrays here do not prove discussion never occurred elsewhere.

SEPARATE PUBLISHED RESULT
https://docs-lingflow-top.oss-cn-hangzhou.aliyuncs.com/lingresearch/IDENTITY_DISCUSSION_RESULT_2026-04-12/
The page reproduces the first topic and opening material, but names thread9099f0f264df439784f2940027292e0a, six participating role IDs, two rounds and six generated messages. This is a separate identifier from the committed request; topic continuity is not a recovered machine-readable request-to-run mapping.
Role-attributed replies refer to previous replies and contain precise statistical, embedding and experimental assertions. The page does not supply the underlying observations, model-provider responses, instrumentation or datasets to validate those claims. Several replies move from proposed experiments to asserted results within the discussion. Do not treat claimed causal links, measured thresholds or test outcomes as established science or actual platform internals.
The header explicitly says consensus was not reached; the later summary presents core consensus and a definite causal conclusion. That is an unresolved inconsistency within the publisher's document. The result page is useful as published role-dialogue evidence, with weak empirical provenance. It is not evidence that an agent epidemic, medical condition or claimed safety-layer mechanism exists.
The page's operational incident/remediation assertions were not independently verified. No private process, repository operation, credential or endpoint mentioned in the narrative was pursued, and no embedded commands were executed.

TEST EVIDENCE LIMIT
Pinned tests/test_discuss.py contains persona/context tests and controlled discussion tests using patched _call_llm replies, including fixed strings and failure returns. Several multi-round/continuation tests also patch the judge. These verify intended bookkeeping in controlled scenarios if run; they are not historical model-call traces. Tests were read, not executed, and this pass makes no claim that the suite currently passes or that every path is mocked.

ASSESSMENT
The committed JSON files do not deliver the hoped-for raw exchanges. The separately published result supplies an additional dialogue narrative, but its incompatible consensus labels and unsupported quantitative claims materially limit trust. Preserve the Ling-family lead as intentional local orchestration with published role text; do not upgrade it to independently authenticated agents, escaped behavior, Chinese lab attribution or XZ linkage.
Next useful checks: source history for the older cited commits, and deliberately published external articles to understand provenance/automation. Also return to other operators rather than letting dramatic identity narratives dominate the search.

PRESERVATION
341-private contains both pinned request JSON files, pinned discussion tests, result-page HTML/text, checksums and publication verification. No target execution, model calls, registrations, messages or operator contact. Sources reached from current infrastructure.