# 011 — Align Temporal Grammar and Documentation

- Area: `pkg/ucxl/address.go`, `pkg/ucxl/temporal.go`, docs
- Priority: Medium

## Background
Temporal grammar in code uses `*^`, `*~`, `*~N`, plus `~~N`/`^^N`. MASTER PLAN describes symbols like `#`, `~~`, `^^`, `~*`, `^*`. The mismatch causes confusion across modules and docs.

## Scope / Deliverables
- Decide on canonical temporal grammar and implement parser support and stringer consistently.
- Provide mapping/back-compat if needed (e.g., accept both but emit canonical form).
- Update UCXL docs in repo (and knowledge pack references) to match.

## Acceptance Criteria / Tests
- Parser accepts canonical forms; unit tests cover all temporal cases.
- String() emits canonical form; round-trip stable.

## Notes
- Coordinate with RUSTLE and Validator modules for cross-language parity.

