Known limitations
| Document version | Date | Summary |
|---|---|---|
| v1 | 2026-07-18 | Initial limitation register |
This file records unresolved limitations that affect implementation, verification, portability, or supported behaviour. Planned release exclusions belong in milestones rather than this file.
Each limitation must link to a PBI or a BUG that resolves, evaluates, or explicitly accepts it. Identifiers are permanent and are not reused.
| ID | Area | Limitation | Impact | Tracking | Status |
|---|---|---|---|---|---|
LIM-001 | Windows | The MSVC and Windows Clang configurations have not been executed on Windows | Windows remains portable by design rather than build tested | PBI-013, PBI-030 | Open |
LIM-002 | Verification | The symbol scan does not parse MSVC dumpbin output and Valgrind does not run on Windows, so neither the Core boundary nor the runtime allocation check can execute there. The header check is toolchain neutral but has not been run on Windows | The three automated boundary checks produce evidence for Linux only. They are recorded as unavailable rather than passing, and do not block v0.1.0 because Windows is not a required environment | PBI-030, PBI-031, PBI-032 | Open |
LIM-003 | Verification | Nothing enforces that tools/verify/alloc_probe.c exercises every public operation, so an operation added later can go unmeasured by the runtime allocation check | The allocation evidence can silently narrow as the public surface grows | PBI-032 | Open |
Add a limitation when work deliberately leaves a relevant constraint unresolved. Close it only when the linked evidence or decision exists.