You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Copper heap metadata: reconcile indigenous field community, abundances and cultivation contexts #1358
Non-graph followup for CommunityMech:000019 from the three primary main bodies cited in the graph issue.
The record describes a closed engineered five-member consortium, although 2009 investigates an open indigenous field community with additional detected groups; industrial management does not establish deliberate five-strain assembly. Its heap cycle was 400 days and run-of-mine ore had mixed copper sulfides, not simply a short chalcopyrite-only assay. Ferroplasma DNA was approximately 10^3 copies/mL, not 10^5; Sulfobacillus field signal is genus-level and must not establish exact species or 50-60 C field niches. Several environmental-factor evidence explanations cite unrelated constant-abundance text as quantitative Fe, oxygen or temperature evidence. Stable DNA is not constant oxidation flux.
Acceptance: separately reconcile taxonomy annotations, functional roles, community origin/engineering metadata, environmental factors and medium provenance. Distinguish 2018 MAC assays at 38 +/- 2 C with A. caldus from 2022 separate strains at 28/45 C and from generic 9K recipes. Do not transfer L. ferrooxidans results to L. ferriphilum. Preserve source discrepancies and validated canonical grounding rather than inventing replacements. Generic 9K/ingredient identities and duplicated concentrations need source-backed review; existing #1082/#1289 cover broken external links and are not duplicated or closed here. The graph-only patch does not close this metadata issue.
Dedup: 691 all-state issue titles/bodies plus hidden/ignored-inclusive local reports/history/research/tests searched. No exact finding in that scope; comments not exhaustively searched. Source-based self-adversarial review, not independent approval.
Explicitly tracked as an open non-graph followup in #1361; the graph-only patch does not close this issue or certify unrelated metadata. Full source scope and access limits are in committed batch25 reports.
Activity
realmarcin commentedon Oct 6, 2026
Explicitly tracked as an open non-graph followup in #1361; the graph-only patch does not close this issue or certify unrelated metadata. Full source scope and access limits are in committed batch25 reports.