Repository navigation
docs: explain corridor benefits and traffic signal operating modes - #63
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Explain the dual value of emergency corridor coordination: faster emergency response and proactive management of general traffic to reduce downstream blocking. Update the bilingual /docs About section and add dedicated Traffic Signal Operating Modes cards to Architecture; mirror the overview and phases in README.
Separate intended queue flushing / gradual stabilization from current PoC behavior: CLEARING retains ordinary route phases, and RECOVERY resumes the ordinary cycle immediately. The simulation does not model queue discharge, gradual offset restoration, or guarantee uninterrupted passage.
Verification
Contract or safety impact
Documentation and documentation checks only. No runtime simulation, API contract, signal timings, or dependencies changed. Operational intent is explicitly distinguished from implemented simulation behavior.
Follow-ups
Queue dynamics and gradual cycle/offset recovery remain future implementation and calibration work.