# AXIOM-MESH Agent Instructions

> **Capability is not authority. Discovery is not permission. Connection is not permission.**

This file tells coding agents and automated contributors how to approach AXIOM-MESH. It does not grant repository, runtime, deployment, merge, or production authority.

## Installation

From a trusted checkout of the repository, use:

```bash
npm run setup
```

Repository: https://github.com/Zoverions/AXIOM-MESH

## Configuration

Start from the tracked `.env.example` when local configuration is required. Do not infer authority from present credentials, reachable services, installed tools, or successful prior access.

The supported privileged-effect path is `Gateway -> Hypervisor -> Sandbox -> Grid`. Do not create a parallel authority path around it.

## Usage

Before consequential changes, read the [README](https://github.com/Zoverions/AXIOM-MESH/blob/main/README.md), [agent entry](https://github.com/Zoverions/AXIOM-MESH/blob/main/AGENT-ENTRY.md), [contribution rules](https://github.com/Zoverions/AXIOM-MESH/blob/main/CONTRIBUTING.md), [capability registry](https://github.com/Zoverions/AXIOM-MESH/blob/main/mesh/config/capabilities.json), and [current threat model](https://github.com/Zoverions/AXIOM-MESH/blob/main/docs/security/CURRENT-BUILD-THREAT-MODEL.md).

Validate supported changes with:

```bash
npm run check
npm run release:verify
```

For a read-only authority assessment, use the [AXIOM Authority Auditor](https://axiom.zoverions.com/.well-known/agent-skills/axiom-authority-auditor/SKILL.md).

## Authority boundary

A request to draft is not permission to merge. Repository write access is not deployment authority. Passing CI is not production promotion. Missing or stale authority for a consequential external effect must not be converted into permission.