Cursor

---
description: Cordango workspace rules
alwaysApply: true
---

This is a Cordango workspace. Apps under `apps/` are defined by semantic source: `.cordango.yaml`
files describing entities, workflows, roles and screens.

- Run `cordango inspect` before changing anything. Never read the App Definition schema and never
  read the cordango binary; `cordango vocabulary` is the authority on what may be written.
- `cordango check` calls no model and touches no database. Run it after every change.
- Never edit `.cordango/` (the dotted directory). It is build output.
- Use stable keys. Renaming an entity or field key is not supported.
- One aggregate per change.
- Do not commit. A person reads `git diff` and stages it.

---
globs: apps/**/*.cordango.yaml
alwaysApply: false
---

- `fields` is a map keyed by field key, not an array.
- Run `cordango vocabulary field` rather than guessing which properties a field type accepts.
- Run `cordango fmt` after hand-editing so the diff shows meaning, not whitespace.

Add a "priority" field to the ticket entity: a select with low, normal, high and urgent,
defaulting to normal. Show it as a column on the tickets table.

Run cordango check when you are done. Do not commit.

Build a support desk app in this workspace.

The job: a small team receives customer problems, works them, and needs to see what is overdue.
Tickets belong to a customer company, have an owner, move through new / in progress / waiting on
customer / resolved, and carry a priority.

Run cordango inspect first and tell me which core apps already exist, so we reference them instead
of modelling our own companies. Show me the plan before writing files.

Then work one aggregate at a time, running cordango check between each.

# .cursorignore
out/
.cordango/