What it fixesnine layers, one foundation
Six situations. Not nine layers.
Nobody has ever had a bad week because of an architecture diagram. They have had one because the report took a day, the approval sat in an inbox, and nobody could say where the thing had got to. So here are the six, in the words of the person they happen to — and underneath each one, the part of the foundation that does the work.
pick one.
the honest version
Where did it get to?
Knowing where something has reached means asking whoever touched it last, and waiting for them to be free.
A day of waiting on a question that has an answer, and a weekly meeting held to read it out.
Status is read from the work itself. The item knows what stage it is at because moving it is what changed the stage.
Built onWorkflow & audit — the step is the record
The same number, three times
One fact typed into a form, a sheet and a message, because none of the three can see the other two.
Quiet, constant, and the one that compounds: every copy is a chance for the three to disagree.
It is entered once, in the process that owns it, and everything else reads it from there.
Built onCore data & identity — one record, many views
The report takes a day
A recurring report assembled by hand from exports, because no single system can answer the question on its own.
A skilled person spending a day a month being a query engine.
The question is asked once, in plain language, and answered from the work — with the same permissions the asker already has.
Built onSearch, analytics & MYNA — the answer comes from the records
New people take months
A joiner spends their first weeks learning where things are kept rather than how the work is done.
Months of half-productivity, repeated with every hire, and never counted.
The process is the software, so following it teaches it. The steps, the words and the roles are your own.
Built onInternal Tools Studio — your operating model, configured
It is sitting in an inbox
Approvals route by memory: someone remembers who signs this, and forwards it.
Days lost to things waiting on a person who did not know they were waiting.
The rule routes it, the threshold is part of the workflow, and the reminder is automatic — not somebody's diary note.
Built onWorkflow & governance — the rule is in the process
Prove that it happened
Evidence is assembled after the fact, from chat threads, mailboxes and memory, in the week before it is needed.
The scramble, and the quiet risk that the reconstruction is not quite what happened.
The record exists because the work happened. Who asked, what ran, what changed, when — kept beside the item.
Built onTrust, audit & permissions — written as it happens
For the reader who asks what it is made of
The same answer, told as architecture.
This is the technical version of everything above: nine layers on one foundation, each of them the reason one of those six situations changes. It is the second thing we say, not the first — but it is not hidden, because the person who has to maintain this will want it.
- Core PlatformLayer 01
Identity, permissions, workflow, audit, documents, search, notifications, APIs — built once, shared by everything above.
- Internal Tools StudioLayer 02
Forms, roles, rules, dashboards and your own terminology. Your operating model becomes the software.
- Business FoundationsLayer 03
Twelve reusable operational blocks, configured around the organisation rather than sold as twelve products.
- AI-nativeLayer 04
Model gateway, retrieval, document intelligence, copilots, prediction, agents — permission-aware and auditable by default.
- IntegrationLayer 05
API-first and event-driven, so retaining a system you already run is a real option rather than a polite concession.
- OperationsLayer 06
Deployment, monitoring, backups, releases, upgrades, security. None of it demos well; all of it decides whether the software lasts.
- TrustLayer 07
Identity, authorisation, human approval, data boundaries, model governance, observability, evaluation. Architectural, not a policy PDF.
- MYNALayer 08
Models, knowledge, memory, context, reasoning, verification, agents, tools. The intelligence layer the AI-native layer implements.
- WorkLayer 09
wayworks.space — people, teams, workflows, execution. The layer every organisation already has, whether or not it bought software for it.
nine layers, one core.
that's the architecture
Where it shows
wayworks.space is the part you use.
Everything above is the ground. wayworks is the floor you stand on: the work layer, at your own address, connected to the assistant your team already has open.