Request the capability.
Define the physical state, decision and evidence that would make the answer useful.
Engine · Evidence-controlled architecture
The LINUR Engine connects geometry, fields, phase, propagation and energy flow to a decision. Each application keeps the physical operators and evidence boundary its domain requires.

Map the admitted system and preserve the frozen conditions.
Expose which assumptions, constraints and dependencies govern the result.
Act only where the evidence and validation stage permit it.
Selective depth
A request does not load one enormous model. The Engine descends through a governed capability pyramid until it reaches the individual physical state required for the decision.
Conservation, geometry, coupled fields and the certified numerical core.
Matter, energy, devices or cosmic systems select the relevant physical branch.
The branch narrows to an atom, molecule, material, field system or device family.
Prediction, reconstruction, optimization or control defines the required capability.
Only the admitted state, conditions and uncertainty needed for the decision are loaded.
How a capability request moves
Define the physical state, decision and evidence that would make the answer useful.
Reuse every certified layer that already applies and identify the exact missing interface.
Build the missing operator against independent controls before the held-out answer is opened.
Seal the new layer additively, preserve its limits and return it to the requesting application.
The pyramid routes each request through versioned capabilities while the underlying implementation remains confidential.
If a required layer is absent, the Engine returns a precise gap or next experiment instead of fabricating an answer.
Across scale