Scope & compliance / Reserve-land passage
The permission
has a boundary.
Check project scope, passage route and work activity separately. One valid record cannot fill a missing field in another.
Make the route explicit.
- 01
Named holder & dates
Check the actual named permit and its time window before travel.
- 02
Escorted maintenance corridor
The described corridor is the only matching passage in the checklist. Escort and actual permit checks remain necessary.
- ×
Closed shells / entire district
The corridor permit gives no entitlement to these areas, ground disturbance or object removal.
Prepare a local access checklist
This checks the described scope. It does not validate an actual permit, issue permission or send a travel plan.
Work agreement / Defined scope
A category informs.
A project defines.
Reserve 9 work proceeded under a project-specific reserve-land agreement covering the retired workshop district. The scope included dismantling, recovered-material routing and selected ground treatment. It did not authorise eviction outside that agreement or clearing the whole city.
The reserve-land category of the Morrow Accord informs our records. A project still needs its own holder, area, activity and dates; a broad category does not supply those fields automatically.
Read the reserve-land & passage policyNo-intelligence-zone passage
Passage coordination with AIForbidden determines which visitors and equipment may enter the specific coordinated route. That arrangement does not override another zone’s rules or make an intelligence-enabled vehicle acceptable everywhere. Equipment routing and its permitted operation remain separate checks.