Evidence & relationships
このコンテンツはまだ日本語訳がありません。
Every artefact in a register carries the trail of where it came from and how it relates to other items. This page covers three things that cut across all the registers: the evidence chain, typed relationships, and duplicate review.
The evidence chain
Section titled “The evidence chain”Open any item — a risk, decision, action, and so on — and its detail page shows an Evidence panel: the communications the item was extracted from. For each source you see the subject, who it was from, when it was sent, the classifier’s confidence, and the exact quote (the claim excerpt) that supports the item:
“FRP pan failing in guestrooms”
If an item came from an attachment rather than an email body, the panel shows a Source: filename link that opens the original file. This is how you verify a fact — you can read the text it was lifted from.
An item with no evidence links was either created manually or had its evidence removed.
Relationships
Section titled “Relationships”Artefacts can be linked to each other with a typed relation (see the Glossary):
| Relation | Meaning |
|---|---|
| supersedes | A newer item replaces an older one (directed, newer → older) |
| duplicate | The same thing said twice |
| contradicts | Opposite positions — a sign the project reversed course |
| relates | Connected, but none of the above |
The system works these out automatically across decisions, risks, issues, actions and meetings — you don’t review them one at a time. Relations show up as badges on register items (for example ↺ 3 prior, ⧉ 2 duplicates, ⚠ 1 contradicts), and they drive each item’s effective register state: the register shows the live head of each chain, and a superseded item is dimmed.
The relations review
Section titled “The relations review”The Relationships page lists relations the system was least confident about under Needs attention (switch to All to browse everything by type). On each one you can re-type the relation or confirm it. Direction for supersedes comes from the items’ dates, so a wrong direction usually means a wrong date.
Your changes are staged until you click Re-resolve registers, which rebuilds the current/superseded state from the reviewed relations. An override you make sticks even when the classifier re-runs.
Duplicate review (dedup)
Section titled “Duplicate review (dedup)”Use the Duplicate review page to find and merge artefacts that describe the same thing. Click Run dedup and the system:
- Finds candidate pairs by similarity. LLM-gated mode (the default) reads each pair and catches paraphrased duplicates; Cosine mode is a cheaper geometric match that can miss reworded ones.
- Judges each pair as same, different, or unsure, with its reasoning.
- Groups the same pairs into clusters.
- Merges each cluster into one entry — keeping the most-substantiated row as the winner, re-pointing evidence links to it, marking the others superseded, and updating the knowledge graph.
The work runs server-side, so it keeps going even if you close the tab. A progress panel shows the live log.
Pending clusters appear under Pending (clusters). Tick the clusters you want, optionally change the winner with the radio button, and Approve to merge in a batch. You can also tick Auto-merge confident clusters to skip the review for clear-cut ones. Pairs the system judged different or unsure can be accepted as kept separate so they stop reappearing on every scan. The Merged and Kept separate tabs are a read-only history of past decisions.