Sultan Task-Package Reachability / 苏丹任务包可达性
This mechanism distinguishes three questions that the Sultan visualizer previously collapsed:
- Are all nodes assigned to the correct content pack?
- Are branches reachable from an internal entry node?
- Is the pack reachable from the wider world graph through a source-backed edge?
A task package may pass the first two and still remain an honest island on the third.
Contract
task_package_reachability:
group_id: required
member_ids_unique: true
raw_source_file_per_member: required
internal_entry_nodes: required
internal_retry_nodes: optional
internal_terminal_nodes: required
branch_families: required
source_backed_internal_edges: required
public_entry_edges: measured
public_exit_edges: measured
external_entry_status: linked | extractor_gap | canonical_review | unresolved_do_not_invent_edge
attach_to_node_ids_without_source: forbiddenInternal reachability
An internally reachable package names:
- the event or rite that begins play inside the group;
- retry or expiry loops;
- every choice fork;
- required cards, slots, counters, and thresholds;
- terminal nodes and durable rewards, losses, deaths, departures, or future routes.
For dark-tide-oasis-expedition, internal reachability starts at 5300147/5300148, retries through 5300149, and terminates through 5000662, 5000683, 5000666, or earlier expedition/farewell closures.
External honesty
If the extracted graph has no public entry, the canonical wrapper must say so. It may document internal entry candidates, but it must not add attachToNodeIds, fabricate an overview edge, or claim whole-world reachability.
The acceptable next fixes are limited to:
- discovering a real raw-source relation;
- repairing extraction of an existing relation;
- making a separately reviewed canonical source edit.
Lens rule
A lens passes only when it can distinguish complete internal branch coverage from unresolved external entry. “The group renders together” is not proof that a player can enter it from the world graph.