OSC BEL termination in v1
Platform spec ADR
OSC BEL termination in v1
Spec standingStandard
- Contracts and edge cases MUST/SHOULD rules for escape emission and supported sequence subsets.
- Design model ESC/CSI/OSC taxonomy and normative control-character tables for terminal output.
- Examples Representative escape composition and gated emission patterns.
- Flow and algorithm How escape bytes are composed, gated, and written to stdout.
- Verification and traceability Golden tests and source anchors for ANSI escape framing.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”OSC framing varies across terminals; v1 picks one terminator for golden tests.
Decision
Section titled “Decision”| Rule | Detail |
|---|---|
| Terminator | BEL (0x07) in v1 |
| ST | ESC termination is not required |
Consequences
Section titled “Consequences”OSC helpers emit BEL-terminated sequences only until a future ADR extends ST.
Verification anchors
Section titled “Verification anchors”AnsiEscapeTests.bd; Ansi.Osc sources.