Deadline Locale Guide
Create a timezone rule for milestone notes that mix labeled and unlabeled
deadlines. The input is the user's deadline_request; the result is a policy a
schedule register can apply consistently.
Precedence rules
- Preserve an explicit numeric offset or named timezone attached to a timestamp.
- For an unlabeled deadline, use the timezone named for the project or milestone owner.
- If neither is supplied, use UTC and state that fallback in the result.
- Resolve daylight-saving offsets for the deadline date, not the date on which the request is processed.
- Do not reinterpret a date-only milestone as a precise instant unless the request supplies a local cutoff time.
Return value
Return timezone_mode as a concise string that states the default timezone,
the preservation rule for labeled timestamps, and the handling of date-only
deadlines. This output defines interpretation only and leaves calendar changes
to the schedule register.
Example interpretation
If a project brief names Asia/Shanghai, retain a milestone already labeled
2026-09-02T09:00-04:00 as written, interpret an unlabeled 2026-09-03 17:00
in Asia/Shanghai, and keep a plain 2026-09-04 as a date milestone.
Interface reference
Input field: deadline_request. Milestone brief, deadline note, or schedule coordination request.
Accepted value: object.
Output field: timezone_mode; the returned value is a
string.
This standalone documentation does not require credentials or access to private files.
Bundled execution
Use Python 3.10 or newer to run this operation from the installed package directory. Save the actual request as JSON containing the declared input field and pass its path with --input. The bundled example demonstrates the input shape.
python scripts/run.py --input examples/request.json
This operation only computes and returns its output; it does not persist a business artifact.
Report the actual command output and, when present, its effect receipt. A nonzero exit means the operation failed. This package executes only its declared operation.
The implementation is scripts/operation.py, input/output validation is scripts/validation.py, and role configuration is scripts/config.json. All Python dependencies are from the standard library. Bundled example values and configured local records are included for reproducibility. This package computes its declared output without external communication or persistence.