denies on NaN/missing; threshold setters and check-id collisions panic; **fails closed**. Not a security boundary. Spend: every `evaluate_request` inside a loop records into the `tokio::task_local!` `LoopScope
Verified** badge once the public key is uploaded to your GitHub account.
### Potential security issues
If you discover what appears to be a security vulnerability while working in this
codebase
check, gate, or threshold)
**Interlinked is a portable, per-tool-call quality and security standard for
agent-written code.** A local daemon sits in front of an agent's tool
What needs a deploy beyond push (`scripts/macapp/`, DMG, Sparkle, `infra/telemetry-worker/`, Homebrew): `docs/agent-rules.md`.
## API and security
- `/api/*` is public API: adding fields/endpoints is fine; renaming/removing/reshaping is a major bump.
- Read `SECURITY.md
design decisions, project structure, and code implementation must follow best engineering practices. Specifically:
### Security & Least Privilege
- Never use overly permissive settings (e.g. `chmod 0777`) as shortcuts. Solve permission problems
canonical path + file hash. Approval is stored outside the repo in `~/.hazmat/integration-approvals.yaml`.
## When making security-relevant changes
**Update docs/design-assumptions.md** if you change:
- The seatbelt credential deny list
- Network policy
/ue-integration-test` - Run integration tests
- `/build-deps` - Build plugin SDK dependencies locally and refresh ThirdParty binaries
### Security
- Never commit secrets, credentials, API keys, or tokens to the repository
- Never print or display
source zip of a GitHub release by `export-ignore` in `.gitattributes`.
## Releasing
The security fix only reaches users when the npm package is republished — updating the repo alone changes nothing
check # Fail if complexity exceeds threshold (CI)
make fmt-check # Verify code formatting
make security # Run security vulnerability checks
make sdk-test # Test SDK as consumer would use it
make
published measurement behind one ([AGENTS.md](AGENTS.md) cautions).
- The planner's exploration envelope is a security boundary
([ADR-0008](docs/adr/0008-planner-exploration-envelope.md)). Do not widen what
it permits without
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.