← Thinking playground

Concept maps · Night access at the harbor

Night Access Map

Build a sentence, then let robots follow it. Connected lines do not necessarily express the right meaning.

One shared access map

The loader, technician and trainee need the loading room and archive; the visitor needs only reception. Use at most 6 relationships and block every other entry. How can shared concepts reduce repetition?

Your concept mapConnections: 0 of 6
LoaderRobot
TechnicianRobot
TraineeRobot
VisitorRobot
Work groupGroup concept
Specialist groupGroup concept
Loading roomControlled room
ArchiveControlled room
ReceptionControlled room

Dashed: belongs to. Solid: can enter. Dotted: maintains. Read full statements in the connection list and remove links individually.

Gate trial
Not tested

Add connections, then select “Test access”. All four robots are checked against all three rooms: 12 tests, including rooms they must not enter.

View the map ↑

Add a relationship statement

Choose a source, linking phrase and destination, then add. Group members inherit group permissions; maintenance alone grants no access.

Try adding this statement: Loader → belongs to → Work group.

No connections yet. An empty map allows no robot through.

View access requirements and rules
  • Loader: Loading room · Archive; all other rooms must be blocked.
  • Technician: Loading room · Archive; all other rooms must be blocked.
  • Trainee: Loading room · Archive; all other rooms must be blocked.
  • Visitor: Reception; all other rooms must be blocked.

Each relationship occupies one slot, up to 6. You may use nested groups or direct permissions; there is no single correct diagram. Arrows have direction: a group does not inherit its members' individual permissions. No permission means denial. Remove and reconnect freely; tests are unlimited.