frontiers / frontier
Reviewable change
back to reviewAnti-amyloid immunotherapy ARIA (amyloid-related imaging abnormalities) — edema (ARIA-E) and microhemorrhage (ARIA-H) — occurs in 15-40% of APOE4 carriers receiving high-dose anti-Aβ antibodies; radiological characterization and risk stratification framework published to guide clinical management.
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
ARIA (amyloid-related imaging abnormalities) including edema (ARIA-E) and hemosiderin (ARIA-H) is a well-established class effect of anti-Aβ antibodies, especially in APOE4 homozygotes. Agent-drafted accept; eligible for human re-review.
Provenance
proposed by
agent:vela-curation-bot-2026-05-09
actor type
human
created at
2026-05-09
target type
finding
Affected finding
inspect finding →Anti-amyloid immunotherapy ARIA (amyloid-related imaging abnormalities) — edema (ARIA-E) and microhemorrhage (ARIA-H) — occurs in 15-40% of APOE4 carriers receiving high-dose anti-Aβ antibodies; radiological characterization and risk stratification framework published to guide clinical management.
vf_3ef6135eee626ee1The 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.