fungal nematode endoparasitism

Refine the infection-strategy hierarchy without conflating infection, trapping and feeding.

CURATION TODO OPEN fungal-nematode-endoparasitism-scope-and-hierarchy · raised by codex · 2026-10-14

Not yet attached to a section of this record — a curator sets attaches_to (e.g. causal_graphs#some_edge) so the gap shows beside the mechanism it concerns.

The fungal bearer has the established spore-infection-strategy phenotype, not merely an anatomical location inside a nematode. The host-contacting or ingested spore is the infectious unit; spore germination into an external hyphal trap is not this route. Adhesion or ingestion alone, killing alone, internal occupancy without the specified route and sequence annotation are insufficient. Vermiform stages distinguish the selected strategy from eggshell penetration in fungal nematode egg parasitism traitmech:000726. Fungal nematophagy traitmech:000719 requires feeding and includes dead prey; fungal nematode trap formation traitmech:000718 concerns hyphal differentiation. Neither is asserted as a parent. Local parasitism traitmech:000043 inherits persistent symbiosis, not required here. Animal pathogen METPO:1004002 is active below pathogenic to host METPO:1004000 and phenotype METPO:1000059. Current upstream clarifies its pinned organism-like wording as a phenotype; the local parent remains unchanged. No organism-level disjointness, exclusive host stage, universal host range or obligacy is asserted. Bare endoparasitism does not specify the fungal actor, host or infection route and is not an exact synonym.

Review the proposed infection class without reviving the obsolete parasitism identifier.

CURATION TODO OPEN fungal-nematode-endoparasitism-metpo-assessment · raised by codex · 2026-10-14

Not yet attached to a section of this record — a curator sets attaches_to (e.g. causal_graphs#some_edge) so the gap shows beside the mechanism it concerns.

No exact active counterpart was identified in inspected pinned/current releases, editor and six template owners. Historical METPO:1000227 obsolete parasitism is broader, deprecated, under ObsoleteClass with OMO:0001000 reason and no replacement or consider annotation in those releases. METPO issue 521 disputes mechanically assigned reasons; the code neither invalidates the biology nor authorizes reuse. The historical ID is not revived or placed in xrefs. The ontology pin remains unchanged; v603 proposes this narrower infection phenotype with PROPOSED status and no equivalent external xref. Existing bacterial endoparasitic predation is not this fungal spore-infection strategy.

Resolve assay endpoints and strain provenance before adding rates, canonical taxa or causal proteins.

KNOWLEDGE GAP OPEN fungal-nematode-endoparasitism-evidence-limits · raised by codex · 2026-10-14

Not yet attached to a section of this record — a curator sets attaches_to (e.g. causal_graphs#some_edge) so the gap shows beside the mechanism it concerns.

Sun's Methods 2.6 counts attached spores or colonization; reported parasitism percentages are not curated as internal infection rates. Its imaged HR-eGFP1 is engineered, and morphological similarity to the wild type does not establish unchanged virulence. Its intestinal-route suggestion remains tentative; the distinct 1997 primary abstract supports ingestion in Harposporium cycloides. Lebrigand's S1 Text reports long laboratory passage and related isolate provenance, so these are not independent natural-strain exemplars. Predicted genes, expression and disputed assembly or mating-type interpretations are not required causal effectors. No canonical taxa, proteins or causal graph are asserted without further authority and strain-provenance work. Microscopy does not measure nutrient flux; no quantitative threshold, field efficacy or safety is inferred. The verification sidecar retains actual source locators, hashes and native verdicts; direct matching does not upgrade NOT_IN_ABSTRACT or UNRESOLVED. Full Glockling Methods and all raw experimental data were not accessed, and bounded notice checks are not comprehensive correction/retraction clearance.