Field Manual, Laboratory, Codex, and Console
Choose the right knowledge or observability surface and recognize experimental material.
Field Manual, Laboratory, Codex, and Console
These surfaces serve different kinds of truth.
| Surface | Owns |
|---|---|
| Field Manual | Stable instructions for understanding and operating active behavior. |
| Laboratory | Experiments, research notes, prototypes, open decisions, and unresolved models. |
| Codex | Internal developer contracts and implementation documentation. |
| Console | Runtime observability and system events. |
| Operator Command Center | Current operational state, warnings, readiness, and actions. |
When to use the Laboratory
Use the Laboratory when you are authorized and need to inspect the reasoning, model, evidence, or unresolved questions behind a system.
An experimental Manual entry must say so visibly and link to its stable Laboratory note. Active operating steps belong here only after the owning route and contract support them.
When something goes wrong
Start with the owning route, then the Field Manual's troubleshooting procedure. Operators may use Console events and Command Center state. Developers may consult Codex contracts. Do not use a Laboratory prototype as a production repair tool.
The architectural boundary is expanded in System Architecture.
Canonical terms
Definitions used here
- Field Manual
- Stable user and operator instructions for understanding and operating active Nysa behavior.
- Laboratory
- The experimental knowledge system for research, prototypes, open decisions, and unresolved models.
- Codex
- Internal developer and contract documentation, distinct from user operating instructions.
- Console
- The runtime observability and diagnostics surface; it reports events rather than teaching workflows.