Found selecting the eleventh #183 record. Worth filing before anyone batches the remaining ~31, because the discriminator I looked for does not exist.
The case
Avena_Rhizosphere_CrossKingdom_SIP_Community came top of the candidate ranking: 95k of cached full text, 100% member coverage, methods keywords throughout.
It is a stable-isotope-probing study of native rhizosphere soil. Avena fatua was grown under ¹³CO₂ and paired rhizosphere/non-rhizosphere soil was collected at 6 and 9 weeks; the microbial community was never grown in a vessel by anyone. Giving it a cultivation_setup would assert a cultivation that did not happen — the same shape as Soil_Corrinoid_B12_Reservoir_Community, which was once scored 5/5 on growth conditions belonging to an E. coli reporter strain in a community that is metagenomic.
The plant had a growth setup. The community did not. CultivationSetup is about culturing the community — bioreactors, flasks, chemostats — not about the experimental system a field community was sampled from.
No field in the record distinguishes it
I checked all three candidates before assuming any of them worked:
community_origin — three NATURAL-origin records legitimately carry a setup, all verified as genuinely cultivated: GLBRC_UFMP_Fermentation_Community (in-house CSTR from a 4 L flask), Phormidium_Alkaline_Consortium (planar and tubular photobioreactors), Thiocyanate_Afipia_Thiobacillus_Bioreactor_Community (five CSTRs). Natural origin, cultivated afterwards.
ecological_state — the same two are STABLE, not ENGINEERED. Filtering on ENGINEERED would drop legitimate records.
community_category — a RHIZOSPHERE record already carries one (Lunar_Martian_Simulant_PGPB_Lettuce_SynCom, a stirred-tank bioreactor), as do CARBON_SEQUESTRATION and OTHER. Environmental-sounding categories are not environmental communities.
So: no combination of the record's own metadata separates "was grown in a vessel" from "was sampled from the world." The check has to be a human reading the source.
Why this matters now
The obvious next step on #183 is to batch the remaining records. That would be a mistake without this check, and the check is not automatable from the KB. The candidate ranking I have been using (member coverage + methods keywords + full-text cache) is a good filter for readable, and no filter at all for cultivated.
Not proposing a test
A guard here would need an allow-list covering every legitimate case, and the four above show the boundary does not follow any field. An allow-list that has to name each record individually is a list of decisions, not a rule — and it would give false confidence to exactly the batch run it is meant to protect.
Recorded here instead, so the next person to pick up #183 knows the ranking does not answer this question.
Found selecting the eleventh #183 record. Worth filing before anyone batches the remaining ~31, because the discriminator I looked for does not exist.
The case
Avena_Rhizosphere_CrossKingdom_SIP_Communitycame top of the candidate ranking: 95k of cached full text, 100% member coverage, methods keywords throughout.It is a stable-isotope-probing study of native rhizosphere soil. Avena fatua was grown under ¹³CO₂ and paired rhizosphere/non-rhizosphere soil was collected at 6 and 9 weeks; the microbial community was never grown in a vessel by anyone. Giving it a
cultivation_setupwould assert a cultivation that did not happen — the same shape asSoil_Corrinoid_B12_Reservoir_Community, which was once scored 5/5 on growth conditions belonging to an E. coli reporter strain in a community that is metagenomic.The plant had a growth setup. The community did not.
CultivationSetupis about culturing the community — bioreactors, flasks, chemostats — not about the experimental system a field community was sampled from.No field in the record distinguishes it
I checked all three candidates before assuming any of them worked:
community_origin— threeNATURAL-origin records legitimately carry a setup, all verified as genuinely cultivated:GLBRC_UFMP_Fermentation_Community(in-house CSTR from a 4 L flask),Phormidium_Alkaline_Consortium(planar and tubular photobioreactors),Thiocyanate_Afipia_Thiobacillus_Bioreactor_Community(five CSTRs). Natural origin, cultivated afterwards.ecological_state— the same two areSTABLE, notENGINEERED. Filtering onENGINEEREDwould drop legitimate records.community_category— aRHIZOSPHERErecord already carries one (Lunar_Martian_Simulant_PGPB_Lettuce_SynCom, a stirred-tank bioreactor), as doCARBON_SEQUESTRATIONandOTHER. Environmental-sounding categories are not environmental communities.So: no combination of the record's own metadata separates "was grown in a vessel" from "was sampled from the world." The check has to be a human reading the source.
Why this matters now
The obvious next step on #183 is to batch the remaining records. That would be a mistake without this check, and the check is not automatable from the KB. The candidate ranking I have been using (member coverage + methods keywords + full-text cache) is a good filter for readable, and no filter at all for cultivated.
Not proposing a test
A guard here would need an allow-list covering every legitimate case, and the four above show the boundary does not follow any field. An allow-list that has to name each record individually is a list of decisions, not a rule — and it would give false confidence to exactly the batch run it is meant to protect.
Recorded here instead, so the next person to pick up #183 knows the ranking does not answer this question.