Agentix Documentation

This is the entry point for using, extending, and evaluating Agentix. If you are new to the framework, follow the learning path in order. The research documents are kept separate so experimental claims do not leak into product guidance.

Learn Agentix

1. Getting started — set up the repository, inspect the sample application, declare a feature, dispatch a command, and add HTTP.
2. Core concepts — schemas, operations, ports, outcomes, events, invariants, application assembly, and the dispatch lifecycle.
3. HTTP adapter — routes, authentication, response mapping, and the Node listener.
4. Testing — deterministic operation tests, traces, port contracts, invariant checks, and replay.
5. CLI and generated index — inspect, graph, affected analysis, verification, scaffolding, and index semantics.
6. API reference — public package exports and behavioral contracts.
7. Releasing — coordinated versions, release pull requests, npm publishing, provenance, and first-release setup.

The complete runnable reference application is examples/framework-app. Its plain TypeScript counterpart is examples/plain-app; both share the same black-box acceptance contract.

Design and development

• Architecture is the frozen experiment-design record. Some implementation-status wording is historical; use core concepts and API reference for current behavior.
• Development guide covers setup, repository commands, change checklists, and evidence hygiene.
• Decision log records accepted tradeoffs and rejected alternatives.
• Limitations preserves the frozen threats-to-validity record; later mitigations remain documented separately rather than rewriting the intervention context.

Empirical study

These documents define the research intervention and must not be silently changed in response to results:

• Hypothesis and evaluation contract
• Agent-maintenance benchmark protocol
• Phase 5 readiness and Phase 6 blockers — historical gate snapshot
• Exploratory HTTP framework benchmark
• Benchmark subsystem

Runtime measurements and coding-agent maintenance measurements are separate. The exploratory HTTP result cannot establish that Agentix saves coding-agent tokens, files, or tool calls.

Release boundary

The five framework packages are public, ESM-only, pre-1.0 packages under the @agentix/* npm scope. They share one coordinated version and follow semantic versioning, but minor releases may contain breaking API changes until 1.0. Release automation publishes only built package artifacts; benchmark fixtures, results, examples, and sandboxes remain repository-only.