Reviews and quality

Guidance for your codebase

See what Yavaren understood of your rules for each part of your work, acknowledge it, and adopt Yavaren's recommended baselines.

Build › Guidance shows, for the whole organisation, a stack, a project, a product or a repository, the rules Yavaren follows there, where each came from, and what it still asks.

What Yavaren understood

Only rules an admin activated count. Each shows its source — your document and section, or a baseline. Conflicts between scopes, rules still waiting for activation and documents that gave no rule are listed as questions.

Acknowledging

An admin reviews the understanding and chooses Acknowledge this understanding. When a rule changes later, the scope shows what changed and asks again. Acknowledging never changes a rule.

Yavaren recommends

Recommended baselines are rule sets per concern (secure coding, testing, API design, a new application) and per stack. Adopt for this scope proposes their rules; an admin activates them under Standards & rules before any job uses them. A baseline is a starting point, not a certification.