# LLMS — Public agent orientation for openOODA
File: website/llms.txt

This file is the public LLM manual at https://openooda.org/llms.txt.
The name `.txt` is the llmstxt.org URL. The content follows `.oot` law.
Canonical agent front door: github.com/openOODA/openOODA/ANCHOR.oo.

openOODA is a capability-secure systems language. The compiler checks
source ahead of time. Privileged work needs an unforgeable cap token.
Public home: https://openooda.org loads `.github/docs/HOME.oot`.

## 1. File law

- Code: `.oo`. Documents: `.oot`.
- Every `.oo` and `.oot` file is at most 256 lines.
- Do not create `.py`, `.js`, `.ts`, `.rb`, or `.pl`.
- Do not create `.sh` except the two host scripts named in RULES.oot.
- Do not create `.md` except the governance repo README.md.
- Product `.oo` files use a 4-element Academy header: Title, Logline,
  Setup, Beats.
- `.oot` files use a 2-line header: `# Title` and `File:`.

## 2. Read order (governance repo)

Start at `openOODA/ANCHOR.oo`. Then:

1. `RULES.oot` — 23 laws. They do not change.
2. `NORTHSTAR.oot` — architecture, grammar, AST, type system.
3. `rfcs/ANCHOR.oo` — 7 accepted RFCs, numeric order.
4. `practices/ANCHOR.oo` — 8D red team, OODA workflow, release.

To propose a change, copy `rfcs/0000-template.oot`.

## 3. 13-repo polyrepo (tags 2026-09-12)

| Repo | Role | Tag |
|------|------|-----|
| openOODA | Governance: laws, RFCs, practices | v2.10.35 |
| oodar | C host substrate (`oo_*`, `gcc oodar.c`) | v4.0.29 |
| oodac | Compiler (lex, parse, check, emit) | v0.2.53 |
| std | Standard library, 8 domains | v1.0.41 |
| ooda | Workflow driver (`ooda` binary) | v0.2.29 |
| install | apt, dnf, pacman, install.sh | v0.1.30 |
| opm | Package manager | v0.8.17 |
| catalog | Public package list for `opm search` | v0.0.15 |
| lsp | Language server | v0.6.32 |
| mcp | MCP server, 23 tools | v0.6.30 |
| blackbox | Operational Logistics: Agent-native execution flight recorder and crash autopsy engine | v0.0.14 |
| website | This site | v1.2.39 |
| .github | Org profile and shared workflows | — |

Do not prefix another `openOODA/` segment onto paths in ANCHOR.oo.

## 4. 20 capability tokens (NORTHSTAR §4.2)

`FsReadCap` `FsWriteCap` `FsCap` `NetCap` `TcpCap` `UdpCap` `BindCap`
`SysCap` `ProcessCap` `EnvCap` `TimeCap` `RandCap` `AllocCap` `ArenaCap`
`ThreadCap` `GpuCap` `FfiCap` `SignCap` `MetricsCap` `CompilerReadCap`.

Pass a borrowed token (`&FsReadCap`). Missing token fails compile
(`E_CAP`) or exits `ERR\tcap\t...`. Zero ambient authority.

## 5. RFCs and practices

RFCs: 0001 capability security, 0002 design by contract, 0003 file
format, 0004 engineering model, 0005 tactical subsystem template,
0006 auto-release, 0007 blackbox flight recorder.

Practices: `8d-red-team.oot`, `ooda-workflow.oot`, `release.oot`.
Practices evolve. RULES and accepted RFCs do not.

## 6. Install

```
curl -fsSL https://openooda.org/install.sh | bash
```

`install/VERSION` is the single exception to the no-VERSION-file
rule (`RULES.oot §1.24`): the install tarball cannot reach git
history at install time, so `install.sh:1093` reads the version
from this file. The file matches the hand-pushed `v0.1.x` tag.

## 7. Cross references

- Front door: `openOODA/ANCHOR.oo`
- Laws: `openOODA/RULES.oot`
- Architecture: `openOODA/NORTHSTAR.oot`
- Do not read deleted boards: START, MOONSHOTS, ROADMAP, SHIPPED,
  FORMAT, SECURITY, WORKFLOW, QUICKREF, CONSTRAINTS, STRUCTURE_EM,
  REDTEAM as ALLCAPS roots. Those files are gone.