# 通用智能体底座

**Repository Path**: rayiiiii/universal-ai-agent-base

## Basic Information

- **Project Name**: 通用智能体底座
- **Description**: 一个通用智能体底座，可容纳不同业务领域项目。
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 1
- **Created**: 2026-08-27
- **Last Updated**: 2026-08-30

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# agent-platform-foundation

CPython 3.12.14 workspace for the agent platform foundation.

Canonical local path: `/home/user/projects/agent-platform-foundation`.

Known aliases:
- `通用智能体底座项目`
- `智能体应用平台底座`
- `agent-platform-foundation`

This repository is constrained by `agent-platform-foundation-technical-route-v0.6.0` and the
project-level implementation baseline in [docs/platform-development-v0.6.0.md](docs/platform-development-v0.6.0.md).
Any route, module responsibility, assembly, or frozen-item change must first be
updated in that document and confirmed before code changes.

Before any modification, read [docs/development-handbook.md](docs/development-handbook.md).
All agents and developers must update development documentation and contracts before
implementation when a change affects module boundaries, routes, protocols, events,
error codes, scopes, Resource URI, audit fields, Provider boundaries, Skill/Tool
manifests, or M00 assembly rules.

## Current status

This branch is the platform release candidate. The reproducible staging profile and the module
release gates are documented in [docs/status.md](docs/status.md). Formal production cutover is a
separate operations/security change: it requires production OIDC, rotated RFC 9421 keys and trust
registries, an approved M09 endpoint, and disaster-recovery approval. Staging evidence must not be
reported as production traffic readiness.

For architecture and ownership, start with [docs/architecture.md](docs/architecture.md). For the
full reading order, historical decisions, and module design documents, use [docs/README.md](docs/README.md).
The long-form reconciliation log remains available at [docs/project-development-memory.md](docs/project-development-memory.md);
its dated entries are evidence and history, not the current status source.

## Foundation Rules

- Only M01-M09 foundation modules are allowed.
- Frontends and external systems may call only M01 `/api/v1/*`.
- M02-M09 expose only internal service surfaces and must not be called directly by frontends.
- Cross-module integration must depend on definitions under `src/foundation/contracts`.
- No shared ORM models, cross-module private imports, or cross-database foreign keys.
- Pending-PoC products must stay behind Provider interfaces with Fake implementations for tests.
- M06 owns Skill versions and assets only.
- M08 owns Tool execution and policy only.
- Project-specific business rules and Skills belong under M00 project assembly packages only.

## Skeleton

- `src/foundation/contracts/`: contract center.
- `src/foundation/service_kit/`: shared service utilities.
- `src/foundation/mcp/`: MCP protocol seams used by approved Tool Providers.
- `src/foundation/services/m01_api_gateway` through `m09_audit`: nine foundation modules.
- `src/foundation/projects/m00_template`: project assembly template only.

## Runtime Baseline

- Python: `>=3.12,<3.13` (CPython 3.12.14).
- Runtime relational database: MySQL 8.4 LTS.
- Persistence: SQLAlchemy 2.x + Alembic, private per-module metadata and migrations.
- SQLite is test-only and must not be used as production acceptance evidence.

## Local Check

```bash
python3.12 -m compileall src
```

## Staging checks

```bash
make test
make run-staging-m06
make run-staging-m08
```

The staging launchers require MySQL-backed facts, signed ServiceAuth, and non-local Providers;
they never create production schemas implicitly. See [deploy/staging/README.md](deploy/staging/README.md).