Proposed change
reason
v0.351 solo-maintainer brain-tumor translation wave: exact public identifier match; clears needs_review without changing the assertion.
frontiers / frontier
Reviewable change
back to reviewPediatric high-grade glioma in NF1 patients (neurofibromatosis type 1) often arises in optic pathway and may behave more indolently than sporadic HGG; mechanistic drivers include NF1-loss-induced RAS hyperactivity, with selumetinib showing efficacy in this molecular setting (Fangusaro 2019).
This is a proposal, not yet accepted frontier state. It names what it would change and who proposed it. Only an accepted review event, signed under reviewer authority, writes it into the frontier. Until then it carries no authority over the record.
Proposed change
reason
v0.351 solo-maintainer brain-tumor translation wave: exact public identifier match; clears needs_review without changing the assertion.
Provenance
proposed by
reviewer:solo-maintainer
actor type
human
created at
2026-05-21
target type
finding
Affected finding
inspect finding →Pediatric high-grade glioma in NF1 patients (neurofibromatosis type 1) often arises in optic pathway and may behave more indolently than sporadic HGG; mechanistic drivers include NF1-loss-induced RAS hyperactivity, with selumetinib showing efficacy in this molecular setting (Fangusaro 2019).
vf_746329b3a240315cThe diff is computed against current frontier state, the same diff a reviewer reads before deciding.
The live diff is computed from a writable workspace. This frontier is read-only here, so the change is shown as recorded without a recomputed before / after.
Canopus treats material changes like reviewable requests: one bounded packet, check output, reviewer decision, and accepted frontier effect.
Pediatric high-grade glioma: distinct biology, distinct trials receives a reviewable source, finding, caveat, replication, evaluation, or proof-affecting edit.
The packet names affected record objects, evidence, rationale, reviewer-facing fields, and expected proof impact.
Schema, provenance, benchmark, contradiction, and proof checks decide whether the request is ready to read.
A steward accepts, rejects, caveats, revises, or retracts the request under an inspectable identity.
Only the accepted event mutates frontier state. Atlases, constellations, and search update from that record state.