# 通用智能体底座

**Repository Path**: zkak/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**: 2
- **Forks**: 1
- **Created**: 2026-08-27
- **Last Updated**: 2026-10-21

## 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`

Current authority is [ARCH.md](ARCH.md), accepted [ADRs](docs/adr/), the target service DESIGN and
stable machine contracts. The frozen v0.6.0 technical route and
[development baseline](docs/platform-development-v0.6.0.md) are historical inputs; consult the
[clause supersession map](docs/technical-route-supersession.md) before applying their requirements.
Boundary or contract changes must update the current design and contracts before implementation.

Before any modification, read [ARCH.md](ARCH.md), [CLAUDE.md](CLAUDE.md), the target service DESIGN.md, then [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 application deployment rules.

## Current status

The current source and historical candidate evidence are distinguished in [docs/status.md](docs/status.md).
That page links the reproducible staging profile and module release gates. 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 [ARCH.md](ARCH.md); [docs/architecture.md](docs/architecture.md) is a navigation view. 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 application-owned deployment assets only.

## Skeleton

- `src/foundation/contracts/`: contract center.
- `src/foundation/service_kit/`: shared service utilities.
- `src/foundation/mcp/`: MCP (Model Context Protocol) infrastructure for M04-M08 service tools.
- `src/foundation/services/m01_api_gateway` through `m09_audit`: nine foundation modules.
- `deploy/manifests`: 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).

## Production cutover check

Production traffic remains fail-closed until an authorized operator supplies a protected cutover
manifest and all nine services pass live health and readiness probes:

```bash
export PLATFORM_PRODUCTION_MANIFEST=/secure/release/v0.0.2/production-manifest.json
make check-production
```

The gate validates the installed release version, HTTPS OIDC and service endpoints, private signing
key and trust-registry references, SHA-256-bound release evidence, and an approved change/rollback
record. It does not create credentials or approve a release. See
[deploy/production/README.md](deploy/production/README.md).


## M00 退役（2026-10-20）

M00 装配模块已移除，底座仅 M01–M09。项目业务资产由应用仓库拥有；通用发布描述位于 `deploy/manifests/`，演示流程只在 M02 测试夹具。M02 通过 `M02_WORKFLOW_REGISTRY_PATH` 显式加载部署登记，默认 `/run/m02/workflow_registry.json`，不再内置 demo。本文旧 M00 目录/冻结要求由 `docs/adr/0010-retire-m00-project-assembly.md` 覆盖；历史项目标识、URI、已发布版本和数据保留。

通用多任务智能体v8源码、合同与验收边界见[实施记录](docs/implementation/general-agent-v8.md)和[ADR 0009](docs/adr/0009-general-agent-research-tasks.md)。行为回归入口见[版本化评测](evals/general-agent-v8/README.md)；源码合并不代表已部署。


Skill 注册发布的 M01 管理入口、M02 持久部署审批与 M06 签名核验见 [注册发布手册](docs/runbooks/skill-publication-approval.md)及 ADR 0012。审批事实与正式业务流程状态独立，运行发布须另附真实验收证据。

## 政策索引二级标题增强

M05新入库载体二级标题复用已确认条款摘要与主体/领域标签，空组省略，引用保持固定原文；同固定版本的跨载体旧引用须重验双端证据、当前来源和授权。旧索引不原地改写，需发布后显式新入库成功才更新。实现和验收边界见 [本次交付](docs/implementation/policy-heading-enhancement-20261021.md)。