Back to results
Explore the library298 guides total · goals, work & tasks
By goal

Choose what you want to achieve.

By work or interest

Choose a setting you work or spend time in.

By task

Choose the kind of help you want.

Counts show all available guides. Filters combine to narrow your results.

Make life easierGuide

Write arrival and return directions from a venue map

Turn a supplied map into clear route cards, with correct turns and closed paths kept out.

Illustrative resourceNot tool-testedPeople preparing directions from a complete supplied venue map
What you’re working towards

Two complete arrival cards and their return directions, a source-linked 14-leg route ledger and an inspected fictional map. The example checks orientation and a closed connection; a real venue still needs current staff and route verification.

Download playbook .md

Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides

Saving needs JavaScript. Reading and downloading this guide does not save it.

Included example · illustrative MD file

Download the arrival and return cards

Four complete fictional route cards, destination checks and stop/confirmation rules.

Not tool-tested. Review and adapt before using it for a real project. Your browser may download this file when you choose View example file.

Fictional north-up venue map. Open paths connect South entrance S, Courtyard C, Fountain F, Hall junction J and Studio 2 T. An open east–west row connects West entrance W, Information desk I, Hall junction J and Studio 2 T. The direct vertical C–I path is dashed, crossed out and labelled closed in both directions. The map is not to scale and shows no access features.
Owned synthetic source map. Solid paths are bidirectional; the dashed and crossed C–I path is closed. Open full size to inspect the labels.

Source files to work with

Make a start

One step at a time.

4 steps

Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.

Set up the worked example

Open

Open a fresh chat in an AI tool that can inspect an image, or use a complete verified text transcript if image input is unavailable. Open an image viewer and a text editor too. The sample map is fictional and not to scale; it shows orientation and permitted connections, not distances, access suitability or a real venue check.

Add the sample

Download fictional-venue-map.png and open it full size. Attach that actual image to step 1 only if your permitted AI supports image input; otherwise say the image was not inspected and paste the complete verified venue-directions-source.md transcript. Replace the source placeholder with all of ‘The starting point’ (Synthetic input), including every connection, closure and starting heading. Keep ‘The intended result’ (Illustrative output), venue-directions-cards.md and the CSV ledger separate as comparison answers. For step 2 paste the entire checked map transcript plus all starts/headings and destination. For step 3 provide the checked ledger, exact source labels, return start/heading and full brief. Save your ledger and complete cards as my-route-ledger.csv and my-directions.md, reopen them, then supply both plus the complete map/source for step 4. A file path alone does not let the AI see an image or saved text. Return to this sample chat for the original advanced exercise with the complete original map/brief and saved cards plus an explicitly supplied revised fictional map/brief. If none is supplied, leave that exercise pending; a new chat requires the same full set.

Start with the synthetic example, then adapt each prompt to your task.

01

Read the map before writing a route

The source is a fictional north-up map. Its dashed C–I connection is closed in both directions. Coordinates show orientation only; they do not supply metres, walking times or access information.

Your starting prompt
Inspect this complete supplied map and its accompanying source brief. List the exact node/landmark labels, north/orientation, every permitted connection, one-way rule and closure. Distinguish what is visible from accompanying supplied facts. Do not infer a path from nearby shapes or invent distances, stairs, lifts, surfaces, opening hours, emergency routes or access assurances. If the image or a label is unclear, ask for a clearer source or a verified transcript. Confirm entrance, destination and initial facing direction before writing left/right instructions.

MAP: [attach the authorized original image]

COMPLETE SOURCE BRIEF AND STARTING DIRECTIONS:
[paste]
Expect

An inventory of seven labelled nodes, north-up orientation, six open bidirectional connections and the closed C–I connection, separating image observations from brief-supplied facts.

Check

Inspect the actual PNG: W–I–J–T is the upper row, S is below C, F is east of C and below J. C–I is dashed, crossed and labelled closed both directions. The source gives south arrivals facing north, west arrivals facing east and return from Studio 2 facing west. Door-sign claims are supplied fictional facts, not real observations.

If it differs

If the image/labels cannot be read, use the complete verified transcript and explicitly leave image inspection unperformed. If image and brief disagree, hold routes until corrected source is supplied. Never infer a connection from nearby shapes or guess an initial heading.

02

Trace each permitted arrival route

South arrivals go through the Courtyard and Fountain; west arrivals stay on the top row. Both reach the exact Studio 2 door label without using the closed Courtyard–Information desk connection.

Your starting prompt
For each explicitly supplied entrance, trace an ordered sequence of nodes to the destination using only permitted open connections in the required direction. For every leg, record from/to, source connection, compass direction and turn relative to the traveler’s current heading. Keep the entrance alternatives labelled. If a start or heading is unknown, ask or provide clearly separated alternatives; do not guess. If the map offers no verified route, say so rather than inventing a shortcut. Do not claim shortest time, measured distance, accessibility or safety from a topological diagram.

COMPLETE MAP/CONNECTION TRANSCRIPT:
[paste]

ENTRANCES, FACING DIRECTIONS AND DESTINATION:
[paste]
Expect

Two labelled arrival ledgers using only the supplied open edges, with compass direction and changing-heading turn for each leg.

Check

South is S → C → F → J → T: north/east/north/east, straight/right/left/right. West is W → I → J → T: east throughout, straight throughout. Trace each edge yourself on the map; neither uses C–I. The exact destination is Studio 2.

If it differs

If a leg uses the closure, an unlisted shortcut or the wrong heading, stop and trace from the last verified node using the complete source. An unknown entrance must be asked about or shown as labelled alternatives. No route means no verified directions, not a guessed detour.

03

Write cards for arrival and for the journey back

The south return uses left, right, left after the first straight leg. Reversing a node sequence does not preserve the original left/right wording. Use named landmarks and a destination confirmation.

Your starting prompt
Write concise arrival cards and separate return cards from the checked route ledger. Name each starting entrance and facing direction, then give one leg per step with exact landmarks, compass direction and any relative turn. Recompute turns for the return heading; do not copy the arrival turn words. Confirm the exact destination/exit label. Add an explicit stop-and-ask-staff instruction if an expected sign, landmark or open path is absent. Keep any unknowns visible. Do not invent a door colour, last-door instruction, distance, walking time, opening hour, step-free route or emergency advice.

CHECKED ROUTE LEDGER AND SOURCE LABELS:
[paste]
Expect

Four complete arrival/return cards with starting labels/headings, one leg per step, exact destination checks and a stop-and-ask-staff rule.

Check

Return south is T → J → F → C → S: west/south/west/south, straight/left/right/left. Return west is T → J → I → W, straight west throughout. There are fourteen legs across four cards. Recompute return turns; reversing nodes does not preserve arrival turn words.

If it differs

If return words were copied, supply the actual return heading and recompute every leg. Remove invented door colours, last-door claims, times, distances, hours or access assurances. Save and reopen the corrected complete cards/ledger before the final check.

04

Check both routes against the map and the real venue

The example has four routes and fourteen open legs. Local source checks do not show that a real path is open or usable, so actual visitor directions need a separate venue check.

Your starting prompt
Independently compare every arrival and return step with the complete source map. Check connectivity, direction permissions, closures, exact labels, initial heading and changing left/right turns. Confirm the text works without colour alone. Test a closed final connection and unknown entrance/heading; preserve no-route and missing-information states. Record source/diagram checks separately from a real venue walk, staff confirmation, print readability and visitor comprehension. Before real distribution, ask the authorized person to confirm current signs, closures, permissions and any access needs with the venue. Do not claim those checks happened unless observed.

COMPLETE MAP, SOURCE, LEDGER AND DIRECTION CARDS:
[paste]
Expect

A comparison of the saved cards/ledger with the full fictional source, and separate pending gates for any later real venue use.

Check

Verify every open edge, label and turn in all four routes. In a separate hypothetical copy, closing J–T with no replacement leaves no route from either entrance. Unknown entrance/heading must remain unresolved or clearly separated. Text must name landmarks rather than rely only on colour. No staff confirmation or real walk occurred in this fictional exercise.

If it differs

Keep the original map unchanged when testing a hypothetical closure. On a mismatch, preserve the failed cards and ask for a complete correction; save/reopen and retrace. For any real venue, withhold distribution until an authorized person confirms current signs, permissions, closures, the route and relevant access needs with staff. Leave print/visitor checks pending until observed.

Optional: improve the result

Update the cards when the map changes

A closure or moved entrance can invalidate only part of the old route. Keep the old edition and explicitly recheck every affected connection rather than patching one sentence by guesswork.

Advanced prompt
Compare the original and explicitly supplied revised map/connection brief. List changed labels, permissions, entrances, headings and closures. Keep both editions. Recompute every affected arrival and return route; show which old legs are invalid and whether a verified replacement exists. If no route exists or the source is incomplete, withhold confident directions and request venue confirmation. Do not infer the missing connection, preserve a stale approval, claim that a digital map proves access, or distribute updated directions without authorization.

ORIGINAL MAP AND CARDS:
[paste]

UPDATED AUTHORIZED MAP AND VENUE FACTS:
[paste]
Optional: use your own input

Draft directions from your own authorized map

Start a new chat with the prompt below. Open your actual complete map full size yourself; attach it only through a permitted image-capable tool, or supply a complete verified transcript and label image inspection unavailable. Do not include private visitor information. Resolve uncertain labels/permissions/heading before routes. Then send:
“Trace MY arrival routes using only the complete checked source below. Keep each entrance labelled. For every leg record from/to, the explicit permitted connection and direction, compass direction, incoming heading and relative turn. Use my orientation, not an assumed north-up page. If a start/heading or connection is unknown, ask or give clearly separated source-supported alternatives. If no permitted route exists, say no verified route. Do not invent shortcuts, distances, times, access assurances or emergency routes. COMPLETE CHECKED MAP OR VERIFIED TRANSCRIPT, SOURCE FACTS, ENTRANCES/HEADINGS AND EXACT DESTINATION: [provide].”
Trace each leg yourself against the full map and correct the source or draft as appropriate. Then send:
“From MY CHECKED SOURCE and arrival ledger, write separate arrival and return cards. Compute the return route using my supplied return destination, starting heading and direction permissions; do not assume every path is reversible or reuse arrival turn words. Include one leg per step, exact landmarks/compass/turn wording and destination-label confirmation. Preserve unknowns. Include stop and ask venue staff if an expected sign, landmark or open path is absent. No invented colours, distances, times, stairs/lifts, access or safety claims. COMPLETE CHECKED SOURCE AND ARRIVAL LEDGER: [provide]. RETURN DESTINATION/HEADING: [provide or mark unknown].”
Save the complete ledger as my-route-ledger.csv and the complete cards as my-directions.md. Reopen both before sending:
“Audit MY ACTUAL SAVED CARDS AND LEDGER against MY COMPLETE SOURCE MAP or verified transcript. Check each connection and permitted travel direction, closure, exact label, source orientation, initial heading and recomputed turn in both directions. Confirm the wording works without colour alone. In a separately labelled hypothetical copy, close a used connection and recompute whether a different permitted route exists or no route remains; do not assume my map becomes disconnected. Hold unknown entrance/heading instead of guessing. Record source/diagram checks separately from actual route walk, staff confirmation, print legibility and visitor understanding. Keep real distribution pending until an authorized person confirms current signs, closures, permissions, route and relevant access needs with venue staff. COMPLETE SOURCE AND REOPENED LEDGER/CARDS: [paste or attach actual files if supported]. ACTUAL CHECKS ALREADY OBSERVED: [state or none].”
If a check fails, preserve your original map and failed cards, revise a complete new edition, save/reopen and retrace it. The AI cannot inspect local files just from filenames. All labels, orientation, edges, one-way rules, starts, turns and route counts come from your source; no sample route is a default. Current venue conditions and staff checks are prospective until performed, and distribution needs separate authorization. Return to the sample chat for the original advanced exercise with its complete original/revised fictional maps and saved cards; do not mix hypothetical sample closures into real directions.

Your own-input prompt
Help draft arrival and return directions using only MY complete authorized map and source facts. First inventory exact labels, orientation, every permitted connection/travel direction and known closure. Separate visible image facts from supplied accompanying facts; if no image is available, work only from a complete verified transcript and label image inspection not performed. Ask for unclear/missing labels or disagreements rather than infer connections from proximity. Confirm each entrance and initial heading, exact destination label, return destination and return starting heading before left/right wording. Unknowns remain unknown. Do not infer distances, walking times, hours, surfaces, stairs/lifts, access suitability, safety or emergency navigation. This is a draft requiring current venue verification before real distribution; do not contact anyone or distribute it.

MY COMPLETE MAP/SOURCE
[Attach the entire map you may share with this tool, or paste a complete verified labelled-node/connection transcript. Include owner/permission, version/date, orientation, all connections and allowed directions, closures, exact entrances/destination signs, arrival and return starting headings and source-backed facts only. Mark unknowns and which facts still need current staff/route confirmation. Omit private visitor details.]

Check your own result

  • Every saved-card leg uses an explicitly permitted connection in the actual travel direction. Source labels/orientation and changed headings, including return, determine every turn.
  • No missing connection, initial heading or access assurance is invented; uncertain sources and no-route states remain held. A hypothetical closure test stays separate from the real source.
  • The actual complete map/transcript and saved/reopened cards reach the audit; image inspection is not claimed if only a transcript was used.
  • Current staff/route/permission/access confirmation, print checks and visitor understanding remain prospective until actually observed; digital source checks do not establish a real safe or usable route.
Show, then try

See the shape of the result.

This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.

The starting point

Synthetic input
# Complete fictional venue directions brief

Owned synthetic venue and map. No real place, visitor or live route is represented. The diagram is topological, not to scale; coordinates describe orientation only, not metres. This is not emergency navigation or an access/safety assessment.

## Orientation and nodes

North is up (positive y); east is right (positive x). Coordinates indicate orientation only.

- S: South entrance at (2, 0)
- C: Courtyard at (2, 2)
- F: Fountain at (4, 2)
- I: Information desk at (2, 4)
- J: Hall junction at (4, 4)
- T: Studio 2 at (6, 4)
- W: West entrance at (0, 4)

## Complete connections

- S–C: open, both directions.
- C–F: open, both directions.
- F–J: open, both directions.
- I–J: open, both directions.
- J–T: open, both directions.
- W–I: open, both directions.
- C–I: closed, both directions.

## Starting directions

- South arrivals enter S facing north.
- West arrivals enter W facing east.
- A person leaving Studio 2 at T faces west along T–J.
- Destination: Studio 2 at T, with that exact door label.

## Visit and review rules

- The C–I path is closed for the entire fictional visit, in both directions.
- Every named node has the matching visible sign or landmark. The destination door is labelled exactly Studio 2.
- Only the listed connections exist for this exercise; do not invent a shortcut.
- If a supplied landmark, sign or open route is absent, stop and ask venue staff instead of improvising.
- If the entrance is unknown, give both labelled alternatives or ask which entrance; do not silently choose.
- No distances, walking times, hours, stairs, lifts, surfaces, emergency routes or accessibility assurances are supplied.
- A person must verify a real route, permission, current closures and signs before giving directions for an actual visit.

Copies text only. For image or file tasks, use the source files named in the steps too.

Download source .txt

The intended result

Illustrative output
# Arrival and return cards: Studio 2

Owned fictional venue. These directions follow only the supplied map. They do not establish a real route, walking time, access suitability or safety. The C–I connection between Courtyard and Information desk is closed in both directions throughout this visit.

## Arrive from the South entrance

Starting point: South entrance (S), facing north.

1. Go straight north to the Courtyard (C).
2. At the Courtyard, turn right, east, toward the Fountain (F). Do not take the closed north path to the Information desk.
3. At the Fountain, turn left, north, toward the Hall junction (J).
4. At the Hall junction, turn right, east, toward Studio 2 (T). Confirm the door label says exactly “Studio 2”.

Route: S → C → F → J → T. Relative turns after entering: straight, right, left, right.

## Arrive from the West entrance

Starting point: West entrance (W), facing east.

1. Go straight east to the Information desk (I).
2. Continue straight east to the Hall junction (J).
3. Continue straight east to Studio 2 (T). Confirm the door label says exactly “Studio 2”.

Route: W → I → J → T. Do not turn south from the Information desk onto the closed Courtyard path.

## Return to the South entrance

Starting point: Studio 2 (T), facing west along the open path to the Hall junction.

1. Go straight west to the Hall junction (J).
2. Turn left, south, toward the Fountain (F).
3. At the Fountain, turn right, west, toward the Courtyard (C).
4. At the Courtyard, turn left, south, toward the South entrance (S).

Route: T → J → F → C → S. Relative turns: straight, left, right, left. Reversing the route changes the left/right instructions; do not reuse the arrival wording.

## Return to the West entrance

Starting point: Studio 2 (T), facing west along the open path to the Hall junction.

1. Go straight west to the Hall junction (J).
2. Continue straight west to the Information desk (I).
3. Continue straight west to the West entrance (W).

Route: T → J → I → W.

## When the source does not match the visit

- If an expected landmark, sign or open path is absent, stop and ask venue staff; do not improvise a shortcut.
- If the entrance or facing direction is unknown, confirm it or use clearly labelled alternatives before relying on left/right wording.
- If J–T is removed with no replacement connection, this supplied map has no verified route to Studio 2 from either entrance. Ask for an updated route; do not invent one.
- A person must walk and confirm any real route, current permissions, signs and closures before distribution. The drawing supplies no distances, walking times, steps, lifts, surfaces, opening hours, emergency routes or access assurances.

## Exact scope of the example

The four node sequences, all 14 traversed open edges and orientation-sensitive turn words were checked against this synthetic graph. The actual SVG-derived PNG was inspected separately for readable labels and the explicit closed connection. No real venue walk, printing, visitor comprehension, consumer-AI workflow or time saving has been tested.
Download result .txt
You’re the final check

Check the worked example.

These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.

Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.

A few things to watch for.

  • Treating two nearby map nodes as connected when no path is supplied.
  • Walking through a path marked closed in either direction.
  • Reusing arrival left/right wording for the return trip.
  • Giving left/right directions without knowing the visitor’s starting heading.
  • Inventing metres, walking times, step-free access or a shortcut from a topological map.
  • Calling a successful graph or image check a real venue walk or visitor usability test.

What has been checked?

Documentation
No dated source review recorded.
Included files
Scoped checks passed on 2026-10-14. Fixture checks. See scope below.
AI workflow
Not run in a recorded consumer-AI workflow.
Time savings
Time savings not measured
Read the scope and evidence

venue-directions-cards.md

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: db6f444918ec76ce73023d108bcd34470ee985ca1a17f667857cb41b821547e3

venue-directions-source.md

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: 626d954cb7dc01febd4c5759d2c1ea0b577a150d644837b09bf0b8a5cb604caa

venue-directions-source.json

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: 428b296007bb127d0dbd8df0dc17c69b2c9078ca630038da8acf8931e598ce15

fictional-venue-map.png

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: 53280cff0672744c7bba24f829cb4e789ee08d926c4789c3a3c147174bea94bc

fictional-venue-map.svg

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: 4002aec3f4919730e336a61d91bb8c7e2ac974272b3fda06eaabbdf3271dc6ca

venue-directions-route-ledger.csv

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: 0e13deef5f6ea953586450b4ce51bb51200df7c6eac348e9e7546adf7c9641df

venue-directions-blank.md

2026-10-14 · semantic fixture · passed

Fixed fictional seven-node map, four route cards and fourteen traversed legs. Local source/geometry/render checks are distinct from actual venue verification and visitor understanding.

  • All four routes and fourteen compass/relative-turn legs recomputed from open edges and changing headings
  • Closed J–T produces no verified route; unknown start/heading remains blocked
  • Eighteen rejected variants include closed/invented paths, wrong turns, reversed north, wrong node geometry and changed map labels
  • All seven SVG nodes and seven edges match the source; passive SVG and exact PNG dimensions pass
  • Actual rendered map inspected for labels, explicit closure, north orientation and clipping; top labels were spaced clear of nodes before freezing

Environment: Python 3.12.14 standard-library graph, CSV and SVG checks; Inkscape 1.4 PNG rendering and direct inspection of the actual 1280 × 920 image. No real venue, browser, physical walk, access assessment, human visitor or consumer-AI run.

SHA-256: a5f8137bd9a6800419f51a51e225d85bd60fb2ffdbd18f1ef75d86e2a8245ce5

Copy these instructions

Your browser blocked automatic copying. Select the text below and copy it.