Agentic infrastructure · sovereign by construction
Nine pre-built Service Packs on one sovereign platform — so a small, mid-market or large enterprise builds the services its own business needs instead of building a platform first. You own the hardware, the control plane and the data from the first invoice, and every consequential action still stops for a person.
Mission
To put agentic AI inside institutions that cannot outsource their accountability — owned outright, routed by policy, and stopped by a person before it does anything that matters.
Delivered as one SKU
Dell PowerEdge hardware with NVIDIA-accelerated compute, Red Hat OpenShift/RHEL and the TerraSigna platform — designed, deployed, validated and supported as one thing, customer-funded through the Dell OEM channel.
An open, declarative platform
A new service is six declarations over one contract — agents, knowledge, connectors, prompts, experience, policy. Runtime, retrieval, routing, gates, placement and audit are inherited, and a service cannot loosen them.
Partners build packs on the same contract we do. Which is why the tenth service costs domain work rather than platform work.
The architecture
Seven planes, owned once and operated everywhere. A vertical service declares six things and inherits everything else — which is why the ninth service costs domain work rather than platform work.
One platform, many agentic services
the Platform Service Contract v1.1 is the only interface between them
each pack declares six things and nothing more
TerraSigna agentic platform — seven planes, owned once, operated everywhere
The pack carries domain meaning. It never carries runtime, retrieval, routing, gates, placement or audit.
Each is owned by the platform, versioned by the platform, and reachable by a service only through the contract.
The platform
Ten agent archetypes, one kernel, and a single path from an intent to an action — the same eleven steps for a 5G design, a meditation session and a factory work order.
A service designer picks an archetype and specialises it. The archetype carries proven defaults for memory, tooling, safety and model policy that a specialisation may tighten and may not loosen. Adding an eleventh is a platform decision, never a service workaround.
| Archetype | Behavioural contract |
|---|
Two of these carry the weight. The Actuator is the only archetype permitted a side-effecting external call — so the set of things that can change the world is enumerable by reading declarations rather than by reading prompts. The Guardian is mandatory in every service and red-teamed before release.
The same path every time. Only the declarations differ.
The class decides the tier and the site. A request carrying regulated personal data cannot reach a frontier API, whatever the prompt asks for, because the router evaluates the data rather than the request.
The part most companies leave out
Both sit inside the execution path rather than in front of it. There is no configuration that removes them and no prompt that talks past them.
Mechanism one · architecturally unbypassable
Three stacked rulebooks — privacy, sovereignty, regulation — evaluated on every single inference. It sits inside the reasoning gateway rather than in front of it, so there is no path to a model that avoids it.
A regulated context cannot reach a frontier API whatever the prompt asks for, because the router evaluates the data and not the request. The decision is made before a model sees anything, and it is recorded.
Mechanism two · declared per service, enforced by the platform
Each service declares which of its actions are consequential and who may confirm them. A network configuration push. A grade written to a permanent record. A maintenance command on a production line. Identical mechanics everywhere, and the declaration is data the platform enforces — not a behaviour the service is trusted to implement.
Execution pauses for a named human. The decision is recorded immutably whether it is approved or refused, so the audit trail contains the refusals too.
Only the Actuator archetype may make a side-effecting external call, and every consequential one raises the gate. That is what makes the claim checkable: the set of things this system can do to the world is enumerable by reading declarations, rather than inferred by trusting prompts.
The catalog
Each is a certified, versioned bundle that installs onto the platform the way an application installs onto an operating system. Each declares six things and inherits the rest.
What a service pack actually is
six declarations — everything the vertical owns, and nothing else
TerraSigna agentic platform — inherited unchanged · zero pack engineering
What the pack adds is domain meaning. What it never touches is runtime, retrieval, routing, gates, placement or audit.
Partners
TerraSigna is not structured as a vendor selling downward into markets. A local company owns its corpus, its evaluation set, its adapters and its customer relationships outright, and licenses its extensions back into the network — so a good adapter built in one country can serve another, and the partner who built it is credited for it.
The asymmetry, named
A local company may tighten the safety posture for its market; it may never loosen it. It may price as it chooses above a floor. It may build any adapter it likes; it may not edit core. Acceptance criteria and evidence requirements, the Policy Router and its data classes, the Consequential Action Gate, trust-domain separation, the Agent Kernel and the archetype model, and the conformance suite itself are not configurable by a partner and not localisable.
That asymmetry is precisely what is being licensed. It is what lets an institution in one country be shown evidence gathered in another and treat it as meaningful, and it is the only reason a certified pack is worth more than a codebase. A partner who wants the freedom to change the acceptance criteria is asking for a product that is worth less.
Go to market
Four stages. Each one is paid work that ends at an evidence gate, and either side may stop at any of them. Nobody is asked to capitalise a business on the strength of a demonstration, and no equity exists until the market has been proven on real numbers.
Every stage is real work that is paid for. Either party may stop at the end of any of them without owing the other anything beyond the disposition of data and code agreed in advance.
Stage one is a paid market definition study whose whole purpose is to turn a market assumption into a named list of institutional targets. It is small enough to be a real test rather than a negotiation, and the ladder is arranged so that either side can walk away three times before any capital is at risk.
One signed contract with an institution willing to be named is worth more than a pipeline of conversations. It sets the reference architecture, produces the first evidence pack, and is what every subsequent procurement in that market asks about.
Territory rights deepen against revenue, customers, quality, funding and conformance results. They are conditional and renewable, and they are not granted on the strength of an intention.
An earlier draft of the framework inserted a licensed-operator phase there. It was removed, because the discipline it was protecting — that deeper rights are earned rather than granted — is already carried by three paid gates standing in front of any equity.
The joint venture
The structure is unusual enough that it ought to be argued for rather than announced. Four conventional alternatives were considered first, and each fails for a reason worth stating.
| Structure | Why it fails |
|---|
A majority stake is available and was proposed in earlier drafts. It was declined, and the reasons are the argument.
01
The local partner carries the capital, the payroll, the customer contracts and the first-line service commitment. An owner carrying that much risk with a minority of the equity is an owner who will eventually stop carrying it.
02
A sovereign deployment is a procurement, and procurements are won by a company with a tax identity in the country, references the buyer recognises, staff who can be in the building, and the standing to sign a first-line service commitment. A majority-foreign-owned vehicle answers a different set of procurement questions, and answers several of them worse.
03
A lead architect who will be taken seriously by an operator's chief architect does not leave a good job to run a reseller's deployment team. They might leave it to co-found a company. "Co-found the national operator" and "run the local branch" attract different people.
04
Governance is held through technical and brand rights rather than votes — and those are more durable, because they are enforced by the conformance suite rather than by a shareholder meeting.
It gives the local market a committed owner with real equity and real upside. It lets TerraSigna contribute what is already built rather than cash it does not have. And it puts both sides on the same profit and loss account, so that neither is optimising against the other.
A partner who reaches the anchor-customer stage and does not want equity — because they are already capitalised, because their shareholders will not accept a minority foreign holder, or because the market turns out to be smaller than a joint company justifies — may instead take a time-limited, milestone-based territory licence. It is country- and pack-limited, with no implied rights to other packs or markets, and its exclusivity is tested the same way.
Four things we do not say
We do not promise cumulative profitability within two years.
We do not describe the incubation period as free or self-funding. It is neither.
We do not grant exclusivity on the strength of an intention rather than measured performance.
We do not claim that aggregate telemetry is anonymous. Aggregate does not automatically mean anonymous.
Local operations
TerraSigna ships a version-pinned core and a Service Pack already proven somewhere else. Of the seven planes, L2 through L6 arrive complete and are not localisable. L1, the Knowledge Plane, and L7, the Prompt & Skill Library, arrive empty — and what fills them belongs to the local company.
Months of skilled work by people with other options. Each stream has a defined output, and every output belongs to the local company.
| Stream | Work | Output — and it belongs to the local company |
|---|
Four ownership layers, classified at acceptance rather than argued about afterwards. These are ownership layers, not the seven architectural planes.
| Layer | Owner | Treatment |
|---|
This is the position on which TerraSigna does not move, and it is held for TerraSigna's benefit as much as the partner's. It is the stated differentiator: the licensing models on offer elsewhere take the local work and keep it. It is what makes the local team recruitable — they will not do months of skilled work to enrich a licensor. And it survives tax scrutiny, because returns on an intangible follow the entity that actually performs and controls its development. What TerraSigna requires is a royalty-free licence back, not title.
TERRASIGNA RUNS
The seven planes, the Agent Kernel, the ten archetypes, the Policy Router and its data classes, the Consequential Action Gate, the reliability stack and the audit trail. The versioned Platform Service Contract and the extension manifest that declares what an overlay may override. The conformance suite, certification of local deployments, and engineering support on verified core defects.
THE LOCAL COMPANY RUNS
The country and Service-Pack business plan. Data: lawful access, licences, consents, provenance, curation into the pack's Knowledge Domains. Localisation at the declared extension points — language, experience, policies, prompts, personas. Infrastructure and hosting. Every employment relationship. Customer contracts, first-line support, billing, and the local service commitment.
Controller and processor roles are determined from the actual processing purposes and decision rights of each Service Pack. They are not assigned by a blanket statement — in a partnership agreement a blanket statement is a liability rather than a simplification.
Subscriber content and personal data remain inside the approved trust domain unless a lawful transfer is documented. The Policy Router enforces this at runtime; the contract merely records it.
Conformance results, evaluation scores, rework rates, incident counts — defined contractually rather than collected broadly. Aggregate does not automatically mean anonymous, and this is not claimed to be.
Training and evaluation use of customer data must be authorised separately from service delivery. Deletion, portability, incident response and model-artefact disposition all survive termination.
What is different here
Each one is a property of the architecture rather than a policy we promise to follow. That distinction is the entire proposition.
01
The hardware is yours from the first invoice. The control plane is yours. The data never leaves ground you control, and an air-gapped site never connects at all — it takes updates on physical media. No hyperscaler sovereign region can say that, because the control plane always stays with the vendor.
02
Policy routing, the human-confirmation gate and a mandatory Guardian arrive with the platform. A service cannot opt out of them and a partner cannot loosen them. The posture may be tightened for a market. It may never be relaxed.
03
Every delivered site contributes its design, its acceptance results and its operational telemetry back into the knowledge domain, so sizing accuracy and proposal speed improve with each engagement. A competitor starting today starts that accumulation at zero.
A demonstration proves something worked once, for the person who built it. An evidence pack proves it works for you, and can be audited after everyone involved has moved on.
Engagements begin with the customer's own requirements specification, not with our product sheet. The design that comes back is sized against it and validated against the rules that apply in your jurisdiction.
Every criterion is tested and its result recorded with the evidence attached, so a procurement office that has changed staff twice can still read what was accepted and why.
A service release must pass adversarial red-teaming of its Guardian, functional tests of both gates, quality thresholds on its own evaluation sets, and a conformance run in a clean environment its authors did not set up. Including our own.
Cost models and facility validators must return identical verdicts for identical inputs — enforced as a service objective, not hoped for.
Contact
The most useful first conversation is about your requirements specification and the rules you have to satisfy — not about our product.
TerraSigna AI, Inc. · Florida, United States
Non-negotiables
Everything this pack owns. Everything else is inherited from the platform.