frontiers / frontier
Reviewable change
back to reviewAPOE4 carrier status increases the importance of ARIA risk stratification for anti-amyloid antibody treatment.
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
Decision-console scope: ARIA/APOE4 risk is a stratification and monitoring constraint, not a standalone contraindication claim; interpret with current label criteria, MRI monitoring, anticoagulant context, and local eligibility rules.
Provenance
proposed by
reviewer:will-blair-bot
actor type
human
created at
2026-05-06
target type
finding
Affected finding
inspect finding →APOE4 carrier status increases the importance of ARIA risk stratification for anti-amyloid antibody treatment.
vf_2e7192704f1767e4The 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.
Anti-amyloid translation in Alzheimer's disease 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.