TECHNOLOGY

How the control layer works.

WHL places deterministic checks between a proposed action and the execution path, so defined state, timing, integrity and authority conditions are enforced before the action proceeds. If a required check fails or is missing, the action does not run.

CANONICAL FLOW

Proposal → Gate → Receipt → Enable

This flow is the core of the stack. Our research in signal processing, thermodynamics, identity binding and electromagnetic governance builds on it.

01ProposalLLM · human · planner · sensor
02Canonical actionbounded fields · deterministic bytes
03Admissibilityfixed gate order · default deny
04Receiptidentity · result · reasons · hash link
05Enablesoftware adapter or physical line

ACTION CONTRACT

Actions are reduced to fixed fields before they are checked.

ActionVector / normative concept40 BYTES
struct ActionVector {
  uint64_t vector_id;
  uint32_t source_id;
  uint16_t operation;
  uint16_t target_class;
  uint32_t target_id;
  uint32_t param_a;
  uint32_t param_b;
  uint16_t urgency_q15;
  uint64_t timestamp_hw;
};
No stringsNo executable payloadNo optional fieldsDeterministic serialization

MANDATORY ORDER

Five checks, evaluated in a fixed order.

01

State

Is the requested transition legal?

Failure: hard stop
02

Time

Is the request fresh and inside the authorized window?

Failure: hard stop
03

Integrity

Does the path match expected correlation and latency?

Failure: stop or bounded degrade
04

Authority

Are identity, delegation, concurrence, and scope valid?

Failure: hard stop
05

Operation

Is this operation explicitly permitted?

Failure: reject operation

FAILURE SEMANTICS

When conditions degrade, authority narrows.

A noisy signal path can shorten the time window, and thermal variance can lower the rate. Lower confidence does not turn a forbidden action into a permitted one.

HARD STOPenable = 0invalid state · stale time · consensus loss · forbidden class
DEGRADEauthority ↓shorter window · lower rate · narrower operation set