# agentsop.ai/org

> Organization-level facts: who is who, which agent does what, shared CI/CD, and the pinned map of what the organization uses.

Repository: [repos] org in ~/.config/agent-sop/config.toml. No config file: read https://agentsop.ai/start/llms.txt.

## Read there

- `org.json`: The SOP source and the capability map, one commit per entry. Read first.
- `governance/agents.json`: The agent roster: one bot identity per harness, active or retired.
- `governance/repos.json`: The governed repositories and each one's recorded deltas.
- `governance/organization-profile.json`: The secret-free profile that machine bootstrap reads.
- `README.md`: The repository's own index and how to validate it.

## More

- [llms-full.txt](https://agentsop.ai/org/llms-full.txt): What each file answers and what to do when one is missing.

## What each file answers

- org.json: which SOP repository and which capabilities, each at one commit. Read it before any other file here.
- governance/agents.json: which bot identity belongs to which harness, and whether it is active.
- governance/repos.json: which repositories the procedures govern and what each one varies.
- governance/organization-profile.json: what a new machine needs to know, without secrets.

## When something is missing

- No config file: go to https://agentsop.ai/start/llms.txt; do not guess an organization.
- The org repository is unreadable: report the pointer and the error; do not fall back to another organization.
- org.json fails validation: report it; do not repair it from memory.
- A capability a procedure names is not in org.json: report which side names it and stop at that step.