# UAPE & DAIMON OS — AI Agent Resource Guide (llms.txt)

Welcome to the official technical directory for the **UAPE (Universal Autopoietic Platform for Enterprise)**, **DAIMON OS**, and **UAPE DAIMON OS Studio** ecosystem. This document is optimized for consumption by Large Language Models (LLMs), AI coding assistants, and search agents.

---

## 1. Project Vision & Core Definitions

* **DAIMON OS**: A sovereign, single-tenant business operating system kernel written in Rust. It runs sandboxed WASM business modules governed by signed Contract Manifests. Storage is local-first, transactional, and powered by an embedded key-value/MVCC store (`redb`).
* **UAPE**: The overarching foundation providing modular workflow governance, contract compilation, cryptographic signing, autopoietic triggers (LLM-driven system self-evolution), and audit tracing.
* **Contract Manifest**: A declarative JSON file signed by the system operator that governs capabilities, storage topology, API gateways, and autopoietic transitions for a module.
* **UAPE DAIMON OS Studio**: An enterprise-grade, manifest-driven workspace and SDK for designing, testing, and deploying business modules.

---

## 2. JSON Schemas & Core API Specifications

The following schemas are hosted at `https://uape.dev` and dictate system-wide contract structures:

### 2.1 Core Schemas (served at `https://uape.dev/schemas/...`)
* **Contract Manifest Schema**: `https://uape.dev/schemas/contract-manifest-1.0.json`
  * *Purpose*: Defines valid fields, scopes, permissions, WASM imports/exports, and storage structures for modules.
* **Autopoietic Trigger Schema**: `https://uape.dev/schemas/autopoietic-trigger-1.0.json`
  * *Purpose*: Formulates LLM-driven runtime changes, capability extensions, and automated code-generation rules.
* **Sub-Entity Schema**: `https://uape.dev/schemas/sub-entity-1.0.json`
  * *Purpose*: Governs relational sub-structures in the modular MVCC store.
* **Audit Event Schema**: `https://uape.dev/schemas/audit-event-1.0.json`
  * *Purpose*: Describes signed state-mutation rows recorded in the append-only logs.
* **Gateway Schema**: `https://uape.dev/schemas/gateway-1.0.json`
  * *Purpose*: Configures integration points (e.g. Telegram TMA, gRPC endpoints, webhooks).
* **Storage Topology Schema**: `https://uape.dev/schemas/storage-topology-1.0.json`
  * *Purpose*: Declares indexes, tables, and partitions for the module store.

### 2.2 APIs (served at `https://uape.dev/api/...`)
* **AsyncAPI Spec**: `https://uape.dev/api/asyncapi.yaml`
  * *Purpose*: Outbound audit and lifecycle events published via gRPC stream or local message buses.
* **OpenAPI Spec**: `https://uape.dev/api/openapi.yaml`
  * *Purpose*: Operator control plane and BFF gateway management interfaces.

---

## 3. Guidelines for Code Generation & Manifest Design

When writing code, manifests, or integrations for UAPE/DAIMON:

### 3.1 Contract Manifest Constraints
1. Every manifest MUST have a unique `$schema` pointing to `https://uape.dev/schemas/contract-manifest-1.0.json`.
2. All modules must specify their exact required capabilities (e.g., `networking: false`, `storage: ["inventory_db"]`). Under DAIMON OS, capabilities not declared in the manifest are strictly denied by the WASM runtime.
3. Every state mutation must yield a deterministic audit event conforming to the `audit-event-1.0.json` schema.

### 3.2 Rust/WASM Component Guidelines
1. Target the WASM Component Model (`wasi:cli` or custom `daimon` interfaces).
2. Avoid external networking inside standard modules; force communication through the configured `Gateway` API.
3. Keep module memory footprint low; optimal configurations operate on 2 vCPUs and 2 GB RAM.