Portable PAI Core.
PAIOS — переносимое ядро Personal AI Infrastructure: память, routing, identity, judge, capability registry и governance-правила.
Claude Code, Codex, Pi, OpenCode и будущие рантаймы не являются фундаментом. Они становятся сменными контурами, подключёнными к Core.
PAIOS вдохновлён Personal AI Infrastructure Дэниела Мисслера и его рамкой PAI как Life Operating System:
Но это не форк. Daniel PAI сознательно остаётся Claude Code native. PAIOS идёт в другую сторону: ценность PAI выносится ниже любого одного хоста в переносимый Core.
Философская основа PAIOS — TELOS: движение человека от текущего состояния к идеальному. Модели, провайдеры и рантаймы — не центр системы, а способности, которые служат человеческой траектории.
Документация:
- docs/ru/architecture.md
- docs/ru/host-as-contour.md
- docs/ru/capability-contract.md
- docs/ru/telos.md
- docs/ru/private-boundary.md
PAIOS is a host-independent core for Personal AI Infrastructure: memory, routing, identity, judge, capability registry, and governance rules.
Claude Code, Codex, Pi, OpenCode, and future runtimes are not the foundation. They are replaceable contours attached to the Core.
PAIOS is inspired by Daniel Miessler's Personal AI Infrastructure project and its framing of PAI as a Life Operating System:
- https://github.com/danielmiessler/Personal_AI_Infrastructure This is not a fork. Daniel's PAI is intentionally Claude Code native. PAIOS takes a different path: PAI value moves below any single host into a portable Core.
The philosophical basis of PAIOS is TELOS: helping the person move from current state toward ideal state. Models, providers, and runtimes are not the center of the system; they are capabilities in service of the human trajectory.
Documentation:
- docs/en/architecture.md
- docs/en/host-as-contour.md
- docs/en/capability-contract.md
- docs/en/telos.md
- docs/en/private-boundary.md
task -> privacy -> capability -> runtime -> model -> artifact -> judge -> apply
capability = role + privacy + provider + model + runtime + fallback + judge + contract
capabilities.example.yaml is the first working registry artifact. It is
generic, human-readable, and validated by a small script.
Real user-specific capability registries must live outside the public repository
or in ignored local overlays such as capabilities.local.yaml.
PAIOS stores no personal data by design. The repository contains Core code, schemas, contracts, docs, and anonymized examples only.
User-specific overlays such as real capabilities, identity, TELOS, memory, provider decisions, paths, and notes must stay outside the repository or in ignored local files.
PAIOS стартует на TypeScript + Bun.
Почему:
- совпадает с уже сложившимся стилем PAI tooling;
- удобен для CLI-first разработки;
- хорошо работает с JSON/YAML contracts, schemas, MCP и adapters;
- снижает порог входа для участников;
- удобен для open-source ревью и чтения кода;
- позволяет быстро развивать Core до появления задач, которым нужна низкоуровневая оптимизация.
Начальный стек:
- Core/CLI: TypeScript + Bun;
- Registry: YAML;
- Contracts: JSON Schema;
- Tests:
bun test, когда появятся test modules.
Это прагматичный выбор первого этапа, а не постоянное ограничение. Будущие модули могут использовать Rust, Go или Python, если конкретная capability этого потребует.
PAIOS starts with TypeScript on Bun.
Why:
- it matches the existing PAI tooling style;
- it is practical for CLI-first development;
- it works well with JSON/YAML contracts, schemas, MCP, and adapters;
- it keeps the contribution barrier low;
- it is open-source friendly and easy to review;
- it lets the Core evolve quickly before any low-level optimization is needed.
Initial stack:
- Core/CLI: TypeScript + Bun;
- Registry: YAML;
- Contracts: JSON Schema;
- Tests:
bun testwhen test modules appear.
This is a pragmatic first-stage choice, not a permanent constraint. Future modules may use Rust, Go, or Python if a specific capability needs them.
bun run validate