Triage indications on your case

An indication is a named claim that something needs improvement. A downvote says something here is wrong; an indication says what.

Raising one is the triage. There is no approval step behind it, and no moderator queue it waits in — other creators who reference the target see the claim as soon as you write it.

Before you begin

• You own at least one case, which is what opens the curation surface. See Work the curation catalogue.
• You have the queue open at /curation, with the target you care about on screen.

Both actions below happen in a panel that opens under a catalogue row. A row offers exactly one of them, and which one is a property of the row.

Raise a claim

The row’s button reads Raise when no claim stands on that target for you.

1. Click Raise on the row. A panel opens under it.

2. Write what needs improvement, under What needs improvement. The placeholder says the job plainly: “Name what is wrong — a downvote alone cannot”.

3. Click Raise indication.

Confirm it worked: the panel closes, the queue re-reads, and the row’s Indication column now shows an Open pill.

The summary is capped at 4,000 characters. Leaving it blank is refused before anything is sent:

Say what needs improvement before raising it.

One live claim per target

A target carries at most one unsettled claim. If one already stands, the server refuses the second:

indication <id> already stands on <TYPE> "<target>"; dispose of it instead of
raising another

<id>, <TYPE> and <target> are filled in with the real values. The refusal names the way forward: judge the standing claim rather than opening a rival one.

“Standing” is asked for you. A target somebody else settled, or that you settled and that fresh downvotes have resurfaced, can be raised again.

You need not own the target

Owning a case is what opens the curation surface. It is not a condition on what you may raise a claim about: any target in the queue takes one, including a technology you never provisioned and somebody else’s case.

Disposing is where ownership returns, and only for one target type — a case can be judged by its owner alone.

Record a judgment

The row’s button reads Dispose when a claim stands open for you.

1. Click Dispose on the row. The panel opens, with the standing claim’s text at the top under The standing claim.

2. Read Already decided by other creators, if the section is there. See Adopt another creator’s fix below.

3. Choose a Verdict: Resolved or Won’t fix.

4. Write a Note. It is required on both verdicts — a resolved says what was corrected, a won’t-fix says why nothing will be. Leaving it blank is refused before anything is sent:

   A note is required on both verdicts — say what was corrected, or why nothing will be.

5. On a knowledge component you are resolving, name the Resolving component — see Name the fix below.

6. Click Record judgment.

Confirm it worked: the panel closes, the queue re-reads, and the row leaves the default view — it is settled for you now.

Cancel backs out without writing anything.

Both verdicts are terminal, and neither is an approval

Resolved and Won’t fix both close the claim. Neither is a vote on whether the claim was a good one, and there is no third state in which somebody senior looks at it.

Who a judgment settles it for

This is the one rule worth learning, because the three targets differ:

Target	Your judgment settles it for
Knowledge component	You alone. Every other affected creator still decides for themselves.
Technology	Everyone. The first creator to judge it settles it.
Case	Everyone, and only the case’s owner can judge it.

The reason is what a fix reaches. Correcting a component mints a new component with a new reference id, which does not reach anybody else’s already published case — so each affected creator has their own decision to make. A technology’s description is patched in place, so one correction reaches everyone.

If somebody else settled it first, the server says so:

curation indication <id> was already disposed of by <name>

Name the fix

When you resolve a knowledge component claim, a Resolving component field appears. It names the component that answers the claim — a new revision, or an alternative definition.

Start typing part of a reference id or part of what a component says, and pick from the suggestions. The claim’s own target is excluded from them: a component cannot resolve itself.

The field appears only where it can mean something:

• On a technology or a case, naming a component is refused with a 400. Correcting either one changes the thing in place, so there is no new id to point at.
• On a Won’t fix, naming a component is refused too. A won’t-fix says nothing changed, so it cannot name what changed it.

A reference that resolves to nothing is refused:

resolving knowledge component "<reference>" was not found

Adopt another creator’s fix

When a claim already carries judgments from other creators, they are listed above the verdict control, oldest first — each with the creator’s name, their verdict and their note.

This is deliberately placed before you decide rather than after. Where a creator named a resolving component, their entry carries two things:

• the reference, as a link that opens the component in a new tab, so you can read the fix before endorsing it
• an Adopt button

Adopt fills the resolving component in with theirs and sets the verdict to Resolved, because adopting a fix is resolving.

Adopting is what stops a third near-duplicate

Without it, each affected creator writes their own corrected component and the knowledge base grows three write-ups of one idea. Adopting says their fix answers my claim too.

A settled claim is not a closed subject

A judgment removes the target from your default queue. It does not end the subject.

The catalogue counts downvotes since your judgment, so a target you marked Won’t fix comes straight back if learners keep voting it down. Those are the rows most worth watching, which is why the pill’s own hover text says the verdict is not final.

Turn on Show analyzed in the queue to see what you have already judged.

What’s next

• Work the curation catalogue — the queue these actions are taken from.
• Correct or retire a published case — what a resolved claim on a case of yours turns into.
• Generate and push components — where the corrected component you name comes from.