Regular workday
Can transit support a conventional workday?
A morning journey to work and a return home after the destination activity.
Public architecture explainer
How three journey agents turn transit signals into evidence.
This simplified view shows how representative journeys connect walking, waiting, transit and public vehicle reports. It explains the structure without exposing private controls or live run records.
Three controlled questions
Different daily needs remain separate.
The agents share a common evidence approach, but each tests a different transit need. They are representative scenarios, not simulated residents or a sample of Toronto riders.
Evening shift
Does the network remain useful outside office hours?
A later journey tests whether service still supports work and the trip home.
Essential trip
Can an essential destination be reached without excessive burden?
A shorter outing with a tighter walking limit tests access to a pharmacy.
Interactive relationship map
Follow the evidence, not a person.
Select a concept to see what it contributes and where its public interpretation must stop.
ControlsJourneyNetworkEvidence
Select a concept to inspect it.
Core concepts
The basic pieces of a journey record
Scenario
The approved question, purpose and broad journey boundary.
Journey run
One controlled attempt to complete a scenario on a service day.
Walking and transit legs
Mapped portions of the trip kept separate from live evidence.
Vehicle report
A recent public-feed report that may support a journey transition.
Evidence event
What was observed, estimated, modelled or unavailable at one step.
Policy boundary
The actions and public claims the experiment is not allowed to make.
One plain-language example
What supports a virtual boarding?
The experiment advances only when the journey plan and recent public transit evidence agree well enough under its private controls.
- 1A mapped stopThe journey plan identifies where the agent is waiting.
- 2A compatible serviceThe planned route and direction must serve that part of the journey.
- 3A recent vehicle reportThe shared transit check looks for supporting public-feed evidence.
- 4An evidence-labelled transitionThe result is recorded with its evidence type and limitation.
Evidence language
Not every part of the journey is known in the same way.
Observed
Reported directly by an approved public source.
Estimated
Calculated from mapped conditions or stated assumptions.
Modelled
Produced by a controlled scenario or decision rule.
Context
Helps explain a place or condition without proving an outcome.
Public by design
Enough detail to understand the experiment. Not enough to operate it.
This page is a static explainer. It does not connect to the private workspace or expose live agent records.
Shown here
- Representative questions
- Core concepts and relationships
- Evidence labels
- Public claim boundaries
Kept private
- Live journey records
- Operational matching rules
- Administrative controls
- Infrastructure and protected configuration
Controlled testing
Understand the design before entering the workspace.
This public explanation shows the journey-agent concepts and safeguards. Live records, operational rules and review controls remain inside the authenticated sandbox.