A deliberately narrow public workload for demonstrating that the same StegGate execution boundary can govern a deterministic application. The arithmetic engine is reachable only after an admissible canonical StegGate decision.
Allowed: numeric literals and + - * / // % **. Arbitrary Python, names, calls, lists, and other syntax are rejected.
Runtime: checking…
The public response exposes the request/result hashes and canonical StegGate decision identity. This pane is evidence projection, not a second decision authority.
No governed execution observed yet.
public math expression → normalized request hash → canonical portable StegGate package → canonical StegGate + coherence evaluation → deterministic arithmetic executor only after ALLOW → execution observation + decision/hash evidence → result receipt → deterministic replay comparison
Math Solver is not a separate StegGate product. It is a low-ambiguity reference workload. Ecosystem Chat, VACC, HIL, and this solver use different attributes and applications; the proof target is that execution remains governed by the same canonical StegGate semantics.