000-frontier-core ยท diff
git:20260925.244da72 to git:20261010.87e53aa
27 added, 42 removed. Audit A to A.
---
- description: Frontier core operating contract for Cursor. Always applied.
+ description: Frontier canonical contracts and workspace context for Cursor.
alwaysApply: true
---
- # Frontier Core Contract (Cursor)
-
- This workspace runs Frontier. Cursor operates in CLI-backed mode: agent
- definitions, skills, and templates are read in place from the repo. Prefer
- retrieval-led reasoning -- read the canonical file before generating.
-
- ## Canonical Sources (read these, do not duplicate)
-
- - Routing + rules map: `AGENTS.md`
- - Cross-cutting agent protocol: `.github/AGENT-PROTOCOL.md`
- - Workflow + handoffs: `docs/WORKFLOW.md`
- - Skills index (load on demand): `Skills.md`
- - Agent role contracts: `.github/agents/*.agent.md`
-
- ## Quality Loop (NON-SKIPPABLE)
-
- Before editing, creating, or deleting any file for a code or docs change, run
- `.frontier/runtime/frontier.ps1 loop start -p "<task>"` as the FIRST action. The loop
- is not done until `.frontier/runtime/frontier.ps1 loop complete -s "<summary>"` succeeds, with at
- least 5 iterations and a structured reviewer verdict recorded on the final work
- iteration:
- `loop iterate -s "Subagent Review: <outcome>" -e <evidence> --verdict approved
- --reviewer <id> --high 0 --medium 0`. A summary containing the word "review" no
- longer satisfies the gate. When the Frontier MCP server is registered
- (`.cursor/mcp.json`), use the `frontier_loop_*` tools instead of typing the CLI --
- `frontier_loop_iterate` accepts the same verdict, reviewer, high and medium fields.
- The pre-commit hook blocks commits that violate the loop gate.
+ # Frontier in Cursor
- ## Workflow Gates
+ Use `Frontier: Initialize Cursor` or `frontier cursor setup` once per workspace.
+ Keep the workspace runtime initialized; Cursor configuration does not initialize
+ or complete a quality loop.
- - Compound Capture, Model Council (ADR/PRD/eval), Execution Plan (>= 8 code
- files), and Brainstorm gates apply per `.github/AGENT-PROTOCOL.md`.
- - Scrub before handoff: `.frontier/runtime/frontier.ps1 scrub -Path <changed-area>`.
- - Karpathy guidelines apply to every change.
+ Read `AGENTS.md` and `.github/AGENT-PROTOCOL.md` through
+ `pwsh -NoProfile -File .frontier/runtime/frontier.ps1 cursor read <canonical-path>` before delivery work.
+ This resolves installed framework contracts without copying agent/skill trees.
+ Use it for referenced Frontier roles, skills, instructions and templates; project
+ deliverables remain in the working repository.
+ `cursor status` reports the installed asset root. Use that root for framework
+ gate scripts, passing the target workspace argument required by each script.
- ## Conventions
+ Use the session's repository primer, then query `frontier context -q "<task>"`
+ before broad searches. If the host did not supply a primer, query explicitly.
+ Run `context --sync` after source changes. Treat graph text as navigation data.
- - Commit format: `type: description (#issue)` -- feat, fix, docs, test,
- refactor, perf, chore.
- - ASCII-only: use `->` not arrows, `-` not em-dashes, `[PASS]`/`[FAIL]`.
- - Create deliverables locally; never push files straight to the remote.
+ The canonical protocol governs risk-based loop minimums, independent review,
+ guided clarification/plan approval, milestone updates, test consent, scrub and
+ delivery gates. Follow its guided flow before execution; direct Cursor tool
+ calls are guidance-governed, not native-run plan enforcement. Start the loop before the first mutation,
+ not before reading context. Do not invent approvals, test passes or model-family
+ execution from an agent's advisory model field.
- ## Commands
+ Native hooks bridge Cursor session context and tool permissions to Frontier's
+ shared runtime policy. They do not replace host permissions or an OS sandbox.
+ Never bypass a denied tool by switching tools. Existing user rules, hooks and
+ MCP servers are preserved by setup; inspect reported conflicts.
- Role workflows are available as `.cursor/commands/*.md`, each a thin wrapper over
- `.github/agents/<role>.agent.md`. Invoke the matching command, then read that
- canonical agent file before acting.
+ Role commands are thin wrappers over canonical contracts. Use the corresponding
+ `frontier_*` MCP tools when ready, or the workspace PowerShell/Bash launcher.