Keep a versioned scope history
A boundary change needs a reason, date, approver and list of affected entity decisions. If a previously excluded participant becomes eligible because the Market's task widens, preserve the old ruling and the new source. That history explains why a profile appeared later without pretending the original rule never existed.
- Write the proposed new rule and the evidence that triggered it.
- List affected entities, routes and claims before accepting the revision.
- Keep old and new rule versions plus the decision date and reviewer.
Versioned boundary-change log
| Decision field | Record or rule |
|---|---|
| Trigger | new buyer task or evidence that the current rule misses. |
| Impact | which records enter, leave or change classification? |
| Continuity | which public routes need an update, redirect or explanation? |
- 01Trigger
- 02Impact
- 03Continuity
Check downstream effects
A revised boundary can change category membership, internal links, comparison sets and discovery routes. Review those dependencies before publishing a new map view. The fact that Search1001 supports several relationship axes is useful here: a rule change may affect one capability relationship without changing product identity. Version the relationship, then inspect the pages that use it.
To carry this decision forward, protect the entity graph.
Trace the effects of a changed rule
Suppose a Market expands from one buyer task to a related task. The operator lists newly eligible participants, category edges, comparison pages and source checks. Existing entity IDs remain stable; new relations receive their own evidence. The old boundary version stays available in the decision log so a reviewer can see why a participant was absent before. This matters for both user trust and measurement: an apparent gain in route coverage may come from a changed definition rather than from real market growth.
A rule change needs a history
Do not silently repurpose an established URL for a different task. A boundary change should preserve interpretability of prior evidence.
References and source notes
Original 1000&1 methodology reviewed and approved by the author. Public claims and historical measurements are bounded by the linked sources and dates.