Skip to content

Create an evidence category boundary atlas

Create an evidence category boundary atlas: A boundary atlas gives reviewers concrete edge cases before the final handoff.

Guides

What should an evidence category boundary atlas make inspectable?

Consider a craft-room review that repeatedly confuses access problems with capacity problems. A boundary atlas gives reviewers concrete edge cases before the final handoff. It prevents advice for a larger box when the reported obstacle concerns reaching contents, while retaining ambiguous passages instead of forcing every account into a clean category.

Artifact schema and decision check
Use these editorial columns: category; inclusion_rule; exclusion_rule; boundary_passage; classification_reason; unresolved_condition; decision_consequence.
Decision check: Test whether merging categories would alter the proposed action. Keep a genuine distinction when it prevents a wrong remedy, and avoid needless splits that have no decision consequence.
01 / Guides

Name the task and decision

Define categories by the reported task outcome. Distinguish inability to reach an item from inability to fit intended materials. Record the recommendation each category might affect so the distinction remains useful, not an abstract taxonomy that adds labels without changing any evidence-based decision in the brief.

02 / Guides

Choose the eligible material

Include clear examples and difficult passages. Exclude analyst-created incidents from observed evidence, while allowing clearly labeled hypothetical training examples separately. Montage original references should preserve surrounding context; unavailable details remain unresolved and cannot be assumed to make an awkward case fit the preferred category.

03 / Guides

Build the reviewable record

Explain why each boundary case belongs in one category, both or unresolved. A crowded box can create both access and fit problems, but the passage must support each label. Multiple codes do not create multiple independent incidents or justify duplicate case counts in the final research summary.

04 / Guides

Resolve or preserve the limit

Test whether merging categories would alter the proposed action. Keep a genuine distinction when it prevents a wrong remedy, and avoid needless splits that have no decision consequence. Automated coding agreement may help consistency but cannot independently establish that the source actually reports the inferred mechanism.

05 / Guides

Hand over the next action

Deliver inclusion rules, exclusions and unresolved examples with source locations. The atlas supports consistent local review, not an assertion that the categories capture every storage problem or describe all users. Keep any proposed recommendation tied to the observed task rather than treating the category label itself as proof.

Keep the boundaries clear.

  • Keep any proposed recommendation tied to the observed task rather than treating the category label itself as proof.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage