radar_review
When to use
magi radar status reports a digest waiting, or magi next says so.
Method
magi radar status --json, then read the digest.- Read the project first:
magi stats wiki-summaryand the open propositions inthreads/. Relevance is to what is asked here, not the field. - Score each candidate by hand. The digest's score is a rank, not a measurement, and a project with no vector index has none at all — then the order carries nothing and every candidate has to be read.
magi search "<title>"before keeping one: a paper the project already covers is not new information, it is a duplicate.magi radar triage --id <id> --decision accept|dismiss, ids from the digest and--idrepeatable when the decision is the same. Never hand-edit the frontmatter — the triage ledger is what the next run reads.- Accepted papers:
magi ingest url "<id>"to queue them, then hand off to theingestskill. magi radar triage --donecloses the report and prints how many of how many you decided. Until you run it,syncandnextkeep reporting it.
Rules
- Never accept a paper because it scored well. The score orders the reading; the judgement is yours and it is the whole point of this step.
- Each candidate is its own question. Judge it against the project, not against your reasoning about the ones before it: twenty in, that reasoning is the loudest thing in context and the least relevant, and the bar drifts.
- Never leave a digest half-triaged without saying so.
--doneprints the count; say the same thing in your own report, and where you stopped. - A citation-gap report asks a different question: whether this project owes a citation, not whether the paper is nearby. Most nearby papers are not owed.