VERSION`, a manifest-wide
native `api:` match, or version literals on unrelated payloads. Documented surfaces stay additive:
- Hook payload data is added as **keyword fields**; callbacks are signature-inspected
plugin Cordis agent harness. Read [docs/architecture.md](docs/architecture.md) before changing `packages/`; follow [docs/AGENTS.md](docs/AGENTS.md) for documentation.
## Pre-stable APIs and released Session data
Public APIs are pre-stable; update every consumer
proposals and decision records that preserve rationale, alternatives, consequences, and required verification. Follow the [documentation standard](../../docs/AGENTS.md) and the [Agent Note rules](README.md).
**Every new Agent Note triggers a supersession
repair, delete, or move a sealed artifact; use an active Agent Note or current documentation for new decisions and facts.
The archival change may only relocate a complete English/Chinese/sidecar triplet
AGENTS.md — The documentation standard
This file defines document structure, Markdown tiers, writing rules, and `verify-doc-budgets` ceilings. Use [dsh-doc](../.agents/skills/dsh-doc/SKILL.md) for placement and validation, and [dsh-prose-standard
subsystem ownership through a canonical English page link or justified [exemption](../scripts/verify-subsystem-pages.ts).
- Package READMEs document model, token, and KV-cache effects using the [canonical Model Experience format](../docs/cookbook/adding-a-package.md#4-write
injected values, store state, and provide contributions use these values. Transient file-read and document-preview content may also carry `Uint8Array`: published buffers are borrowed read-only, copied before Worker
through `devDependencies`; examples may load them explicitly.
- Experimental status does not relax engineering, security, documentation, lifecycle, testing, invariant, or snapshot requirements.
- Publishing an experimental package does not promote
AGENTS.md — Documentation website adapter
Follow the [root instructions](../AGENTS.md), the [documentation standard](../docs/AGENTS.md), and the [documentation workflow](../.agents/skills/dsh-doc/SKILL.md).
## Keep documentation content out of this tree
`website/` owns only VitePress configuration
Multi-Chat Architecture
> Node runtime service construction is documented separately in [`node/serviceBootstrapping.md`](node/serviceBootstrapping.md).
> Host startup timings, process-lifetime correlation, and session workload counts are documented in [`PERFORMANCE.md`](PERFORMANCE.md).
> **Status: COMPLETE
tools registered by Agent Host. This internal debugging setting assumes those values use the documented string shape.
> **Launch-time freeze.** The SDK accepts a system message only at session create/resume
calling `onKeyDown` as a safety net; every handler on a raw ` `/` `, a container, or `document` must use `isKey` itself. That atom-level guard is deliberately unconditional, so a modifier chord
support
- **Frontend** (`frontend`): Next.js React application
- **Shared Libraries** (`autogpt_libs`): Common Python utilities
## Component Documentation
- **Backend**: See @backend/AGENTS.md for backend-specific commands, architecture, and development tasks
- **Frontend**: See @frontend/AGENTS.md
React Best Practices
**Version 1.0.0**
Vercel Engineering
January 2026
> **Note:**
> This document is mainly for agents and LLMs to follow when maintaining,
> generating, or refactoring React and Next.js codebases
Documentation Guidelines
## Block Documentation Manual Sections
When updating manual sections (` `) in block documentation files (e.g., `docs/integrations/basic.md`), follow these formats:
### How It Works Section
Provide a technical explanation
explicit and bounded. Do not perform external I/O inside an open transaction unless a documented consistency contract requires it.
- Read configuration through `configs.dify_config`, access storage through `extensions.ext_storage.storage`, and route
package's `uv` environment and Pydantic v2 APIs. Inspect current dependency source or official documentation before integrating, implementing, or mocking an API whose runtime contract is not established locally.
## Tests
Global development guidelines for the LangChain monorepo
This document provides context to understand the LangChain Python project and assist with development.
## Corridor security analysis
When Corridor's `analyzePlan` tool