What GodEngine will not do

It does not give advice

In everyday use

GodEngine reports support your own judgement. They are not professional, financial, investment or legal advice. Examples on our pages about markets, funding or investment use made-up companies, and a report is never a substitute for a qualified person who knows your situation.

It does not claim to predict the future

We do not say GodEngine predicts what will happen, and these pages publish no accuracy percentages for it. Scenarios describe how a decision could play out under stated assumptions. If a forecasting track record ever appears on our pages, it will be computed from resolved forecasts and dated.

Rules of the system we are building

Proposed

The following rules belong to the architecture described in the open notes. They are designs, not shipped behaviour, and we list them here so that the product can be held to them as it grows.

• It will not present an uncalibrated score as a probability. Without calibration, the output is a comparison of scenarios with explicit assumptions.
• It will not act on a recommendation. Asking “should we do this?” never implies permission to send, spend, deploy or delete. The internal decision service already marks every record it writes as not authorised.
• It will not execute free-form text. A recommendation written in prose has to become an explicit plan with named operations before anything can run.
• It will not fabricate a plan. If no valid planner is available, it stops and names the missing capability.
• It will not route around a safety check. If a required policy check or verifier is unavailable, the operation that needs it is blocked. There is no direct fallback.
• It will not take narration as proof. A model saying an action happened is not evidence that it did. Verification uses observable state or deterministic checks wherever they exist.
• It will not pretend effects are reversible. Some actions cannot be undone: an email sent or a trade executed is not reversed by a journal entry. If a provider times out after accepting a write, the effect is marked unknown until it is reconciled, and automatic retries stop.
• It will not pool private data across customers. Shared improvements are abstracted procedures, never raw conversations or private documents, and anonymisation alone is not taken as proof of safety.
• It will not give a model reusable production credentials in its prompt.

It does not learn from your questions without consent

Built, switched off

As of our design note of 22 August 2026, no training data had been collected from users and no model had been fine-tuned. A capture mechanism exists for the day we might, and it is off by default.

Its rules are deliberately conservative. Production traffic is ineligible unless there is a declared consent basis. Output produced by outside AI providers goes to legal review, because provider terms often restrict training on it. The only data the design treats as eligible is data we generate ourselves, the output of a model running on our own machines over our own prompts, and human annotation produced under contract. Every candidate record would carry its source, consent basis, redaction state and a fingerprint, so that a deletion request can reach any dataset built from it.

Note We do not plan to train a foundation model. Independence from any single AI provider comes from routing each stage to models we can control, not from producing our own weights.

Where data sits

Partly built

For now, GodEngine runs on our server in the USA. We plan to host it in India (Navi Mumbai) before a full launch. Each stage of the engine can be routed to a self-hosted model instead of an outside provider; that option is partly built.

How we describe the work

These are the editorial rules every page of these notes follows, this one included.

• No invented numbers, customers, testimonials, ratings, awards or press.
• No counts of agents, models or simulations used as a selling point.
• No “real-time”, “secure by design” or “enterprise-ready” unless it is true and can be shown.
• Examples are labelled when they are made up.
• Status words follow the four marks, and every page carries the date it was last checked.

Known weaknesses today

Checked 5 October 2026. We will remove an item only when it is fixed.