The Question Map

Twenty questions across Hitchhikers Field Guide's three documents. Each one now has an answer you can run, and the mapping between them is checked rather than asserted.

Why check a map

It is easy to answer a question in prose and believe it is handled. It is harder to keep believing that when a suite tells you the row is empty.

So every row anchors to the properties that answer it, and a suite fails if a question has no property, if an anchor points at something that no longer runs, or if the inventory drifts from twenty. A new question appearing in their documents has to be added deliberately — it cannot be quietly not-answered.

Where they came from

• seven from the handoff's own ask — how edges are made, disclosure on discoveries, passport restore, id remap, the card, shared quests, where Knowledge lives
• four open questions on the trust-weighted map — what counts as a witness, the default audience, recency, and sharedrops
• five acceptance criteria for Phase 0, which were the most obviously runnable things in the pack and were five unticked boxes — see Phase 0 Acceptance
• four open questions on discovery — the camera, partner claims on map data, the till redeem, and the photograph

The answers that are refusals

Three of the twenty are answered no, and those are the ones worth arguing with.

A shared quest completion is not a trust edge — co-presence with a timestamp has no consent in it. A till redeem is not a trust edge either — a steward and a pilgrim are not symmetric, and one object for both would put every player's trail inside the venue's map in exchange for a cup of tea. And sharedrops should not reuse the social edge type: keeping equity off the map is a UI decision, and UI decisions get revisited by someone who was not in the room, whereas keeping the kinds separate is structural.

The map itself, with every question quoted in full, is in The Working Files as question-map.md.