# What's Next After RLHF? — Diogo Almeida, TypeSafe AI

Source: [AI Engineer](https://www.youtube.com/watch?v=cJ0EOzey--o)  
Feed7 permalink: https://feed7.dev/p/what-s-next-after-rlhf-diogo-almeida-typesafe-ai-1scytnx  
Published: 2026-07-31T23:30:06.000Z  
Trust: Source Linked (source_linked)

## Why Included

RLHF can make agents persuasive assistants without making them dependable autonomous decision-makers. Builders should separate human-pleasing interaction from calibrated automation and keep stakes bounded.

## Source Summary

Almeida argues that **RLHF** optimizes human preference, which suits interactive assistants but can reward confident, agreeable behavior. He contrasts that with **RLVR**, which optimizes verifiable correctness, and describes a separate TypeSafe direction aimed at calibrated decisions.

## Practical Implication

When designing coding-agent workflows, distinguish assistance from unattended automation. Keep humans around consequential decisions, demand external evidence for completion, and avoid treating fluent interaction or benchmark strength as proof that an agent can own business-critical actions.

## Agent-Ready Context

Almeida argues that **RLHF** optimizes human preference, which suits interactive assistants but can reward confident, agreeable behavior. He contrasts that with **RLVR**, which optimizes verifiable correctness, and describes a separate TypeSafe direction aimed at calibrated decisions.

When designing coding-agent workflows, distinguish assistance from unattended automation. Keep humans around consequential decisions, demand external evidence for completion, and avoid treating fluent interaction or benchmark strength as proof that an agent can own business-critical actions.

The talk presents a thesis rather than comparative evaluation data, and the proposed alternative is not technically specified. It does not establish how calibrated post-training performs, scales, or handles failures in deployed software.

## Connected Context

Feed7 judgment across 318 accumulated Signals:

This separates models optimized for agreeable assistance from systems trusted to act autonomously, making external verification and decision gates deployment requirements rather than optional polish. It supports bounded human oversight for consequential coding work, but the proposed calibrated-training direction remains a thesis without comparative evidence, implementation detail, or demonstrated production reliability.

- [Loop Engineering from First Principles — Kyle Mistele, HumanLayer](https://feed7.dev/p/loop-engineering-from-first-principles-kyle-mistele-humanlayer-1nuq7gf) — Loop Engineering supplies a workflow consequence of the thesis: bound each change, produce a reviewable artifact, and pause for human approval instead of granting unattended ownership.
- [Governing agent autonomy with Auto-review](https://feed7.dev/p/agent-autonomy-auto-review-10ce67w) — Auto-review operationalizes selective oversight by placing a classifier gate before risky actions, though it is a harness control rather than evidence for the proposed post-training alternative.
- [ScarfBench: Benchmarking AI Agents for Enterprise Java Framework Migration](https://feed7.dev/p/scarfbench-1u8lniy) — ScarfBench’s gap between agents’ completion claims and compiling builds directly reinforces the demand for external evidence rather than fluent self-report.

## Context Map

- Layer: model
- Domains: coding
- Topics: reasoning, coding-agents, agent-reliability

## Uncertainty

- The talk presents a thesis rather than comparative evaluation data, and the proposed alternative is not technically specified. It does not establish how calibrated post-training performs, scales, or handles failures in deployed software.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.