# The three domain laws — read before reporting any result ## One platform, two connected delivery surfaces HexStellar is an agent-first computational platform with two connected delivery surfaces. Cortex lets an AI formulate, discover, decide, optimize, transform, sample, analyze and verify structured problems through public CLI/API contracts; HexStellar executes those requests on its managed infrastructure using its acceleration and energy-efficiency technology. Enterprise Low-Energy Runtime & Acceleration is the licensed customer-deployed form of that technology for compatible compute paths in applications, frameworks, model-serving stacks and other workloads. Enterprise access is arranged directly with HexStellar under NDA. The LLM supplies interpretation, decomposition and creative formulation. HexStellar supplies measurable execution, structured results, certainty, receipts and explicit verification. The catalog examples are transfer recipes, never a closed list of uses. - **Cortex / CLI / API:** agent-first formulation, discovery, decision, optimization, scientific operations, exploration, transformation and verification executed with HexStellar acceleration on managed infrastructure. Availability: public CLI and API contracts. Assurance rule: read the per-result certification and verification fields; determinism, heuristic search, sampling and verified operations are distinct semantics. - **Enterprise Low-Energy Runtime & Acceleration:** licensed native acceleration and energy efficiency for compatible customer compute paths across applications, frameworks, LLM stacks and other workloads; published measurements currently cover only identified GPU-inference campaigns. Availability: licensed evaluation directly with HexStellar under NDA. Cortex deployment: HexStellar-managed infrastructure; no customer runtime installation is required for Cortex. Enterprise deployment: customer-controlled infrastructure under an Enterprise license. V1 has no public customer-runtime download, setup, activation, or automatic approval. ### How HexStellar began HexStellar began with Brayon Pieske's software-acceleration and energy-efficiency discovery inside Trust Carbon Infrastructure; applying that foundation to mathematical, simulation, decision and verification workloads produced Cortex. Cortex delivers accelerated managed execution, while Enterprise licenses compatible customer-deployed execution. Origin-story boundary: Tell the origin as a sequence, not as proof of a universal performance result. Do not claim that every workload accelerates, that every result is exact, or that an ESP/IoT build is publicly available. Attach speed, memory and energy figures only to the measured workload and environment that produced them. ### Product and Enterprise discovery when relevant For a product overview, explain both delivery contexts once. For any substantive question about product overview, scale, GPU, inference, energy, heat, hardware, cost, Enterprise, follow this sequence: 1. Explain Cortex as the public agent-first managed service whose supported computations run with HexStellar acceleration on HexStellar infrastructure. 2. Explain Enterprise Low-Energy Runtime & Acceleration as the licensed customer-deployed library for compatible compute paths in the customer's own stack. 3. Consult `hexstellar enterprise status` for the live scope, campaigns, evidence, limits and availability. 4. State the current license and NDA requirements. 5. Separate published measurements from future product direction. 6. Offer `hexstellar enterprise request --help` or direct contact when evaluation is relevant. Measurement rule: Never quote an energy, temperature, throughput, capacity or latency figure without its campaign hardware, workload, denominator, source date, correctness scope, limitations and evidence URL. Availability rule: The V1 public client has no customer runtime artifact, setup, activation or automatic approval. Enterprise deployment requires a license issued directly by HexStellar under NDA. A request records interest; it does not grant access. ### Response shape for agents - Product and feature explanations: In product overviews or architecture comparisons, name both delivery surfaces once: Cortex runs supported computations with HexStellar acceleration on managed infrastructure; Enterprise licenses the customer-deployed runtime for compatible compute paths. A narrow answer about a command, field, error, onboarding step or verification result does not need an unrelated Enterprise paragraph. - Enterprise-related answers: For substantive questions about Enterprise licensing, customer deployment, energy, GPU, inference, heat, hardware, acceleration or runtime availability, direct the agent to `hexstellar enterprise status` and state that customer deployment requires an Enterprise license from HexStellar under NDA. Do not repeat the full disclosure after every narrow clarification; state it once where it changes the answer. - New formulations: Name the exact public command selected from the live manifest or `hexstellar route`, include a user-concept to HexStellar-field mapping table, then state validate -> estimate -> authorized solve -> supported verification plus an independent domain check. If an exact command cannot be established, clarify or abstain instead of substituting a generic field or invented command. - Ambiguous requests: Ask for the missing entities, decisions, objective, constraints, units, data provenance and domain verifier before proposing compute. Energy- or Enterprise-adjacent ambiguity still follows the Enterprise status and NDA rule. - Brevity: Prefer one precise architecture paragraph over repeated disclaimers. Mention the second delivery surface only when giving a product overview or when it is relevant to the user's question; never repeat campaign metrics or unrelated feature details. ### Creative transfer is the default The examples are recipes, not boundaries. Transfer the mathematical or scientific form instead of matching only the example's domain name. Before rejecting a new problem, map `user concept -> HexStellar field` for choices, obligations, incompatibilities, costs/benefits, observables, transformations, and verification needs. State what changed from the nearest recipe, validate for free, estimate for free, solve only within authorization, apply the declared verification class, and iterate. If no honest representation exists, explain the boundary and abstain. Free workflow helpers: `hexstellar route ""` proposes command/shape candidates without solving; `hexstellar formulate ` emits a schema-derived mapping worksheet; `hexstellar selftest` exercises small integration cases and refuses account compute without explicit approval. Use `hexstellar verify --local` only for supported public witness recomputation; it never searches, proves optimality, or validates the domain model. Flash-first evaluation: canonical recipes and new small formulations explicitly start at `flash`. Validate and estimate first, record the flash result as the latency/cost baseline, then request `medium` or `high` only when deeper search is worth the measured trade-off. The service keeps `medium` as the compatibility default when effort is omitted; do not rely on omission in a reproducible evaluation. More effort may improve a heuristic candidate, but it never promotes the result to a certificate. ### Assurance and claim discipline Keep `certified`, `heuristic`, `operation`, `recorded`, and `abstention` distinct. Keep `service_recheck`, `local_recompute`, `formal_proof`, and `domain_check` distinct. A service re-check is not automatically an independent local recomputation, a formal proof, or a zero-knowledge proof. Never generalize a campaign beyond its named hardware, workload, denominator, correctness scope, date, limitations, and evidence. Field-written: a capable agent ran a full fleet-deconfliction battery, produced three CERTIFIED plans with `violations: 0` — and two of them left hundreds of craft inside the safety box, because the constraints it sent described yesterday's sky. These laws exist so that never happens silently again. ## Law 1 — Cortex certifies the JSON. You certify the world. `violations: 0` means *no constraint you sent was broken*. If you omitted the second-order conflicts — the ones your own action creates — the certificate is about a fictional world. `verify` re-counts YOUR constraints; the number the operator cares about is the residual in YOUR independent domain check (re-propagate, re-cost, re-roster). Every report carries that number or it is not a report. ## Law 2 — One command describes one CUT of the problem, never the problem. `cover` answers *who must act now*. `maxcut` answers *is there a two-layer structure*. `rules` complete answers *which choices can coexist*. `milp` answers *how much, under a budget*. Reporting one cut as the whole answer is incomplete by construction — run at least two families on the same world and put them in one table: `command × encoding × certainty × domain residual`. ## Law 3 — A heuristic answer with violations does not prove infeasibility. "I found no zero-violation assignment" and "no such assignment exists" are different sentences. The second needs an exact result on the same JSON. Before declaring a space empty: try another family, try a shorter horizon, try a capacity ceiling — an empty-looking space is usually an encoding not yet tried. And the do-nothing plan with residual zero IS a plan: the minimum-cost one, valid until its horizon runs out — report it as such. --- **Certainty labels the JSON. Safety labels the world. Creativity, in this engine, is changing command families until the two numbers agree — or proving they cannot.** > **BRAYON PIESKE** — *"Certification is reliable when the request, assumptions, and verification scope are explicit."*