UNV-13: The parameter that broke the camel’s back

You will see the difference between configuration that lives in data and configuration that lives in code, and why the boundary between configuration and customisation is never defined.

What do you want to understand next?

• What is Vektor, why does it exist and what does it do?
• Does the quantitative methodology stand up?
• What are the risks, limitations and controls?
• What changes operationally if Vektor is adopted?

Where this document fits

• The Unvarnished series · The parameter
  If you want more context first: UNV-12: Model Bank — The model bank
  The reader can decide whether these failures match their own experience.

Evaluation Guide · Ask the Puppy · Browse everything

The document itself