Requirements and plans

Standards & rules: what Tulaian must follow

Upload your terms, practices, patterns and instructions for the coding assistant; approve the rules Yavaren proposes from them.

Tell Tulaian how your organisation builds software, the way you would brief a new engineer: your business and technical terms, best practices, design patterns, architecture decisions, coding conventions, and the instructions you would put in a CLAUDE.md or AGENTS.md file. Yavaren turns them into enforcement rules. Nothing is enforced until an admin approves it.

Upload

Open Standards & rules → Documents. Choose what the document is for: the whole organisation, one product, one project, one repository, or one stack (for example everything in Python). Choose its kind and download the template for it if you like: each template explains how to write a rule that can be checked, with examples. Markdown, plain text, CSV, Excel, Word and PDF are accepted. Yavaren shows what it read and the rules it would propose before anything is stored. Each upload of a document is a new version; earlier versions stay available.

Admins upload documents for the whole organisation; members can upload for a product, project, repository or stack. Files are read by their content, never run, and kept with your organisation's other documents.

Review the proposed rules

As soon as you upload a document, and again when a repository or a production org is connected, Yavaren proposes rules. Each one says where it came from (the document and the section, or what Yavaren found in the repository, such as its formatter configuration). Admins are told when rules wait for review.

Under Waiting for review, an admin can:

• Activate a rule as proposed, or edit it first. Activating asks you to confirm.
• Reject it. The same proposal is not made again.
• See a changed rule next to the version in force, and where a rule for the whole organisation says something else than a rule for a repository (the more specific one applies).

Members can edit proposed rules and suggest changes to rules in force; an admin activates them.

What happens with active rules

On every story:

• The coding assistant is given the active rules that apply to the repository, its stack, the project and the product, and your approved instructions. The instructions are never added to your pull request.
• Rules with a check are checked automatically after the change is written. A broken must rule goes back to the assistant to fix; if it stays broken, the pull request says so.
• The code reviewer uses the rules too, when you have switched it on.

Under In force, choose a repository to see exactly which rules a job there is given. Retire a rule to stop using it.

A check never runs a command written in a document: it can only name a quality tool Yavaren already runs for that stack.