Product

This area describes the product LoopX is becoming. It separates durable foundations from runtime-specific experiences, operator surfaces, use cases, and staged roadmaps so experimental observations do not masquerade as stable contracts.

Current Product Truth

• Product vision: long-running Loop Agents, maintainer-first management, evidence, and open-source direction.
• Core control-plane graphs: the product and runtime map for state, interactions, and bounded contexts.
• Release readiness: the currently supported v0.x install and compatibility boundary.
• Release note template: the copy-ready release decision summary, product groups, optional-capability guidance, validation, and bilingual attribution format.
• Public adoption loop: a public-safe path from external attempt to inspectable feedback.
• Domain capability packs: what belongs in the generic control plane and what requires an explicit domain pack.
• Scenario capability gap map: reusable capability increments across issue-fix and other scenario signals.

Product Areas

• Foundations: agent identity, planning, reward, replanning, and server/client shape.
• Runtimes: Codex CLI, Codex App, and future runtime experiences.
• Operator surfaces: status, observability, frontstage, and presentation boundaries.
• Use cases: auto research, issue/PR work, cross-runtime review, and office operations.
• Roadmaps: proposed milestones that are not current runtime contracts.
• Migrations and history: naming and state migrations.

Implementation-facing schemas belong under docs/reference/. Architecture proposals belong under docs/architecture/. Public outcomes belong under docs/showcases/.