Get to first run quickly
Use the quick start for install, CLI examples, PowerShell flows, and the shortest route to a working orchestrator.
Installation, first run, CLI and PowerShell usage, architecture and race-condition control, benchmarks, security, enterprise evaluation, audit logging, integration references, AI tool-use files, community policies, and licensing are all collected here.
Start with setup, the control model, and release history.
Use the quick start for install, CLI examples, PowerShell flows, and the shortest route to a working orchestrator.
Review architecture, AuthGuardian, trust levels, and audit schema to understand how state, permissions, and workflow boundaries are enforced.
Check the security policy, benchmarks, and changelog together to verify support windows, release cadence, and operational discipline.
These are the main files a technical evaluator, implementer, or security reviewer will actually read first.
Installation, first run, multi-framework setup, CLI usage, PowerShell and Python script workflows, and the shortest path from package install to a running orchestrator.
The race-condition problem Network-AI solves, the control-plane components, FSM journey design, delegation handoff protocol, and the structure of the orchestration layers.
Provider performance, rate-limit behavior, local GPU and self-hosted deployment guidance, and the `max_completion_tokens` sizing rules that prevent silent truncation.
Supported versions, vulnerability reporting, the security module, permission system, trust levels, audit trail, scanning posture, and disclosure policy.
A fast evaluation path for architects and technical buyers covering offline operation, auditability, security review posture, stability policy, and integration entry points.
An end-to-end integration walkthrough for technical leads, from discovery and agent inventory through phased rollout, framework mapping, validation, and common mistakes.
These files explain how the control plane behaves, how access is scored, how events are logged, and how the ecosystem plugs into the orchestrator.
The append-only audit trail specification, including the event envelope, event types, permission request fields, denied-request scoring payloads, and lifecycle events.
The full permission-wall reference, including weighted scoring, thresholds, token lifecycle, default restrictions, and audit logging behavior for protected resources.
The agent trust model used by AuthGuardian, from default trust levels through trust bands, approval impact, and guidance for introducing new agents safely.
The adapter architecture for plugging in existing frameworks, custom handlers, and mixed agent stacks without locking the system to a single ecosystem.
The public adopters list for organizations and open-source users, including the process for adding yourself through a pull request.
Three repository-root integration files are already included for tool use, custom GPT actions, and Claude project configuration.
Drop directly into a Claude API tools array or compatible Codex-style tool-use integration to expose Network-AI operations.
Import directly into the GPT editor as a Custom GPT Action spec for swarm delegation, state inspection, and orchestration endpoints.
Paste into Claude Projects custom instructions to configure the orchestrator agent behavior without requiring the MCP server.
These files explain how the project is governed publicly and what contribution quality bar the repository expects.
Professional standards, unacceptable behavior, enforcement scope, and reporting paths for the project community.
Issue-first contribution workflow, test and type-check requirements, security expectations, documentation updates, and review criteria.
Permissive licensing with rights to use, modify, and distribute the software, provided the copyright and permission notice stay with the code.
Use the security policy, advisories, changelog, and benchmark docs together when evaluating maintenance discipline and production readiness.
These sections cover the rest of the public repository documentation.
Read the repository overview and the runnable examples guide in site format.
Review version history, release cadence, and recorded changes.
Operator guidance and machine-readable manifests for Claude, Codex, and skill-based integrations.
Reference material for architecture, state layout, and MCP planning.
Ecosystem and launch-positioning documents for the broader project story.