Normative build package / qec-build-0.3

Quantum Etz Chaim build specification

The implementable contract for the deterministic Hebrew-letter engine, IvritOS orchestration, replayable evidence, Da’at observation, and Malchut output.

INTEGRATED PROTOTYPE23 REGISTERS22 INSTRUCTIONSEXCHANGE 0.2
01 / Build objective

One engine, two public experiences

IvritCode executes normalized Hebrew source over twenty-two visible base-22 registers plus Aleph Olam. Quantum Etz Chaim presents that same run through services, paths, gates, observation, and manifestation. IvritOS names the orchestration contract between purpose and output.

The register reducer is authoritative. Coherence, graphics, sound, and prose may describe completed state; they may never alter it.
02 / Deliverable boundary

Implemented software, bounded claims

In scope

  • NFC Hebrew input and final-form normalization.
  • Exactly 23 immutable bounded registers.
  • All 22 instructions and a versioned path map.
  • Replayable trace, observation, screen, sound, file, and export.
  • Shared contracts consumed by both sites.

Out of scope

  • Physical qubit control or quantum speed-up.
  • Generated-code execution or runtime network access.
  • Unrecorded permission or global-state mutation.
  • Symbolic language presented as scientific or religious proof.
03 / Package ownership

Canonical dependency direction

PackageOwnsMust not own
@ivritcode/coreRegister state, Hebrew operations, execution traceDOM, network, architectural prose
@qec/coreManifest, policy, verification, orchestrationAlternate letter transforms
@qec/specVersions, identifiers, exchange validationUI or runtime state
QEC adapterPaths, gates, observation and Malchut viewsA duplicate engine

Direction: UI → QEC orchestration → IvritCode engine → Unicode primitives.

04 / Normative state

Machine invariants

23

Registers

Indices 0–21 are visible; index 22 is Aleph Olam.

0–21

Bounds

Every value is an integer base-22 digit.

+1

Sequence

Each trace event advances exactly once.

0

UI mutation

Projection and rendering never change state.

Every beforeHash matches the preceding afterHash. Equal source, state, versions, seed, permissions, limits, and mode yield byte-identical canonical output.

05 / Atomic instruction

Ten accountable stages

01 Parse02 Authorize03 Context04 Path05 Services06 Transform07 Trace08 Project09 Observe10 Manifest

Any failure prevents partial state commit. Malchut remains locked until Da’at records a valid observation.

Open lifecycle plate →
06 / Cross-site exchange

Reproducible handoff

ivritcode-exchange-0.2 carries source, hashes, initial and final state, engine version, path-map version, seed, complete trace hash, manifestation version, returning letters, and gates.

Quantum Etz Chaim validates the envelope through @qec/spec. Unknown versions, invalid register counts, malformed payloads, and out-of-range values fail closed.

Build contract Trace schema Path map

07 / Safety limits

Bounded by construction

ResourceCeilingFailure
Source graphemes4,096E_SOURCE_LIMIT
Instructions1,024E_PROGRAM_LIMIT
Execution steps10,000E_STEP_LIMIT
Trace events50,000E_TRACE_LIMIT
Export5 MiBE_OUTPUT_LIMIT
RecursionDisabledE_RECURSION_DISABLED
08 / Release gates

Evidence required

CONTRACTSchemas + typesInvalid fixtures fail closed.
STATEBounds + immutabilityAll 23 registers remain valid.
PATHS22-route coverageEvery instruction resolves once.
DETERMINISMGolden replayEqual runs produce equal bytes.
TRACEHash continuityNo gaps or discontinuities.
SECURITYFail closedNo arbitrary code or I/O.
ACCESSIBILITYWCAG 2.2 AAKeyboard, contrast, reduced motion.
RESPONSIVE375–1440 pxNo inaccessible controls.
PUBLICATIONLink verificationEvery bundled target exists.
09 / Delivery status

What is built

PhaseOutputStatus
AtlasArchitecture and engineering platesComplete
Engine@ivritcode/core runtimeComplete
Contracts@qec/spec, schemas, exchange 0.2Complete
Orchestration@qec/core verification and policyIntegrated prototype
ConsolePrograms, traces, Da’at, MalchutComplete prototype
HardeningExpanded fuzzing and automated accessibilityNext
10 / Definition of done

A traceable machine, not an atmosphere

Kernel 0.3 is done when both experiences consume one versioned engine; all instructions resolve; execution is deterministic and bounded; every visual claim cites a trace event or explicit convention; exports validate; classical state is independent of visualization; and every verification gate runs in CI.

Inspect implementation Download Markdown