CAD
KernelSketchFeaturesAssemblyMotion studySTEP · X_T · IGES · .rcad
Parametric, exact, named.
Pick the card. Draw nothing.
A window and its input. Presentation and input adaptation only.
Our UI. A caller of the engines like any other.
KernelSketchFeaturesAssemblyMotion studySTEP · X_T · IGES · .rcad
Parametric, exact, named.
Free documentsUndoSVG and DXF in and out
2D work with no other home.
PDFSVGImagingPrint readerOCRPMIRecreate
From files to understanding.
G-codeToolpathsStockTooling
From model to machine.
WorldPhysicsAnimationAudio
Real-time worlds.
Construct and interact
TrimExtendFilletRegionsPickSnapGripMeasure
Answers to the host, with sources and guarantees. Draws nothing. Recompute only for declared interaction or model changes.
2D drawing
FillsStrokesDashesClipsGradientsEffectsPDF and SVG writers
Keep by path. View transforms reuse retained forms while declared quality and visibility limits hold.
The text engine
Unicode 18ShapingLayoutHintingGlyph functionsAtlas
Its own fast path. Outlines at the edge, as Field2D.
3D drawing, Scene above it
SceneCameraPickingMeshesEdgesRaysNo-card painter
Draws 3D. Draws what CAD hands it.
The one 2D curve, and the maths every engine needs once
Piece · Loop · VectorPathCoverageWindingDistanceThe exact edgeLengthOffsetThe one strokeThe one crossingDXF
Exact, Bound or Sign: every result defines its guarantee, scope, units and assumptions.
One card program for every field
2D and 3DSPIR-V · HLSL · WGSL · MSL · capability checks
Field evaluates. The engines draw.
SICAD: the 3D field kernel
TreesOwners and namesExact faces back
CAD and Physics stand on it.
One device API and shader model; four backend targets.
VulkanDirect3D 12WebGPUMetalBindings and backend capability contracts
Engines name no card; the app picks it.
One runner for the cores
Own parked threadsNo wait on the caller's thread
What every kept form, answer and approximation keeps.
Every kept form declares source, style, view, quality and device dependencies. Rebuild only the affected work; explicit eviction may also require reconstruction.
Colour changes preserve geometry. A pan stays a matrix while coverage and quality remain valid. A drag updates its declared dependency closure.A lost card throws away card resources only.
Geometry, layouts and models survive and compile to the new device.Every answer defines Exact, Bound or Sign for a named quantity, representation and domain of validity.
Exact states what is exact; Bound states a metric, units and enclosure; Sign states behavior at zero and uncertainty. Byte reproducibility is a separate guarantee.A derived result names sources, revisions, parameter ranges, coordinate frames and guarantees.
Lineage supports rebinding. Splits, merges, deletion and ambiguity have explicit outcomes; identity is never silently guessed.Lifetime, revision ordering, recovery, persistence and observable reuse.
Every compiled form has one owner responsible for CPU memory, card resources, pooled scratch and reclamation.
A compiled form owns its resources; borrowed data has an explicit lifetime. Reclamation waits for CPU readers and GPU completion.Readers see complete immutable snapshots. A compilation publishes only if its captured dependency revisions are still current; stale completions are discarded.
Compile privately; publish atomically against a revision token; pin readers and in-flight device work; retire after completion. State the required determinism scope.A failed optimized way preserves source truth. Use a fallback only if it meets the requested semantics, accuracy and permitted resource limits.
If none qualifies, return an explicit unsupported, cancelled, resource-limit or failed result. Record the cause; never label stale output as current.Compiled forms are reproducible artifacts, not document truth, unless a format explicitly defines a versioned cache section.
RasterPath, glyph words, meshes and GPU buffers are normally rebuilt from source.Validity uses a complete dependency key: source identities and revisions, relevant options, quality, compiler version, and view or device generation where applicable.
Matching keys permit reuse if the artifact is resident and valid. Changed dependencies trigger their closure; dependency cycles need an explicit solver boundary.Diagnostics report dependency keys, publication tokens, selected way, reuse, rebuild, stale completion, eviction, memory, build cost and fallback or failure reason.
RETAINED is provable; EDIT identifies affected work. Profiling includes frame latency, allocations, upload volume and peak retained memory.What makes the shared foundation safe across domains and devices.
Units, coordinate frames, handedness, scale and transforms are explicit at every geometric boundary.
Separate model-space, world-space and pixel-space tolerance. Large coordinates, singular transforms and degenerate input have defined outcomes.Each stage accounts for inherited and introduced error in a declared metric. The final result must meet the consumer’s total budget.
A local bound is not automatically an end-to-end bound. If a stage cannot propagate a valid guarantee, return uncertainty or failure.Persistent entity identity is distinct from source lineage, revision and render identifiers.
Split: name descendants. Merge: preserve ancestry. Deletion: mark missing. Ambiguity: request resolution or leave unresolved; never silently reattach.Retained representations declare the scale, coverage, visibility and quality assumptions under which they remain valid.
Transforms reuse data inside that envelope. Crossing it permits targeted tessellation, visibility work or refinement; keep source geometry intact.Caches have CPU and GPU budgets, eviction policies and in-flight limits. Interactive work has priorities, cancellation and backpressure.
Eviction releases derived state safely; visible work can be rebuilt. Define overload behavior and avoid unbounded compilation queues.Own semantic contracts. Choose internal implementations or isolated dependencies using measured value, conformance, maintenance and delivery cost.
Record owner, supported subset, dependency policy, staffing and exit strategy. A package ban is a product constraint to justify, not proof of architectural quality.From source to result. One authoritative owner per step; explicit contracts between steps.
Model → Field2D + style → Raster → target
Curves stay curves. Strokes and dashes arrive as style. Screen, memory, PDF, SVG.
Guard: strokes retain style; no unchanged source rebuilt without a declared reason
Text → shape → glyphs → Raster.Gpu
Functions by default, atlas as legacy. An outline leaves only when asked.
Guard: ordinary glyphs never through Geometry
File → Svg → P1 → target
To the SVG spec. Paths kept, made when the document changes.
Guard: unchanged paths never rebuilt
File → Pdf → P1 → target
Read and shown, or made with true curves, weights and dashes. Fonts through Text.
Guard: strokes reach Raster as strokes
PDF · image → Sheet → OCR → PMI
Read, map, balloon, recreate. Its calibrated pixels stay its own.
Guard: calibrated pixels never through Geometry
Model → Geometry → answer
The host applies the answer to its own model. Shown by P1.
Guard: no unconditional frame rebuild; glyph rendering stays independent
File → Kernel → triangles → Scene → Space
Render packets carry meshes, edges, transforms and source identity. A pick resolves against the matching model revision.
Guard: a mesh is derived; stale or ambiguous picks cannot silently bind
Sketch → Cad.Field → tape → GPU
Faces where representable under the declared guarantee; otherwise bounded triangles, field evaluation or explicit unsupported output.
Guard: Field is not the drawing engine
Part → toolpath → stock → backplot
Routing tree, tools from the database, mated, drawn by Space.
Guard: drawing types are not business truth
World → step → one bridge → Space
A fixed simulation step publishes snapshots; frames interpolate them. Physics and Animation never see Space.
Guard: Physics and Animation never defined by Space
Assembly + keyframes → mates → Space
Solve mates on simulation ticks or dependency changes; publish poses for display. Save assembly constraints and authored motion in .rcad.
Guard: display state is not the assembly
App → host → Surface → ICanvas
The card, or the painter with no card. The 3D view and print kept apart.
Guard: no platform name in an engine
Engines → Recursive.Gpu → backend
Work over the cores through Threads.
Guard: no API name in engine code
Thirty-two rules in five groups. Original numbers retained.
Laws 1–8 · Who owns meaning and how the engines remain independent.
Laws 9–15 · How derived forms preserve source truth and implementations change without losing their guarantees.
Laws 16–18 · How conformance correctness and speed are judged.
Laws 19–24 · Who owns compiled resources and how publication failure persistence validity and reuse behave.
Laws 25–32 · What numerical resource and implementation guarantees must travel across subsystem boundaries.
For each migration: declare the guarantee, establish an independent check, switch callers, measure representative workloads, then retire by the agreed policy.
Acceptance requires evidence. Thresholds and supported scope are agreed before a capability is called complete.
ALL-7Every 2D curve between subsystems is Field2D or named as compiled from itALL-8One owner and one Reference for every shared questionALL-9Geometry serves sketch, drawing and Vector knowing none of their modelsALL-10Raster resends only what changedALL-11Text hands out outlines only when askedALL-12Space apart from Raster; overlays by P1ALL-13Every approximation states its tolerance and whose it isALL-14Construction keeps provenanceALL-15Forbidden references fail the buildALL-16Every retirement comes with its specification, independent checks and representative measurementsADDEvery kept form has one resource owner; stale completion and in-flight reclamation cases are verifiedADDFailure uses a contract-compatible fallback or returns an explicit failure without changing source truthADDCompiled artifacts stay outside persistent truth unless explicitly versioned as cache dataADDDiagnostics prove retention, dependency closure, eviction, stale rejection, rebuild and fallback or failure decisionsAcceptance scenarios to agree and measure; no results are claimed here.
Degenerate curves, extreme scales, transformed bounds, split and merged faces, ambiguous selection and unsupported export.
Compare with declared guarantees, independent oracles and adversarial or metamorphic checks. Record supported specification versions and subsets.Rapid edits with reversed compile completion, cancellation during work, device loss, allocation failure and cache eviction under load.
Verify current snapshots, safe CPU/GPU reclamation, preserved documents and explicit failure when no fallback qualifies.Cold open, retained idle frame, local edit and view or quality change across representative CAD, text, document and simulation workloads.
Agree scene sizes and targets per device: p50/p95 frame latency, input-to-visible latency, rebuild time, uploads and peak CPU/GPU memory. Report unsupported features too.