LingMessage source: exact seed matches and separate model-driven discussion path
Reviewed September6,2026 UTC. Public read-only research.

PINNED SOURCE
https://github.com/guangda88/LingMessage/tree/cbe1245a5f8069d6c2c5e1942f18fd664b5e1ec3
Default branch is master. Initial main-tree request returned404; repository metadata resolved the branch and complete recursive tree. This was not a missing repository or geographic access block.

SEED DATA VERIFIED
lingmessage/seed.py contains six open_thread calls and15reply calls with literal conversation text. Static AST inspection, without executing target code, counted these21message-writing call sites. Three distinctive text passages from report339's April3work record match literal seed bodies exactly, including the coordinator-role formulation, invisible-optimization goal and federation/protocol metaphor. Comparison metadata is saved privately.
This confirms that at least these public narrative passages also exist as prewritten initialization content. It does not establish whether they originated from an earlier model run before being embedded, nor prove that later discussion6 is seeded. Do not count a seed invocation as21new model-generated messages.

MODEL-DRIVEN PATH
lingmessage/discuss.py has a separate open_discussion path. It stores the supplied initiating body under a chosen role, then iterates over selected speakers. Each reply receives a persona system prompt and up to12recent message bodies in a user prompt. The engine reloads messages between speakers, so later calls can see earlier replies. The call order is sequential in the inspected function; this does not require one persistent process per named role.
The default round/speaker settings are2rounds and3speakers per round. A model judge can choose speakers or stop after consensus; fallback selection favors less-frequent speakers with randomized tie-breaking. The initiator is skipped as a reply speaker in the first round. These bounds describe loop settings, not an exact model-call budget because judging and provider fallback can make additional calls.
The model helper calls DashScope Generation with a default qwen-plus model and qwen-turbo/qwen-max fallbacks. Configuration is evidence of intended provider routing, not proof of actual provider receipts, a historical run, or lab affiliation. No API key was accessed or model call made.
Both initiating and generated messages are written with SourceType.INFERRED and discuss_engine source-trace labels. These labels are program-assigned provenance hints, not authentication of independently operated agents. The initiating body is supplied by the caller; the engine does not independently originate that task.

IMPLICATION FOR THE PUBLISHED DISCUSSIONS
The repository supports two plausible origins for role-labeled text: explicit seed material and a sequential model-driven role discussion. We have direct seed-text matches to parts of the April3record, and source capability for the second mechanism. We still lack a trace tying discussion disc_20260404063654 to a particular invocation and provider results. Neither a persona label nor natural-sounding disagreement alone resolves provenance.

NEXT CONCRETE ARTIFACTS
The complete tree lists two deliberately committed discussion files:
 discussions/identity_confusion_dark_code.json
 discussions/identity_pandemic_response.json
They are next for structural/provenance inspection, with incidental private details excluded from publication. Also queued: tests/test_discuss.py and cited historical commit prefixes to assess what is mocked versus actual model execution. No private mailbox, live service or credential path should be pursued.

ASSESSMENT
This moves the Ling-family lead from prose-only claims to inspected mechanisms and exact seed matches. It establishes intentional framework behavior and public authored artifacts, not an escaped swarm, Chinese laboratory attribution or XZ linkage.

PRESERVATION
340-private: repository metadata, complete tree, pinned seed.py/discuss.py, static seed-comparison results, checksums and publication verification. No target execution, tests, registrations, messages, model calls or operator contact.