Core boundary
EVENAI Agent Core
The operating plane for portable agents.
A human-readable view of the approved Agent Core baseline: what can run, which policy governs it and which capabilities remain deliberately unavailable.
Published baseline · 14 August 2026 · read-only
Phase 11 profile
Controlled
Renew v1.6 retains its approved production-pilot policy and private control service.External mutation
Disabled
This public plane has no authority to send messages, change workflows or alter participant state.Live AI providers
None
Production continues without live-provider credentials or a public provider activation path.Deployment profiles
One core. Explicit operating rules.
Profiles bind portable architecture to a particular deployment without allowing product or industry language to leak back into the core.
Controlled pilottrusted-active
Primary deployment
Renew v1.6 / Participant 1
Preserves the Phase 11 production-pilot boundary while adopting the neutral deployment-profile contract.
- Agent Type
- [email protected]
- Workflow
- renew-v1.6
- AI policy
- synthetic_only
- External mutation
- disabled
Review binding details
Exact Source, Decision and Product Pack versions remain pinned. The private readiness, evidence and kill-switch controls continue to govern the pilot.
Reference onlydormant
Neutrality proof
Retail reorder reference
A non-gas reference deployment proves the same core contract can bind a different domain without production authority.
- Agent Type
- [email protected]
- Domain
- retail inventory
- Assurance
- reference-only
- Operational authority
- none
Review binding details
The profile exists to validate portability. It cannot be selected by the trusted production registry and cannot create external effects.
Portable architecture
Agent Type is not a deployment.
The separation makes new deployments reproducible while keeping authority and policy visible at the final binding point.
- 01
Agent Core
Generic orchestration, evidence, authority, policy, scheduling and provider ports.
- 02
Agent Type
Defines portable capabilities and required ports without naming a customer, sector or provider.
- 03
Packs
Source, Decision and Product Packs supply bounded domain behaviour with explicit assurance.
- 04
Deployment Profile
Binds an Agent Type, exact Pack versions and deployment policy into one deployable unit.
AI provider boundary
Provider-neutral by design.
The core depends on an AI provider contract, not a provider brand. Provider selection is deployment policy and remains inactive until its evidence and governance gates pass.
Synthetic provider
Deterministic controlled testing
Hugging Face candidate
Adapter boundary prepared; no model, network or credentials
Public-plane safeguard
Visibility without operational exposure.
The public surface contains no customer data, secrets or live controls. Its authenticated status route is live but remains fail-closed: identity, server-only storage and a fresh redacted snapshot must pass validation on every request.