Rules

<security_requirements type="critical"> </security_requirements>

This project uses Changesets for automated versioning and release management.

TrustGate emits one OTLP **log record** per completed request (`pkg/infra/telemetry/otlp`). Operators do not just read those records — they **load** them into typed tables and build billing, usage and reporting on top. The attribute keys are effectively column names.

Cursor IDE rules and conventions for AI-assisted development.

The Memory Files consists of required core files and optional context files. Files build upon each other in a clear hierarchy: PB[prd.md] --> PC[tech_context.md] PB --> SP[architecture.md] SP --> TC[tasks_plan.md]

This rule provides guidance for running brutal audits after completing a development phase or milestone.

Use this rule when changing **`agents/analytics/`**, analytics **ORM tables**, or **`RecordEnriched`** batch fields consumed by the analytics agent. **Epic:** #175 · **Sub-issues:** #184 (Steps 10–11), #185 (Step 12), #186 (guardrails + Step 13).

The **Implement** phase of [`../../workflow-rpi.md`](../../workflow-rpi.md). Goal: turn the approved `docs/plans/descriptive-name.md` into working code, phase by phase, without letting the context balloon.

def __init__(self, config: ServerConfig): self.clients: Dict[str, Client] = {} self.tools: Dict[str, Tool] = {} self.logger = setup_logger(__name__) async def handle_message(self, message: Message, client: Client) -> None:

workflow_dispatch: {} group: ${{ github.ref }}-${{ github.workflow }} cancel-in-progress: true cleanup_old_workflows: runs-on: ubuntu-latest uses: dmvict/clean-workflow-runs@v1 token: ${{ github.token }}

This is a Node.js CLI application that takes a trust indicator set (JSON) and a trust profile (YAML)and evaluates the trust indicator set against the trust profile, producing a trust report either in JSON, YAML or HTML format.

**Read `AGENTS.md` at the repo root first.** It holds the durable contract: layout, determinism rules, pgwire protocol gotchas, test tiers, commit conventions, and what-not-to-do. This file is a short Cursor-facing summary that points at the canonical

Follow this structure for all [.astro components](mdc:src/components/): // TypeScript frontmatter import type { Props } from './types'; import { getTranslation } from '@/i18n'; interface ComponentProps {

requires-python = ">=3.10" [project.optional-dependencies] target-version = "py310" python_version = "3.10"

Use when the task is documentation alignment, docs drift review, or safe docs cleanup. Canonical policy: `.hawp/kit/references/docs-alignment.md`

Canonical multi-agent rules: `@AGENTS.md`, then `@PROJECT_BIBLE.md`. Full lockdown: `CLAUDE.md §1–3` (that file wins on any conflict). This `.mdc` is the Cursor-specific pointer.

Cursor IDE rules and conventions for AI-assisted development.

Function/method calls use a space before `(` — see `.cursor/rules/code-style.mdc`: $content = QueryBuilder::for ($callback ()); array_map (fn (RoleEnum $role) => $role->value, RoleEnum::cases ());

Cursor IDE rules and conventions for AI-assisted development.

**Every new feature MUST include a `risks.yaml` file with initial risk assessment.**

Cursor IDE rules and conventions for AI-assisted development.

1. **After analyzing the prompt** 2. **Whenever you modify code** 3. **Sections order**