---
title: Shallow handoff drift
summary: >-
  A clean-looking UI brief omits the implementation contract, then gets
  rewritten into the required portable handoff sections.
agent_summary: >
  This example shows how JudgmentKit rewrites aesthetic summaries into a real
  token, recipe, composition, state, theme, accessibility, and escalation
  handoff packet.
canonical_url: /docs/examples/shallow-handoff-drift
page_type: example
related_resources:
  - /resources/examples/shallow-handoff-drift.v1.json
related_schemas:
  - /schemas/example.schema.json
  - /schemas/verdict.schema.json
last_reviewed: '2026-04-14'
---
# Shallow handoff drift

A clean-looking UI brief omits the implementation contract, then gets rewritten into the required portable handoff sections.

> Agent summary: This example shows how JudgmentKit rewrites aesthetic summaries into a real token, recipe, composition, state, theme, accessibility, and escalation handoff packet.


## Headings
- ## Scenario
- ## Raw decision or output
- ## What JudgmentKit detected
- ## What action was taken
- ## Corrected result
- ## Why the correction matters
- ## JSON artifact links

## Scenario

A team asks for an implementation-ready export flow, but the first pass only describes how the interface should feel.

## Raw decision or output

`The export page should feel simple and trustworthy, with clear cards, obvious hierarchy, and a polished summary area before the final handoff action.`

## What JudgmentKit detected

- a visual summary with no token, component, or theme contract
- no explicit state coverage or escalation list

## What action was taken

JudgmentKit rewrote the handoff into the required portable sections.

## Corrected result

`Return core_screens, token_spec, component_recipes, screen_composition, state_coverage, theme_contract, accessibility_contract, and escalation_items. Map the summary region to card plus artifact-panel recipes, include React+Tailwind composition snippets with slots and interaction rules, define loading, empty, ready, error, review-needed, and disabled states, bind light-dark tokens explicitly, and list the export edge cases that still require review.`

## Why the correction matters

Portable UI authority only helps implementation when the handoff survives beyond the model run itself.

## JSON artifact links

- Example resource: `/resources/examples/shallow-handoff-drift.v1.json`
- Schema: `/schemas/example.schema.json`

## Related pages
- /docs/workflows/ai-ui-generation
- /docs/reference/portable-no-design-system-pack
- /docs/guardrails/spec-completeness

## Related resources
- /resources/examples/shallow-handoff-drift.v1.json

## Related schemas
- /schemas/example.schema.json
- /schemas/verdict.schema.json