Contracts and delegated authority
The system begins with principals, entities, agreements, policies, budgets and named approval owners. No agent receives authority through implication.
Agentic operating architecture
Agents are the labour layer. Authority is the product.
DESIGN RULE
Provider-neutral skills, deterministic workflows and evidence receipts survive model turnover. Existing ERP and business systems remain authoritative until a controlled write-back gate says otherwise.
01
System layers
The control plane begins above the model.
The model is replaceable. The durable asset is the operating graph that binds organisations, contracts, identities, assets, workloads, approvals and evidence.
Identity and tenant boundaries
Separate organisations, service accounts, secrets, memory, budgets, repositories and queues. Shared infrastructure never means shared access.
Existing-system connectors
ERP, shop, CRM, documents, email, finance preparation, facilities and energy enter through read-first, typed interfaces.
Canonical operating graph
Parties, assets, contracts, workloads, orders, approvals, evidence and revenue streams receive stable identifiers and provenance.
Workflow and agent runtime
Deterministic workflows handle repeatable state transitions; agents research, classify, draft and reason inside explicit boundaries.
Model and compute routing
Local inference, cloud frontier models and specialist providers are selected by sensitivity, quality, latency, resilience and measured cost.
Control room and evidence ledger
Owners see decisions, economics, incidents, obligations and proof—rather than a stream of autonomous activity without accountability.
02
Existing IT estate
Integrate by earned authority, not replacement theatre.
Initial access is read-only. The system learns the company's actual object model and exceptions before any agent can change prices, inventory, contracts, finance or customer commitments.
Inventory
Catalogue systems, data owners, interfaces, identities, manual workarounds and contractual constraints.
Observe
Create read-only connectors and event capture. Establish baseline quality before changing production state.
Normalise
Map source objects into typed canonical records with source references and freshness policies.
Shadow
Run recommendations beside current human workflows. Record disagreement, exceptions and missing evidence.
Delegate
Grant narrow write actions only after acceptance tests, rollback and a named authority owner.
03
Reusable skill estate
Ten skills turn the deal into an operating discipline.
Each skill declares inputs, outputs, authority, stop conditions, proof obligations and handoff. The repository files are executable operating specifications—not loose prompts.
Partner Underwriter
Decision. Is this counterparty, asset base and mandate worth entering?
Output. Partner score, red flags, data-room request and stop/go memo.
Recommend only. Legal, credit and investment approval remain human.Workload Underwriter
Decision. Which workloads justify local, cloud or hybrid capacity?
Output. Demand baseline, data classification, latency profile and utilization envelope.
May classify and model; cannot buy capacity or promise savings.Deal Architect
Decision. Which commercial structure separates value, control and risk cleanly?
Output. Deal memo, party graph, consideration map and stage gates.
Produces options; principals approve economics and control rights.Contract Pack Composer
Decision. Which agreements and schedules make the operating bargain explicit?
Output. Clause issue list, document matrix, dependencies and counsel brief.
Never issues legal advice or executable agreements without counsel review.IT Integration Mapper
Decision. How does the system attach to the existing estate without destabilising it?
Output. System inventory, trust boundaries, connector plan and write-back gates.
Read-only discovery by default; production writes require named approval.Capital Stack Planner
Decision. Which cost belongs to operating cash, lease, debt, subsidy review or equity?
Output. Sources-and-uses model, financing pack and covenant questions.
Planning support only; lenders, tax advisers and principals decide.Procurement Conductor
Decision. What is purchased now, deferred or rented?
Output. Bill of materials, quote comparison, warranties, acceptance tests and asset register.
May prepare orders; cannot bind a company without delegated authority.Node Operations
Decision. Is the physical and digital estate healthy, secure and within its service envelope?
Output. Runbook, health state, incident record, capacity ledger and maintenance queue.
May execute reversible runbook actions; consequential actions escalate.Revenue Operator
Decision. Which verified capability becomes an internal saving, service or external offer?
Output. Offer design, pricing evidence, pipeline and contribution-margin view.
Drafts and analyses; pricing and customer commitments require approval.Provenance Auditor
Decision. Can every material claim, action and payment be reconstructed?
Output. Evidence receipts, exceptions, missing approvals and audit-ready timeline.
Append and flag; never rewrites source records.04
Compute estate
Buy each class for a named economic role.
Heterogeneous infrastructure is intentional: reliable workers, private high-memory inference, cloud quality and later CUDA throughput solve different constraints.
| Class | Reference form | Economic role | Purchase trigger |
|---|---|---|---|
| Always-on worker nodes | Mac mini-class or equivalent | Browser, repository, scheduling, observability, lightweight services and resilient orchestration. | Pilot-approved after workload baseline |
| Private-memory node | High-memory AMD / unified-memory class | Confidential retrieval, embeddings, document intelligence and larger quantised models without default cloud transfer. | Pilot-approved after workload baseline |
| Cloud burst | Frontier API and hosted accelerators | Irregular high-quality reasoning, coding, vision and peak throughput paid per use. | Metered from day one |
| CUDA production node | NVIDIA workstation or server | Purchased only when measured queues, media workloads, fine-tuning or cost crossover justify ownership. | Measured utilization or revenue crossover |
| Site foundation | UPS, encrypted storage, network, metering | The unglamorous layer that determines recoverability, evidence quality, insurability and total cost. | Measured utilization or revenue crossover |
The architecture aligns with resource-centric zero-trust principles and lifecycle AI risk management. See NIST SP 800-207 and the NIST AI RMF.