Part 1 · What a state contract is

A state contract is a small physics state machine that runs on your state machine. You declare the states it can be in (e.g. idle → watching → alert) and the transitions between them. Each transition carries a real operator — the verbatim equation of a physical law (NIST CODATA-bound, ≤0.1% precision) — and fires when a value crosses your threshold, or on a time trigger. The kernel evaluates it on the HulyaPulse heartbeat (1.287 Hz) and writes every fire to your tamper-evident entangled state.

Not a blockchain smart contract (no gas, no bytecode, financial-only). State-first, pulse-synchronised, physics-grade, chain-rooted.

Part 2 · The easy pipeline (4 steps)

1. Pick — describe it in ✦ Generate (the kernel architects it), pick a template by name (📚, 69 industry examples), or write JSON in ⌁ Expert. Always: preview → one-click deploy.
2. Set — your thresholds and (optionally) where it runs: this state machine, or your own server.
3. Deploy — it’s saved to your state machine and starts safe (paused-ready).
4. Manage — find every contract under 📁 Saved: open, edit, pause/resume, fire, or change hosting. This is your contracts’ home.

Part 3 · Where your contracts are saved (the files question)

Every contract you deploy is saved on your state machine and listed under 📁 Saved here (and in Workbench → step 7 · Files). Each deploy snapshots a version — roll back any time. Every fire is a row on your entangled-state chain, viewable in the chain observer.

Part 4 · Hosting elsewhere — run the compute on your own server

By default a contract’s compute runs on this state machine. You can instead point its execution at your own server (a signed webhook URL): the kernel sends each transition’s payload to your endpoint, your code computes, and the signed result is written back to your chain. The contract, its state, and its proof stay anchored to your state machine — you just host the work wherever you like. Set it per-contract under 📁 Saved → Hosting.

Part 5 · The shape of a contract (JSON, for Expert)

• name (required, 1–255), states object (one initial), transitions array of { from, to, operator, condition?, trigger? }.
• Triggers: recurring (every N Zeqonds), one_shot, on_event/on_events, on_aggregate.

Part 6 · Cost

Each fire is billed in credits (fuel); the compute mints a ZEQ envelope (80% to you on paid-funded). Heavier operators cost more.