Keep protections for credentials, unsafe paths, and settings the user explicitly requests.
- Prefer straightforward code and tests for real behavior.
- Mention another `openai/` repository in comments or pull request descriptions
time context, not required startup reading.
- Treat source code and tests as authoritative. A brief's unknowns and review items are verification gaps, not automatic requirements.
- Prefer the narrowest quiet
Workflow`**. Business rules stay in code
(a `$100` threshold routes low-value expenses straight to auto-approval); only
high-value expenses reach an LLM `review_agent`, which then **pauses
Start-here** column names the exact real function to read — open it; that
production code is the lesson.
| Interface | Start-here (real function) | Transferable vs Horizon-specific | Deep-dive |
|---|---|---|---|
| Environment
Agent guidance
Guidance for AI agents (Claude Code, Copilot, Cursor, etc.) working in this
repository. See `CONTRIBUTING.md` for the full contributor workflow.
## Committing
Run the `pre-commit` hook before committing
definitions override built-in agents of the same name.
```json
{
"agents": {
"review": {
"description": "Senior codereviewer focused on correctness and security",
"model": "anthropic/claude-opus-4-6",
"temperature": 0.3,
"prompt": "You are a senior
kernel**: it defines the architecture and is held to a higher bar than UI/gatekeeper code. Reviewers read *every line* of `workshop-backend` and of API changes in `workshop-shared
hand; regenerate it with `scripts/regenerate-node-types.sh` after
changing the pinned swift-syntax version, then review the diff alongside the
mapping in `extractor/src/languages/swift/swift.rs`.
## AST Mapping
- The target AST shape is described
thread.
### Accountability
- Pure code-agent PRs are **not allowed**. A human submitter must understand and defend the change end-to-end.
- The submitting human must review every changed line
headings.
- Keep headings `font-medium` with `tracking-tight` where appropriate.
- Use `JetBrains Mono` for code, commands, and monospace UI.
- Keep labels and link text in sentence case.
- Prefer light borders
reasoning from the code alone.
- When debugging a failure, start from the incident or issue Polylane recorded: it carries the evidence an investigation already gathered.
- Polylane reviews pull requests
packages plus the TypeScript SDK: core protocols in `praisonaiagents/`, agentic terminal CLI in `praisonai-code/`, bots/gateway in `praisonai-bot/`, LLM fine-tuning + agent training in `praisonai-train/`, browser automation
ExitPlanMode` via hooks, letting users approve or request changes with annotated feedback. Also provides codereview for git diffs and annotation of arbitrary markdown files.
> **Reusing the document UI (theme
session, or hand the diff to a
subagent that did not write the code. An agent reviewing work it produced in
the same session re-reads its own intent rather
first. We design systems and use agents to implement them — this is not vibe coding. The product provides safe, sandboxed runtimes for autonomous AI agents, and the project itself
upstream code. These patches are stored in the `patches/` directory and are applied during the build process. When updating these dependencies, it's important to review and update the corresponding
become dangling
See `README.md` §Safety Pattern Catalog for detailed When/Why/How for each pattern.
## CODEREVIEW RULE
When reviewing changes to streams code, check whether the change requires updates