Operating model for fit-for-purpose, consistent agent curation and explicit runtime activation.

ai4X is an operating model for agentic AI work. It exists to make agent work explicit, reviewable, and reusable — across any "bring your own agent" platform (#byoa).

Important

What sets ai4X apart

1. Need-first discovery — A structured interview process identifies the user's actual needs (why and what, not how). The result is a declarative requirements set that captures intent, not implementation.
2. Curated agentic fulfilment — From that requirements set, ai4X identifies the cognitive capabilities needed and assembles them as a curated agentic team with an explicit collaboration model — declaratively, reproducibly, and client-agnostic.

Rather than hiding behavior in ad hoc prompts, implicit local setup, or client-specific glue, ai4X brings declarative agent definition, deterministic materialization, and explicit client activation together in one coherent command surface.

In that model, agent creation and activation follow a clear lifecycle:

1. define what an agent is
2. materialize what the agent needs
3. activate it for an explicit client context

That makes agent work easier to understand, easier to reproduce, and easier to evolve with discipline.

ai4X is also a reference implementation of a strict agent-first development model and an agent-guided documentation model for human-facing onboarding and support. (click to expand)

Operational implications:

• Deterministic checks are handled programmatically through TypeScript tests, shell checks, and validation commands such as verify and doctor.
• Higher-order semantic review, judgment, and proposal assessment are intentionally designed for execution with agentic AI actors.
• In this model, developer and operator roles are primarily modeled as agentic AI roles.
• Documentation is authored for human consumption but designed for agent-mediated delivery — users ask an agent rather than reading docs directly.
• doc/usr/ is the direct human-facing documentation surface.
• doc/agn/ is the agent-facing onboarding and navigation surface.
• doc/arc/ is human-readable architecture and system-reference documentation.
• adm/gdl/dev/ is agent-facing development governance.
• adm/gdl/ops/ is agent-facing operations governance.

ai4X is, in that sense, built by agentic AI agents for agentic AI agents.¹

Core Model

• curate writes declarative, client-agnostic agent artifacts
• spawn materializes and activates an agent for an explicit client
• doctor validates configuration, declaration, and spawn-readiness

Principles

• explicit configuration
• explicit command inputs
• client-agnostic declarations
• project-local runtime artifacts
• deterministic validation before activation

Configuration

• Global config: ~/.config/ai4x/config.yaml
• Project config: <project>/.ai4x/config.yaml

Contributing

See CONTRIBUTING.md.

License

See LICENSE. © 2026 nemron (#hgtt)

Footnotes

1. #eyodf = "eat your own dog food". ai4X applies its own agent-first development and operations model to itself. ↩