Build status
What is built and what is not
Every capability this website mentions, marked built, partly built or not built. Where something is partly built, the row says which part. This page is the authoritative one: if any other page on this site implies more than this, this page is right.
RoadmapWhat it can and cannot tell you
Current as of version two. Neither plugin has run on a production WordPress install yet, and the section at the bottom says exactly what that means.
Built
Works today, end to end
Each row here is code that runs and can be exercised from the interface.
| Capability | State | What that means in practice |
|---|---|---|
| Extraction rules | Built | Rules read tables by their column headings and prose by the shapes numbers take in business writing. Every fact carries its source, chunk, quoted span and method. Runs every time, with no language model involved. |
| Knowledge graph | Built | Facts merged on normalised names with aliases kept, nodes for customers, suppliers, competitors, departments, products, salespeople and partners, with sizes and edges and importance as a share of the node type. |
| Nine agent classes | Built | Customers, competitors, suppliers, salespeople, executives, employees, investors, regulators and partners, generated for every twin with objectives, constraints, visibility, personality, relationships and history. |
| The simulation | Built | Monthly, arithmetic, seeded and reproducible, with Monte Carlo over the bands in your ledger. No network calls, no key required. |
| Adaptive management | Built | Executive agents acting when their own numbers cross a line, gated on authority, personality and a cooldown. Switchable per run. |
| Scenarios | Built | Fifteen templates and twenty four levers, or build your own combination. Each scenario runs against the same twin doing nothing, on the same seeds. |
| Sweeps | Built | One lever across a range with the whole Monte Carlo behind every point, returning a response curve with a best point. |
| Compare | Built | Up to six scenarios against one baseline on one set of seeds, in one table. |
| The brief | Built | Answer, path, mechanism with the agent that caused it, bad case, tripwires with months and thresholds, and the assumption list with defaults at the top. |
| Sensitivity | Built | Each load bearing assumption moved to its own low and high and re-run, so the ranking is measured rather than asserted. |
| Ask | Built | Answers from the graph, the ledger and the runs, with the rows that answered them. Works with no key, returning cited rows instead of prose. |
| The assumption ledger | Built | Every number with origin, band, confidence, source, chunk and quote. Editable and lockable, with band width scaling by origin and defaults widest. |
| The worked example | Built | Harborline Components, invented, with its files, its twin and the scenarios already set up on it. |
| The network | Built | A graph neural network trained on your own twin: twenty four inputs per node, two rounds of message passing, twelve hidden units, and three heads for risk, impact and structure. Labels come from running the engine with and without each sampled node, so it is trained on your own simulator rather than on anybody else's data. Seeded, so training twice gives the same weights. |
| Explanation chains | Built | Every assumption, metric, agent property and network score has a Why chain that ends at a quoted line in one of your files or at a plain statement that an industry default is being used. Network scores add integrated gradient attribution over the inputs and neighbour ablation over the relationships. |
| Readiness and file reports | Built | Every upload returns what it recognised, what it ignored and why, the facts produced and the assumptions settled. Readiness is scored overall and per area of the company, and the blockers table ranks the documents you have not sent by how much each would move an answer. |
| Plan gating | Built | Five plans, including a free tier, with limits on twins, files, runs, sweeps, replications, horizon and seats plus feature flags for the network, exports, the API and language model use. Resolved from Paid Memberships Pro or set by hand, enforced on every API route, metered per calendar month. |
| This website | Built | Every page held as structured content in the plugin rather than as editable posts, so it re-renders from source and cannot drift. |
Partly built
Works, with a condition attached
These are the rows that get oversold by other products. The condition is stated first.
| Capability | State | The condition |
|---|---|---|
| Reading PDFs | Partly built | A PDF with a text layer is read by decompressing its content streams and pulling the text operators out. A PDF that is a scan has no text to find, so the source is marked as needing text and you are told plainly, with a suggestion to paste the numbers or upload the spreadsheet behind it. There is no optical character recognition in the product. Heavily formatted PDFs can also come out with the reading order scrambled, so check the parse preview. |
| Reading Excel and Word files | Partly built | Both are read by unzipping the file, which requires the ZipArchive extension in PHP. It is present on most hosting and absent on some, and without it those files read as empty and say so. Excel reads the first six sheets, takes stored values rather than formulas, and handles merged cells and pivot layouts badly. |
| Language model extraction of prose | Partly built | It exists, it works, and it is optional. It only runs if a key is configured, only over chunks the rules produced nothing from, and is capped per pass. Everything it returns is marked as an estimate with a wider band. With no key, extraction is rules only, which is the intended floor rather than a broken state. |
| Brief rewriting and prose answers in Ask | Partly built | Same condition. With a key, the brief can be rewritten into flowing prose and Ask answers in paragraphs. Without one, the brief keeps every section in structured form and Ask returns the retrieved rows with a plain sentence saying what they are. |
Not built
Does not exist, and is not partly there
If one of these is what you need, this is not the product for you today. Some are on the roadmap, some are on the part of the roadmap headed probably not.
| Capability | State | What there is instead |
|---|---|---|
| Live data feeds | Not built | Nothing connects to an accounting system, a CRM or an ERP. Everything arrives as an uploaded file or pasted text, and a twin is a snapshot until you upload a newer file. |
| Scheduled re-runs against new actuals | Not built | Runs happen when you ask for one. Comparing what happened against what the model expected is manual, using the tripwires in the brief. |
| Workflow and process simulation | Not built | The engine models a company at the level of demand, capacity, cost and cash. It does not model queues, handoffs or process steps, and that is a different kind of simulation rather than a missing feature. |
| Per employee modelling | Not built | Employees are modelled as capacity and cost, by department. There is no named individual with their own attrition risk. |
| Learning from outcomes | Not built | The model does not improve from what actually happened at your company or anybody else's. Priors are fixed values in the source. The network added in version two is trained on the engine's own answers about your twin, on your own server, and nothing about your company trains anything anybody else uses. That is deliberate and permanent. |
| Scoped API tokens | Not built | There is a REST namespace the application uses, available on Boardroom and Enterprise, authenticated as a signed in WordPress user. There are no scoped machine tokens, so driving this from another system means holding a user session. |
| Mobile apps | Not built | The interface is responsive and readable on a phone. There is no native application for any platform. |
| Optical character recognition | Not built | Scanned documents are refused with an explanation rather than guessed at. |
| Multi entity or group twins | Not built | A group is several separate twins, with no shared overhead, transfer pricing or cross entity effects between them. |
| Any certification | Not built | No SOC 2, no ISO 27001, no penetration test. The security page says what would change that and in what order. |
The honest part
Neither plugin has run on a production WordPress install yet
Everything above has been built and exercised in development. Neither the application nor this website has been installed on a live production WordPress with real traffic, a real database and a real payment gateway. That is a meaningful difference and it would be wrong to leave it implied.
Two things in particular are genuinely unknown, and they are unknown in the specific way that only a real install resolves.
- Table creation against a particular MySQL. The plugins create their tables through the standard WordPress schema helper, which is famously sensitive to whitespace, index definitions, storage engines and collations. It works here. Whether it produces exactly the intended schema on a given host, MySQL version or MariaDB build is the kind of thing you find out on the first install.
- The payment wiring. Plans resolve from Paid Memberships Pro levels through a configured map, and the admin screen checks every link in that chain and refuses to pretend a half working checkout is working. Nobody has yet completed a real purchase with a real card on a live gateway and then refunded it, which is the only test that counts.
This page is kept current, and the refund policy is tied to it: if the product does not do what this website says it does, say so within thirty days of paying and you get your money back. That is only a meaningful promise because this page exists and is specific.
Everything in the built table works with no key and no internet
Upload one file, run one scenario, and judge the parts marked built. The rest of this site is only worth anything if that part holds up.