CONVENTION LEARNING
Your way of working, learned.
Read your standards. Review your feedback. Reinforce cycle after cycle — until the engine ships the way your best engineer would.
Bring your conventions1
Read
Learn your codebase
The architect reads your repo, your conventions files, and your existing patterns before writing a single line. The conventions you've documented become the plan's constraints.
2
Review
Absorb your feedback
Every CHANGES-REQUESTED on a PR, every retro delta you approve — these feed into the engine's learned conventions. Your reviews are the training signal, not abstract guidelines.
3
Reinforce
Ship your way
By cycle 3, the reviewer knows your error-handling patterns. By cycle 6, the engineer names variables the way your team does. The conventions compound cycle over cycle.
What gets learned, per tenant
Code style
Naming, structure, file layout, error patterns
Review standards
What CHANGES-REQUESTED looks like in your repo
Process deltas
Retro findings you approve become next-cycle defaults
In wakalix, what the team learns about your conventions stays in your tenant — not in a shared model, not in a public fine-tune. Every conventions file, every review feedback, every retro delta you adopt is tenant-scoped. Another customer doesn't benefit from (or inherit) your standards. The engine learns your way of working because you taught it, and that teaching is yours.
Under the hood.
The roles, the contracts, the orchestration — shared under NDA for technical evaluators.
Under the hood