PROPOSED REVISION · 22 NOV 2026Architecture intent, not a claim of implementation or conformance. The original stack is retained; contracts below refine its guarantees.
Build · Model · Draw · Simulate · Manufacture · ExploreGeometry drives a more capable world.

Applications

PartManagerRecursive3DModelViewerPrintViewerUniverse games

Pick the card. Draw nothing.

Hosts

Windows (our own window)WinForms (the Form only)Browser (WebGPU)X11 · Wayland · Cocoa

A window and its input. Presentation and input adaptation only.

Surface

ControlsLayoutInput · focusDockingICanvas → Raster, Text

Our UI. A caller of the engines like any other.

▼ meaning: a model, names, a styleanswers: a pick, a face name, a crossing ▲

The rule at the centresource · compile · keep · execute

SourceThe truth. One owner defines it.
Compiled on changeA private fast form, made when a dependency changes.
KeptWith an owner, lifetime and dependencies: source, style parts, view, device.
ExecutedFrames consume published forms. A compatible fallback or explicit failure preserves source truth.
2D VectorPath → RasterPath, cut boxes → words on the cardText text + format → layout, fitted glyph → glyph words3D B-rep → mesh, edges → Space's buffersField tree → tape words → one card program
Domains · truth: meaningeach keeps its own model, rules and names

CAD

KernelSketchFeaturesAssemblyMotion studySTEP · X_T · IGES · .rcad

Parametric, exact, named.

TO BUILD

Vector

Free documentsUndoSVG and DXF in and out

2D work with no other home.

Documents

PDFSVGImagingPrint readerOCRPMIRecreate

From files to understanding.

CAM

G-codeToolpathsStockTooling

From model to machine.

Universe

WorldPhysicsAnimationAudio

Real-time worlds.

Engines · behavior and drawingeach the one place its work is done; private forms, made on change

Geometry

Construct and interact

TrimExtendFilletRegionsPickSnapGripMeasure

Answers to the host, with sources and guarantees. Draws nothing. Recompute only for declared interaction or model changes.

Raster

2D drawing

FillsStrokesDashesClipsGradientsEffectsPDF and SVG writers

Keep by path. View transforms reuse retained forms while declared quality and visibility limits hold.

Text

The text engine

Unicode 18ShapingLayoutHintingGlyph functionsAtlas

Its own fast path. Outlines at the edge, as Field2D.

Space

3D drawing, Scene above it

SceneCameraPickingMeshesEdgesRaysNo-card painter

Draws 3D. Draws what CAD hands it.

▼ stands on Field2D▼ stands on Field2D▼ outlines as Field2D(no field of its own)
Field · truth: mathematicsone architecture in two dimensions; field evaluates, the engines draw
REFERENCES

Field2D

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.

The tape

One card program for every field

2D and 3DSPIR-V · HLSL · WGSL · MSL · capability checks

Field evaluates. The engines draw.

Cad.Field

SICAD: the 3D field kernel

TreesOwners and namesExact faces back

CAD and Physics stand on it.

Executionknows the least; a lost card loses only card resources

GPU

One device API and shader model; four backend targets.

VulkanDirect3D 12WebGPUMetalBindings and backend capability contracts

Engines name no card; the app picks it.

Threads

One runner for the cores

Own parked threadsNo wait on the caller's thread

HELDEach implementation is checked against a declared specification and reference. Mathematical exactness, topology guarantees and byte reproducibility are separate claims. Bounds are checked in their stated metric; independent oracles and adversarial cases challenge shared mistakes.

The contracts

What every kept form, answer and approximation keeps.

Invalidation

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.
Device generation

A lost card throws away card resources only.

Geometry, layouts and models survive and compile to the new device.
Accuracy

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.
Provenance

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.

Derived state

Lifetime, revision ordering, recovery, persistence and observable reuse.

Resource ownership

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.
Concurrency

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.
Failure and fallback

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.
Persistence boundary

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.
Identity and revision

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.
Observability

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.

Boundary contracts

What makes the shared foundation safe across domains and devices.

Numerical meaning

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.
Composed accuracy

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.
Topological identity

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.
View and quality

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.
Memory and scheduling

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.
Implementation scope

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.

The paths

From source to result. One authoritative owner per step; explicit contracts between steps.

P1

2D drawing

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

P2

Text

Text → shape → glyphs → Raster.Gpu

Functions by default, atlas as legacy. An outline leaves only when asked.

Guard: ordinary glyphs never through Geometry

P3

SVG

File → Svg → P1 → target

To the SVG spec. Paths kept, made when the document changes.

Guard: unchanged paths never rebuilt

P4

PDF

File → Pdf → P1 → target

Read and shown, or made with true curves, weights and dashes. Fonts through Text.

Guard: strokes reach Raster as strokes

P5

Print reader and PMI

PDF · image → Sheet → OCR → PMI

Read, map, balloon, recreate. Its calibrated pixels stay its own.

Guard: calibrated pixels never through Geometry

P6

Construct and interact

Model → Geometry → answer

The host applies the answer to its own model. Shown by P1.

Guard: no unconditional frame rebuild; glyph rendering stays independent

P7

3D model

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

P8

Implicit solid

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

P9

CAM and PartManager

Part → toolpath → stock → backplot

Routing tree, tools from the database, mated, drawn by Space.

Guard: drawing types are not business truth

P10

Universe

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

P11

Motion study

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

P12

Window and controls

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

P13

Execution

Engines → Recursive.Gpu → backend

Work over the cores through Threads.

Guard: no API name in engine code

The laws

Thirty-two rules in five groups. Original numbers retained.

Ownership and subsystem boundaries

Laws 1–8 · Who owns meaning and how the engines remain independent.

1One ownerAuthority is singular; implementations and independent verification may be plural.
2One curve languageField2D's Piece, Loop and VectorPath.
3One question, many waysDefined once; ways switched and probed.
4Models stay homeEach domain keeps its meaning.
5Meaning down, answers upHosts give models; engines give answers.
6Geometry draws nothingThe host applies its answers.
7One drawing pathGeneral 2D reaches Raster as geometry plus style.
8Specialized engines remainText and Space keep their roads.

Correctness specialization and evolution

Laws 9–15 · How derived forms preserve source truth and implementations change without losing their guarantees.

9Compile, retain, invalidateReuse while dependencies, quality and residency remain valid.
10Exact until forcedState the exact quantity or approximation metric; compose error budgets explicitly.
11Provenance survivesLineage is preserved; split, merge and ambiguous identity outcomes are explicit.
12Output owns no geometryScreens and files are destinations.
13Execution knows the leastThe card learns no CAD, document or UI.
14Legacy is a wayReplaced beside; retired on Trevor's word.
15Proof follows specializationA fast way names what it preserves.

Standards performance and verification

Laws 16–18 · How conformance correctness and speed are judged.

16The standard is the truthDeclare applicable specification versions, subsets and deviations; use independent checks.
17The race is the whole frameLike for like, four situations.
18Tests sized to the changeThe smallest check that proves it.

Derived state and operational accountability

Laws 19–24 · Who owns compiled resources and how publication failure persistence validity and reuse behave.

19Derived state has an ownerCompiled forms own their resources and lifetime.
20Publish complete statePublish complete current snapshots; reject stale completions and retire safely.
21Failure does not change truthA compatible fallback or explicit failure preserves the requested contract.
22Compiled is not persistent truthExecution artifacts are reproducible unless explicitly versioned as cache data.
23Validity is deterministicComplete dependency keys decide validity; residency decides availability.
24Reuse is observableDiagnostics name retained, rebuilt, invalidated and fallback work.

Boundary contracts and acceptance evidence

Laws 25–32 · What numerical resource and implementation guarantees must travel across subsystem boundaries.

25Numerical meaning travelsUnits, frames, transforms and tolerance metrics cross boundaries explicitly.
26Error budgets composeAccount for upstream and local error before accepting a final guarantee.
27Identity has outcomesSplits, merges, deletion and ambiguity use declared rebinding rules.
28Views have validity envelopesRefine only when view, coverage or quality dependencies require it.
29Memory is boundedBudget caches, queues and in-flight work; cancel and evict safely.
30Determinism has a scopeState whether ordering, numeric results or bytes must repeat, and on which targets.
31Implementation is a tradeoffJustify internal work and dependencies against ownership, cost and conformance.
32Evidence qualifies claimsRepresentative correctness, latency and memory results support each guarantee.

Mending, in order

For each migration: declare the guarantee, establish an independent check, switch callers, measure representative workloads, then retire by the agreed policy.

The one stroke in Field2D, the card's widening held to it
The one crossing in Field2D
SVG keeps its paths
PDF hands Raster strokes as strokes
The product on the new pipeline, controls first
Invalidation declared in every kept form
Provenance as Geometry's result
One promise vocabulary
Guards checked by the build
Ownership and concurrency declared for kept forms
Compatible fallback, explicit failure and persistence boundaries declared
Revision races, identity cases, memory budgets and view refinement verified

Complete when

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 it
ALL-8One owner and one Reference for every shared question
ALL-9Geometry serves sketch, drawing and Vector knowing none of their models
ALL-10Raster resends only what changed
ALL-11Text hands out outlines only when asked
ALL-12Space apart from Raster; overlays by P1
ALL-13Every approximation states its tolerance and whose it is
ALL-14Construction keeps provenance
ALL-15Forbidden references fail the build
ALL-16Every retirement comes with its specification, independent checks and representative measurements
ADDEvery kept form has one resource owner; stale completion and in-flight reclamation cases are verified
ADDFailure uses a contract-compatible fallback or returns an explicit failure without changing source truth
ADDCompiled artifacts stay outside persistent truth unless explicitly versioned as cache data
ADDDiagnostics prove retention, dependency closure, eviction, stale rejection, rebuild and fallback or failure decisions

Prove it in use

Acceptance scenarios to agree and measure; no results are claimed here.

Correctness

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.
Lifecycle and recovery

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.
Whole workflow

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.