Menú
Prepare aiOS for production release and distribution. Use when hardening CI/CD, observability, security boundaries, packaging, deployment, rollback strategy, and operational readiness.
| name | release-readiness |
| description | Prepare aiOS for production release and distribution. Use when hardening CI/CD, observability, security boundaries, packaging, deployment, rollback strategy, and operational readiness. |
context/04-release-readiness.md first.Agent-facing interface to the Lago knowledge substrate. Provides Karpathy-style wiki operations (ingest, search, read, write, lint, wake-up, query) on top of Lago's event-sourced, content-addressed filesystem.
Create and maintain a control-system metalayer for autonomous code-agent development in any repository. Use when you need explicit control primitives (setpoints, sensors, controller policy, actuators, feedback loop, stability and entropy controls), repo command/rule governance, and a scalable folder topology that lets agents operate safely and keep improving over time.
Build or modify aiOS control-plane HTTP/SSE behavior. Use when changing apps/aios-api routes, request/response models, streaming/replay semantics, approval endpoints, or API compatibility guarantees.
Evolve core aiOS kernel behavior and contracts. Use when modifying crates aios-model, aios-events, aios-policy, aios-tools, aios-memory, aios-runtime, or aios-kernel, especially for event schema, lifecycle phases, capability checks, checkpoints, memory provenance, or session semantics.
Detect unused dependencies in Rust projects for cleaner Cargo.toml files and faster builds. Use when auditing dependencies, optimizing build times, cleaning up Cargo.toml, or detecting bloat. Trigger terms: unused dependencies, cargo-machete, dependency audit, dependency cleanup, bloat detection, cargo-udeps.
Run full workspace validation (format, lint, build, test)