Made on
Tilda
Conventions screen → + Create.
| Field | What to enter |
|---|---|
| Name | A short name for the convention |
| Description | The convention text. The agent receives it in full, so it has to be applicable without further explanation |
| Severity | must is mandatory, should is recommended, note is a note |
| Category | The area it covers: code, architecture and others |
| Scope | Entity for specific entities, Project for the whole project, Path for a location in the file tree |
| Audience | Who it is for. A review convention is checked during review and isn't delivered to the agent writing code |
| Binding conditions | Binding conditions in JSON, for example a path match |
If a convention has zero bindings, the agent won't receive it. Check the binding count on its card. After renaming or moving code, click Rebind.
Knowledge screen: decisions (decision), notes (note), changelogs (changelog), diagrams (diagram) and procedures (procedure). Entries are created by people and agents. An entry is delivered to the agent when it works with linked code. If the card shows zero linked entities, the entry isn't delivered: specify the files and modules it relates to.
Entries live on git branches. The branch picker in the header shows that branch's entries; the count for other branches is shown separately.
Knowledge review screen. Review doesn't change or hide an entry. It adds a label: "stale since commit…", "superseded by another entry" or "disputed". Readers get the entry together with its label.
The review model, daily limit and second opinion are configured in Settings → Knowledge review.