SIMULATION LAYER 01 / 05
Questions, answered at the level they were asked.
Where an answer is "not yet", it says not yet.
SIMULATION LAYER 02 / 05
The product
What it does, and what it refuses to do
Is this a forecasting tool or a reporting tool?
Both, kept visibly apart. Recorded figures are reporting: arithmetic on documents you supplied. Projected figures are simulation: a range over the next three quarters, labelled with the method that produced it. They never merge into one number, and they never share a colour.
Why a range instead of a number?
Because a single number is read as a commitment. Three quarters out, on a handful of quarters of history, the honest output is a band with its error on the holdout printed beside it. If you want a point to plan against, take the p50 knowing what the p10 and p90 are.
Why are some panels empty?
Because the document that would support them has not arrived. Each empty panel states the reason and names what would unlock it. Filling the gap with an industry average would look identical to a real reading and there would be no way to tell them apart later.
Can you benchmark us against our industry?
Not from your ledger. A benchmark requires a comparable population measured the same way; anything else is a number with a confident label. If we ever ship benchmarks, the population and the method will be stated on the panel.
What happens when the model cannot answer?
It abstains. Every figure in a written answer is checked against its grounding before you see it, substitution included; on failure the answer is regenerated once and then withheld with a reason.
SIMULATION LAYER 03 / 05
Your data
What you send, and what happens to it
What do you need from us to start?
One accounting export. A trial balance makes Finance real and computes inventory cover. Beyond that: a purchase register unlocks vendor concentration, a purchase-order register with receipts unlocks lead time, a filing calendar unlocks compliance, a CRM export unlocks the pipeline panels.
Does it need to be clean?
No — the opposite. Header on row seven, subtotals in the middle, bracketed negatives, lakh grouping and a scale note buried in a title cell are the cases the parser is built for. A cleaned-up file tells us less than a real one.
Can we send it anonymised?
Yes, and for a first conversation we would prefer it. The shape is what matters, not the values. Replace names and scale the numbers; keep the layout, the notation and the calendar exactly as they are.
Will it write to our accounting system?
No. The connector layer verifies that a credential cannot write and refuses to save it if it can. Read-only is checked when the credential is stored, not asserted in a document.
Does a language model see our ledger?
Extraction and calculation are ordinary code, not model inference. One narrow module bridges to the forecasting engine and every import inside it is function-local, so the list of places a model can be involved is short and reviewable.
SIMULATION LAYER 04 / 05
Status and access
Where this actually is
Can I use it today?
No. Phase 0 is complete: the repository boots, the vendored engine is reachable, the first migration applies and reverses, the frontend builds, and every CI gate is green and blocking. The dashboard, the setup wizard, projections, the Ask bar and connectors are not built.
What is a design partner expected to do?
Send three to five real, messy exports — anonymised is fine — and answer questions about which sections you actually hold data for. In exchange the first working sections get built against your shapes rather than invented ones.
What does it cost?
There is no price, because there is nothing to sell yet. The wider GodEngine web platform is live and currently free to all users, with billing deliberately switched off. When pricing exists it will be published rather than quoted case by case.
Why does the product have three different names in your own material?
It did, and that is a real defect we are fixing rather than explaining away. The name used here is Business Intelligence Simulator by GodEngine — written in full, never abbreviated.
How many people are behind it?
One founder, and effectively a single-author codebase. Stated plainly because it is checkable and because it is relevant to anyone deciding whether to depend on this.
SIMULATION LAYER 05 / 05
Something not answered here?
Ask it directly. If the answer is “we do not know yet”, that is what you will get.