---
title: Onboarding clarity drift
summary: >-
  A landing-page first pass over-emphasizes internal artifacts and inspect
  surfaces, then gets rewritten into a clearer connect-and-start story.
agent_summary: >
  This example shows a homepage draft drifting toward self-referential proof and
  away from onboarding clarity before JudgmentKit rewrites it into a clearer
  path for the human team evaluating whether to use it.
canonical_url: /docs/examples/onboarding-clarity-drift
page_type: example
related_resources:
  - /resources/examples/onboarding-clarity-drift.v1.json
related_schemas:
  - /schemas/example.schema.json
  - /schemas/verdict.schema.json
last_reviewed: '2026-04-10'
---
# Onboarding clarity drift

A landing-page first pass over-emphasizes internal artifacts and inspect surfaces, then gets rewritten into a clearer connect-and-start story.

> Agent summary: This example shows a homepage draft drifting toward self-referential proof and away from onboarding clarity before JudgmentKit rewrites it into a clearer path for the human team evaluating whether to use it.


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

## Scenario

A first-pass landing page for JudgmentKit leads with inspect surfaces, raw references, and bundle mechanics before it makes the product and start path obvious.

## Raw decision or output

`Open the homepage with the inspect surface, bundle call details, resource ids, and raw references above the fold so the page proves JudgmentKit is real before it explains what it is or how to start.`

## What JudgmentKit detected

- internal artifact proof is crowding out onboarding clarity
- the page is speaking like an operator console before it has oriented a first-time user
- the next action is present but visually secondary to the system internals

## What action was taken

The refinement loop rewrote the page into a clearer connect-and-start path. Inspect links and raw artifacts were kept, but moved below the primary onboarding story.

## Corrected result

`Lead with what JudgmentKit is, why it improves the first pass, and how to connect it in one screen. Keep inspect links and raw artifacts below the primary onboarding path, and only surface them once the operator already knows the next step.`

## Why the correction matters

The goal is not to hide the system internals. It is to sequence them correctly. A landing page should orient the human decision-maker before it proves every underlying artifact.

## Related workflow and guardrails

- Workflow: `/docs/workflows/ai-ui-generation`
- Guardrails: `/docs/guardrails/brand-and-tone`, `/docs/guardrails/provenance-and-escalation`

## JSON artifact links

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

## Related pages
- /docs/workflows/ai-ui-generation
- /docs/guardrails/brand-and-tone
- /docs/guardrails/provenance-and-escalation

## Related resources
- /resources/examples/onboarding-clarity-drift.v1.json

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