---
id: "concept-machine-readable-okrs"
type: "concept"
source_timestamps: ["00:16:28", "00:17:45"]
tags: ["management", "ai-alignment"]
related: ["concept-intent-engineering", "framework-intent-gap-layers", "claim-human-osmosis-ending", "action-translate-okrs"]
definition: "The translation of human-centric business objectives into explicit, structured, and actionable parameters for autonomous AI agents."
sources: ["s24-prompt-engineering-dead"]
sourceVaultSlug: "s24-prompt-engineering-dead"
originDay: 24
---
# Machine-Readable OKRs

## Definition

**Machine-Readable OKRs** are the translation of human-centric Objectives and Key Results into explicit, structured parameters that autonomous agents can act upon.

## The Problem with Traditional OKRs

Classic OKRs assume:

- Humans will read them.
- Humans will use *judgment* to handle prioritization.
- Humans will absorb tradeoffs through culture, mentorship, and tacit observation.

Agents, however, do **not** absorb culture through osmosis — see [[claim-human-osmosis-ending]]. They cannot listen at the watercooler. They cannot read tone at an all-hands. They cannot watch how a senior leader handles a tough customer call and infer the unwritten rule.

## What Machine-Readable Means

Machine-readable OKRs encode:

- **Explicit resolution hierarchies** ("if policy says X but CSAT signals Y, weight by Z").
- **Tradeoff weights** in mathematical or logical form.
- **Boundary conditions** (when to escalate, when to refuse, when to pause).
- **Time horizons** (short-term cost vs. long-term LTV).

## Worked Example (from the source)

Klarna's AI ([[claim-klarna-intent-failure]]) had a single implicit OKR — *minimize resolution time and cost*. A machine-readable OKR would have explicitly bounded that with: *…subject to maintaining Customer Satisfaction Score ≥ 4.2/5 and Lifetime Value retention ≥ baseline*.

## Operational Step

The corresponding action item is [[action-translate-okrs]]. This is the entry point for any organization beginning [[concept-intent-engineering]].

## Position in the Stack

Machine-readable OKRs are the *concrete artifact* produced at Layer 3 of the [[framework-intent-gap-layers]].



## Related across days
- [[concept-spec-quality-bottleneck]]
- [[concept-intent-engineering]]
- [[action-translate-okrs]]
- [[framework-intent-gap-layers]]