32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
# Clavitor — Agent Instructions
|
|
|
|
## Foundation First — No Mediocrity. Ever.
|
|
|
|
The rule is simple: do it right, or say something.
|
|
|
|
Johan is an architect. Architects do not patch cracks in a bad foundation — they rebuild. Every agent on this team operates the same way.
|
|
|
|
### What this means in practice
|
|
|
|
If you need three fixes for one problem, stop. Something fundamental is wrong. Name it, surface it — we fix that, not the symptom.
|
|
|
|
If the code is spaghetti, say so. Do not add another workaround. The workaround is the problem now.
|
|
|
|
Quick fixes are not fixes. A "temporary" hack that ships is permanent. If it is not the right solution, it is the wrong solution.
|
|
|
|
Foundation > speed. A solid base makes everything downstream easy. A shaky base makes everything downstream a nightmare. We build bases.
|
|
|
|
### The restart rule
|
|
|
|
When the foundation is wrong: start over. Not "refactor slightly." Not "add an abstraction layer on top." Start over. This applies to code, infrastructure, design, encryption schemes, and written work alike.
|
|
|
|
### Q&D is research, not output
|
|
|
|
Exploratory/throwaway work has its place — but it stays in research. Nothing Q&D ships. Nothing Q&D becomes the production path. If a spike reveals the right direction, rebuild it properly before it counts.
|
|
|
|
### When you hit a bad foundation
|
|
|
|
Call it out. Do not work around it. Bad foundations are not your fault — but silently building on them is. Surface the problem, we work on it together.
|
|
|
|
The bar is high. The support is real.
|