BW-04: AI as Instrument

You will know where Vektor uses machine learning, where it deliberately does not, and why the boundary was drawn before the code was written.

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

• Understand design choices · Why Vektor does not say AI
  If you want more context first: BW-03: The Configurability Gap — The configurability gap
  If you want to go further: Why Not the Incumbents? — The alternatives, fairly assessed

Evaluation Guide · Ask the Puppy · Browse everything

The document itself