Facet
DeutschInstall

SOLUTIONS

“Does anyone remember why it works like this?” Your code should.

The colleague who knew is on holiday. The wiki page is from 2021. And the test is called test_case_7. FACET writes down what a feature is supposed to do — right next to the code that does it and the test that checks it.

IS FACET A FIT?

A weekend project doesn’t need this. Your product in three years does.

pays off

When the extra structure can pay off

The case is strongest for long-lived products: hard-to-navigate monoliths, multiple teams and domains, repeated handoffs or frequent agent edits. What matters is whether knowledge will be reused and someone will maintain it.

often enough

When a README and tests may be enough

For small projects a person or agent can understand in full, and for throwaway prototypes, FACET may create more maintenance than value. If existing tools already connect rules, code and evidence reliably, another layer may be unnecessary.

Already working with specs?Where spec-driven development and FACET complement each other — and where another layer adds nothing.

THE FIRST STEP

Take the question that bugs you right now. One hour is enough for an answer.

No rollout, no big project: one feature, one question, one hour. Afterwards you know whether the answer comes faster next time — or whether you don’t need FACET at all.