Contribute
Ship 0.3 without hiding its boundaries
What is complete, what remains release metadata, and what is explicitly out of scope.
- sheet
- 12 / 12
- rev
- v0.3
- sections
- 2
- compiled
- 2
01 / 0.3Primitive and rotation work is complete
Quarter-turn transforms, typed primitive families, polished qgate, semantic ports, bus-width checks, expanded UML relations, deterministic fuzzing, exact resource ceilings, and 100% core coverage are complete.
source:DC "DC" at (90, 130) #blue [type=voltage-dc]
inductor:LX "L" at (280, 130) #purple [orientation=down]
mux:MX "mux" at (520, 130) #amber [type=mux]
hadamard:HX "H" at (730, 130) #cyan
package:PKG "subsystem" at (860, 300) #slate [width=160 height=80]02 / GatePublication metadata remains pending
The 0.3 line documents releases 0.3.0 through the current 0.3.x patch; the newest release in the line is the deterministic fallback until npm publication confirms it. The timeline must replace the pending date and commit hash from registry/GitHub data after release. Phase 5 owns version changes, changelogs, README updates, tags, pushes, and npm publication authorization.
logic:OK "1" at (100, 130) #blue [type=high]
comparator:CMP "gate" at (350, 130) #amber
load:BZ "sounder" at (600, 130) #emerald [type=buzzer]
OK.out -> CMP.in1 #blue [digital line]
CMP.eq -> BZ.in #emerald [digital line]Known boundaries remain deliberate: no arbitrary-angle rotation, no browser font measurement, no unbounded plug-in renderer, and no silent scalar/bus coercion.