Aegis Runtime is a purpose-built authority-enforcement platform for AI agents. We are exploring a strategic acquisition that could accelerate its integration into established AI, cloud, cybersecurity or enterprise software platforms.
Strategic opportunity; no acquisition is agreed. Not an offer to sell securities. Restricted RC1 demonstrations only.
An agent may have credentials and technical access without being authorised to perform a specific consequential action. Aegis defines and evaluates that boundary before governed execution.
AI Action Envelope™ expresses delegated authority across agents, actions, resources and constraints.
Runtime evaluation, enforcement gateway, policy, approval, audit and Sentinel proposal preparation.
Potential to extend an established platform with action-level governance. Buyer-specific value requires validation.
Requests action, resource and arguments
Action Envelope · Identity · Policy · Decision · Approval
Execution only where permitted and integrated
Prepares bounded action proposals; does not independently authorise or execute tools.
Proposed stable market-facing authority specification baseline, subject to final technical and legal review. MCP Gateway integration is deferred to RC2.
The following reflects previously accepted simulated authority decisions. This page does not call the live Runtime or execute any external tool.
design.readproject:rc1-sentinel-acceptance
Within the active Action Envelope.
design.readproject:unauthorised-project
Resource outside the active Action Envelope.
Live RC1 demonstrations are founder-led, screen-shared and limited to synthetic or explicitly approved non-sensitive data.
Internal release verification is not independent certification. Technical acceptance does not establish commercial traction.
Founder-confirmed rehearsal checks
Release package checksum checks
Restricted demo deployment
MCP Gateway integration planned
| ID | Evidence | Status | Date | Limitation |
|---|---|---|---|---|
EV-001 | Enterprise RC1 deployed Accepted for restricted, founder-led, non-sensitive demonstrations | Accepted RC1 | 28 Oct 2026 | Not general customer production |
EV-002 | Controlled rehearsal Eight of eight user-confirmed checks passed; no production changes | Founder-confirmed | 28 Oct 2026 | Not independent external assurance |
EV-003 | Release package integrity 16/16 checksums passed; acceptance evidence preserved and matching SHA-256 verified | Verified internally | 28 Oct 2026 | Evidence records available under controlled disclosure |
EV-004 | Bounded decision simulation design.read ALLOW for approved project and DENY for unauthorised project | Demonstrated | 28 Oct 2026 | Simulation only; no external tool execution |
EV-005 | Sentinel bounded proposal Sentinel prepares action proposals; Runtime remains authority decision-maker | Demonstrated | 28 Oct 2026 | No independent execution authority |
EV-006 | MCP Gateway Separate development implementation; RC1 integration deferred to RC2 | Development | Oct 2026 | Not part of accepted RC1 deployment |
EV-007 | Security exception Private HTTP transport between peered VPCs remains to be remediated | Open exception | 28 Oct 2026 | No sensitive customer data integrations |
EV-008 | Independent security assessment No completed independent assessment evidenced in this release record | Not evidenced | — | Do not describe as independently certified |
EV-009 | Commercial validation Customer revenue and signed design-partner traction not evidenced here | Not evidenced | — | Do not infer product-market fit |
This is a catalogue of proposed disclosures, not an unlocked document repository.
Why should a strategic buyer own this capability?
Executive acquisition thesis, strategic fit, build-versus-buy considerations and buyer-specific rationale.
What has been implemented?
Runtime, Action Envelope, PolicyEngine, ToolGateway, approvals, audit, Sentinel, Monitoring and system boundaries.
What can be substantiated?
Controlled RC1 acceptance, verified release evidence, test history, scope and known limitations.
What rights could be transferred?
Software ownership, contributor rights, trademark application, specifications, licences and chain-of-title review.
How could the buyer integrate Aegis?
API integration model, execution boundaries, deployment and RC2 MCP Gateway roadmap.
Where could it create value?
Buyer-specific product adjacency, competitive alternatives, commercial hypotheses and validation gaps.
What assets and obligations exist?
Ownership, expenses, financials, liabilities, agreements and transaction perimeter.
How would an acquisition proceed?
NDA, qualification, demonstration, indicative proposal, diligence and definitive agreements.
Statuses are preparation indicators, not access grants. No confidential documents are embedded or served by this prototype.
| Document | Category | Preparation status | Intended disclosure |
|---|---|---|---|
| Executive acquisition deck | Executive | To be uploaded | Pre-NDA or qualified |
| AI Action Envelope™ Specification v1.0 | Technical | Proposed baseline; final legal/technical approval required | Qualified |
| RC1 acceptance summary | Technical | Summary to be prepared | Qualified |
| Technical architecture overview | Technical | Sanitised version to be prepared | Qualified |
| Security exceptions summary | Security | To be prepared | Under NDA |
| IP ownership and assignment register | Legal | To be verified | Restricted diligence |
| Financial and operating summary | Financial | To be verified | Restricted diligence |
| Open-source dependency register | Technical / Legal | To be prepared | Restricted diligence |
| MCP Gateway RC2 roadmap | Technical | To be prepared | Qualified |
Executive thesis, high-level product overview, non-sensitive evidence summary and buyer fit. No source-code access.
Appropriate confidentiality agreement, buyer mandate confirmation, founder-led RC1 demonstration and selected technical documents.
Secure specialist virtual data room with per-buyer access, document classification, logging, watermarking where supported and legal review. Sensitive source access exceptional.
Transaction perimeter, IP transferability, indicative proposal, remaining diligence, definitive agreements and transition planning.
Contact Aegis Runtime through an approved existing business channel. The secure acquisition enquiry service is being prepared.
Actual restricted files should be hosted in a separately configured specialist virtual data room. A confidentiality agreement alone does not enforce technical access controls.
If your organisation is evaluating strategic opportunities in AI-agent authority enforcement, we welcome a preliminary expression of interest. Confidential access is not currently available through this website.
The secure enquiry service is being prepared. No submissions are being accepted through this website.
1. Submit an expression of interest through the verified secure intake service when activated.
2. We verify your professional identity, organisation and acquisition mandate.
3. Appropriate confidentiality arrangements are completed where required.
4. Approved representatives receive individually authorised, revocable access to selected diligence materials.
Source code, sensitive architecture, security information and transaction documentation are never published through this public page.
The registration service requires deployment and verification. Confidential diligence hosting remains separate and is not enabled by registration.