AEVUM CORE — CODEX TOOLING & EXECUTION POLICY

Status: Active

Effective date: 2026-04-18

Authority: User-controlled execution policy

Enforcement standard: Any deviation requires explicit user approval before execution

1. System Principle

Aevum Core is a local-first, sovereign system.

No external dependency is allowed unless it is explicitly approved in this policy or explicitly approved by the user in the current thread.

2. Approved Technology Stack

2.1 Native Apple Stack (Primary)

The following are fully approved and must be preferred:

• iOS / iPadOS / macOS
• Siri (native Apple)
• Xcode
• XCUITest
• Apple Simulators
• Swift
• Core Data / SQLite / SwiftData for local storage
• Localhost API (Aevum-owned)

2.2 Local And Open-Source Stack

Approved for local execution only:

• Python
• OpenClaw
• Open-source tools running locally only

2.3 AI / Intelligence Systems

Approved for controlled usage:

• ChatGPT
• Codex
• Gemini
• Antigravity (AG)
• Phi
• QWEN

2.4 Approved External Services (Explicitly Allowed)

These are the only externally hosted systems allowed:

• Cloudflare R2, for storage and file downloads only
• Stitch by Google
• Codex, as the execution layer

3. Strictly Disallowed Unless User Initiates Or Approves

The following must not be introduced, suggested, or used without explicit user approval:

• Any SaaS tool not listed in this policy
• Any cloud API not explicitly approved
• Any external database or storage system not listed above
• Any third-party automation platform
• Any external testing service

4. Hard Execution Rules

Rule 1 — No Assumptions

If a tool, service, framework, or system is not listed as approved:

• Do not use it
• Do not suggest it as a default
• Ask for approval first

Rule 2 — No Silent Substitution

Do not replace approved tools or architecture components with alternatives for convenience, preference, or industry convention.

Rule 3 — Local-First Enforcement

All core logic must:

• run locally
• execute without internet
• remain functional offline

Exception:

• Cloudflare R2 may be used only for file storage and file downloads

Rule 4 — Persistence And Pipeline Integrity

All internal state changes must route through:

• the IntelligencePipeline via EventQueueActor, where pipeline-driven ingestion is required
• authorized SwiftData / Core Data / SQLite-backed local containers owned by Aevum

The Aevum Local API on port 8080 is classified as:

• an internal inference gateway
• an external execution hook
• not the canonical internal CRUD boundary for native app persistence

No direct state mutation is permitted from external or third-party scripts unless it passes through the locally compiled Aevum pipeline and approved local persistence layer.

Rule 5 — Native App Persistence Boundary

The native iOS, iPadOS, and macOS apps must rely on local persistence owned by Aevum, not an external hosted backend.

UI and local app flows must not introduce unapproved remote state dependencies.

Rule 6 — Testing Integrity

All testing must:

• run locally
• use XCUITest plus OpenClaw, or another explicitly approved local stack
• validate UI plus API together when the tested flow touches both layers

No external testing platform may be introduced without explicit approval.

Rule 7 — Data Sovereignty

• No external data transfer unless explicitly approved
• No background sync to external systems unless explicitly approved
• No hidden telemetry
• No silent analytics or monitoring services

5. Operational Behaviour For Agents

Agents, including Codex and automation systems, must:

1. Read this policy before execution
2. Restrict actions to approved tools and services
3. Refuse execution if constraints would be violated
4. Ask for clarification when uncertain
5. Stop and request explicit approval before any deviation from this policy

6. Failure Condition

If any agent:

• introduces an unapproved tool
• attempts an unapproved external integration
• bypasses local-first rules
• bypasses pipeline or local persistence constraints

execution must stop immediately and the agent must request explicit user approval before proceeding.

7. Priority Order

When building, recommending, or executing, the order of preference is:

1. Apple-native stack
2. Aevum-owned local persistence and local execution boundaries
3. Local/open-source tools
4. Approved external services, only when necessary and only within their allowed scope

8. Final Directive

This policy overrides:

• default tool preferences
• industry-standard substitutions
• convenience optimizations
• undocumented architectural shortcuts

Aevum Core must remain:

• Controlled
• Deterministic
• Sovereign

at all times.

9. Explicit Approval Clause

Any deviation from this policy requires explicit user approval in advance.

Silence, implication, convenience, prior habit, or inferred intent do not count as approval.