INTELLIGENCE FOR A MORE CAPABLE WORLD
A complete intelligence ecosystem.
THE ELDER governs models, knowledge, tools, memory and execution — then extends them into specialized intelligence for every domain.
HUMAN AMBITION AMPLIFIED BY INTELLIGENCE.
WHAT THE ELDER IS
An operating layer for intelligence — not another assistant.
Most AI you meet is a conversation. THE ELDER is the layer the work runs on: it chooses the model for the task, keeps the knowledge and the memory, calls real tools, and acts only within the authority you granted — recording what it did. The ecosystem is organized around this shared layer, so products can consume common intelligence, memory, authority and execution instead of duplicating them.
A CHATBOT
The conversation is the product.
Useful for questions and dialogue. Continuity, tools, authority and execution depend on the platform around it.
A SINGLE MODEL
One provider's judgement.
One vendor's strengths, limits, prices and outages become yours. Changing your mind later means rebuilding on top of a new one.
THE ELDER
An operating layer.
Routes work across models, keeps knowledge and memory between sessions, uses real tools, and executes only what you authorised — on your machine or in the cloud, with a record of every step.
Governed autonomy
Operate with built-in safety, alignment and control.
Model independence
Use the best models for the task — today and tomorrow.
Local or cloud deployment
Run where it makes sense — on your infrastructure or ours.
Shared intelligence
A common foundation that drives greater capability across every domain.
HOW IT WORKS
Six things have to hold together. THE ELDER is where they do.
An answer is easy. Work that survives contact with your systems needs a model chosen for the task, knowledge that outlives the session, tools that reach real software, specialists who own their domain, execution that stops at the limit of what you granted, and a record of what actually happened.
Models
Route, never marry.
The task chooses the engine: a model running on your own machine, a hosted provider, or a deterministic calculation where guessing would be wrong. Credentials stay references, never copies.
Knowledge and memory
What was decided is kept.
Decisions, artefacts and context persist between sessions, in your own store — so the next request starts from what the last one established instead of from nothing.
Tools
Real systems, not descriptions of them.
Open protocols — MCP, A2A, OpenAPI — reach the software you already run. Secrets are passed by reference and never written into a prompt.
Operators
Specialists, not one general assistant.
Each operator owns a domain and carries its own rules, so the work is done by something that knows the subject rather than by a single voice improvising across all of them.
Governed execution
Nothing material happens unasked.
Every action runs at a granted level of authority. Anything above that level stops and asks, and each step is written down before it runs and after it finishes.
Verification and learning
The record is the point.
What a run cost, what it produced and whether it held are checked and kept. That record is what the next run begins from.
Step six returns to step two: what a run establishes becomes what the next one already knows. That is the cycle, and it is why the ecosystem gets more capable without each product having to learn the same things again.
COMPUTER INTELLIGENCE
Capability status: AVAILABLE · READ-ONLY DISCOVERY
Your computer, made legible.
THE ELDER discovers the machine it runs on, maps applications, services, processes, runtimes, repositories and storage as connected entities, and records how that observed structure changes over time — without changing the system itself.
DISCOVER
Inventory the machine through controlled, read-only observation.
MAP
Organize what was found as entities, relationships and states.
TRACK
Compare observations and preserve the history of detected change.
AUDIT
Record every discovery run in a verifiable chain.
Maps what it discovers. Tracks what changes. Changes nothing.
GOVERNED AUTONOMY
Capability status: PROVEN AT A2 · OWNER APPROVED
Power, bounded by permission.
THE ELDER can prepare a material action, show exactly what it will do, obtain explicit Owner approval, execute only the signed action within the granted authority, verify the result, and leave a durable receipt.
OBSERVE
Understand before acting.
THE ELDER gathers the context required to define the work without producing a material effect.
PREPARE
Turn intent into an exact action.
The target, payload, authority ceiling, effect, expiry and rollback plan are fixed before approval.
AUTHORIZE
The Owner decides.
The approval is cryptographically bound to one action, one payload, one runtime and one authority ceiling.
EXECUTE
One permit. One bounded effect.
A one-shot permit can produce only the action that was signed. It cannot become permanent or authorize a different execution.
VERIFY
Read the result back.
Success is recorded only after the final effect is measured at its real destination and matched to the signed payload.
RECORD
Leave durable evidence.
The execution receives a verifiable receipt inside the valid audit segment, including its identity, result and proof.
Authority does not widen because work continues. Every material effect must match the permission that created it.
THE ELDER ECOSYSTEM
One core. Specialized by domain.
THE ELDER is the common core: intelligence, memory, orchestration and governed authority. Each product below is that core applied to one domain — not a separate platform rebuilt beside it.
THE CORE
THE ELDER
Intelligence, memory, orchestration and governed authority — the foundation every product in the ecosystem runs on.
- Shared intelligence
- Shared memory
- One orchestration layer
- Governed authority and audit
Products consume these capabilities instead of duplicating them.
The ecosystem does not multiply platforms. It extends one governed core into the domains where the work happens.
THOR
MARKETS INTELLIGENCE
Market structure, options analysis, strategy, risk and execution in one governed trading environment.
Primary context: For traders and trading desks.
ATLAS
ARCHITECTURAL INTELLIGENCE
Architecture, structure and building services — design work carried through to the documents a project actually needs.
Primary context: For architects and engineers.
LEDGER
FINANCIAL INTELLIGENCE
Financial, economic and record-keeping intelligence for the numbers a business runs on.
Primary context: For finance and accounting work.
CYBER
SECURITY INTELLIGENCE
Protection, security and governed defence.
Primary context: For defensive security work.
SECOND SELF
PERSONAL INTELLIGENCE
Contextual personal intelligence and a continuous interface with its Owner.
Primary context: For the individual, every day.
FOR YOU · BUSINESS · ENTERPRISE
One platform. Three ways to work with it.
THE ELDER adapts to the context it is used in — a person, a team, an organization. What changes is scope, integration and how much you configure. What does not change is the core, the memory and the limits on authority.
ONE PERSON
For you
A more capable you, every day.
Primary user: A person working on their own — the Owner, or an independent professional.
Personal work, research and decisions, with context that outlives the session. The specialized products stay connected to the same core, so what is learned in one place is not lost in another.
Implementation and controlYou are the Owner. No material action happens without your explicit approval, and each one is limited to exactly what you signed.
A TEAM
For business
Turn ideas into outcomes.
Primary user: A company, a team, or an operation.
Coordinate information, processes and specialized products across the people doing the work — design, finance, markets, security — on one shared foundation instead of separate tools that do not know about each other.
Implementation and controlHuman approval stays in the loop, and every material action leaves a record of what actually happened.
AN ORGANIZATION
For enterprise
Trusted intelligence at scale.
Primary user: An organization with its own infrastructure, rules and separation of duties.
Controlled integration into an environment that already exists: where the platform runs, what it is allowed to reach, and who authorizes what are decided per deployment.
Implementation and controlRequires assessment and configuration before use. Authority limits and separation of duties are set up front, not assumed.
THE SAME FOUNDATION IN ALL THREE
- A model chosen for the task
- Knowledge that outlives the session
- Tools that reach real software
- Specialists who own their domain
- Execution that stops at the limit of what you granted
- A record of what actually happened
The difference between the three is scope, integration and control — never the governing core. Commercial terms are set per product.
COMMERCIAL ACCESS
Access is configured, not taken off a shelf.
THE ELDER is offered through a small number of commercial models. Which one fits depends on the context, the products involved and where it runs — so terms are set after an evaluation, not before one.
Licensing
THE ELDER and its products can be licensed within the scope and configuration agreed in the contract.
Scope, term and rights are contractual. None of them are fixed on this page.
Subscription
Access can also be arranged as a subscription, for the products where that model applies.
No tiers and no published rates. The shape follows the evaluation.
Deployment
Where the platform runs is part of the arrangement, not an afterthought — your infrastructure, cloud, or both.
Each option is subject to technical, security and compatibility assessment, per product and per environment.
Custom implementation
For business and enterprise, the platform can be assessed and configured for an environment that already exists.
Assessment comes first. Universal integration is not claimed.
Deployment options, each evaluated
- LOCAL / PRIVATEOn infrastructure you control.
- CLOUDOn hosted infrastructure.
- HYBRIDSplit between the two, where the work requires it.
Evaluated per product and per environment — not guaranteed for every combination.
The next step
Access begins with an evaluation — of the context, the products involved and the environment they run in. Demonstrations and commercial discussions follow from that evaluation.
This page does not publish a channel for requesting one yet, and it will not pretend to.
COMMERCIAL TERMS PER PRODUCT · PRICES NOT PUBLISHED IN THIS PHASE
Terms, scope and availability are set per product, after evaluation. Nothing on this page is an offer or a price.
TRUST · SECURITY · CONTROL
Nothing material happens unless you sign it.
THE ELDER does not receive open-ended authority. A material action is prepared, shown to you in full, signed by you, executed once within exactly the permission you signed, verified against its real result, and recorded.
OWNER APPROVAL
You decide, and the decision is bound to one action.
Observing and preparing happen first and change nothing. Authority begins only when you sign — and the signature is bound to that one action, that payload and that runtime, not to a category of work.
LIMITED AUTHORITY
One permit. One use. One ceiling.
The permit covers exactly the action that was signed, at the internal-execution ceiling it was granted for, and it can be used once. It cannot become permanent, and it cannot authorize a different execution.
CANONICAL EXECUTION
One path, or none.
The effect is produced by one canonical executor, at the destination that was signed — created exclusively there, never in a temporary place and copied afterwards.
VERIFIED EFFECT
Read back, not reported.
Success is recorded only after the result is read back from its real destination and matched, byte for byte, against what you signed. A response is not an effect.
VERIFIABLE RECORD
A receipt that outlives the run.
The execution leaves a durable receipt inside the valid audit segment, carrying its identity, its result and its proof. Repeating the same execution returns the same receipt instead of acting twice.
WHAT IS NOT CLAIMED
- One action type, at one ceiling. What was proven is a single reversible internal action — not general autonomy, and not a higher authority class.
- Rollback is not claimed as demonstrated by this evidence.
- The receipt is verifiable inside the valid audit segment. The history before that segment is not claimed as verified.
- No certification, no external audit, no absolute security. Business and enterprise implementations require assessment and configuration before use.
Explicit control. Limited authority. Verified effect. Verifiable record.
A MORE CAPABLE TOMORROW