> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exterview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Gradientflo Roadmap

> How Gradientflo is being released: the sequence of capability, what gates each stage, and what is required before any assessment of an employee runs.

## Purpose

Gradientflo is released in stages, sequenced by readiness rather than by date. This page states the order and what gates each step.

<Info>
  **Status: Upcoming.** Nothing described here is available today. We state
  sequence and readiness, not dates, and this page is updated as stages
  complete.
</Info>

## The sequence

<Steps>
  <Step title="Candidate Success — the first 90 days">
    The first release. A new joiner signs in on day one — with Workday,
    Darwinbox, Microsoft Entra or a company email — and sees the people they
    work with, the project they joined, and what day 30, 60 and 90 require,
    assembled from your HR system and project tools or entered directly when
    none is connected. **Notice comes first and gates everything else**: no
    check-in and no AI suggestion runs before the joiner has been told what is
    observed and why. Structured check-ins at each milestone are reviewed by a
    human; a below-bar result triggers support, never an automatic outcome.
  </Step>

  <Step title="Core loop — companion and role fit">
    The onboarding companion answering from your own material, ramp risk signals,
    and role-fit re-evaluation at day 60 and 90 against the original hiring
    criteria.
  </Step>

  <Step title="Development">
    Structured development planning from an identified gap, and connection to the
    learning your organization already licenses.
  </Step>

  <Step title="Operate at scale">
    Administrative agents, manager-facing insight, and reach through the channels
    a new hire actually has on day one.
  </Step>

  <Step title="Adaptive">
    Coaching prompts and pace personalization driven by accumulated signals, and cross-organization benchmarking in anonymized form.
  </Step>
</Steps>

## What gates the sequence

<CardGroup cols={2}>
  <Card title="Transparency before assessment" icon="megaphone">
    Notice and attestation ship before any agent evaluates an employee in the background. This is a hard ordering constraint, not a preference.
  </Card>

  <Card title="Evidence before judgment" icon="file-check">
    Role-fit re-evaluation requires the onboarding companion to have run first —
    without interaction evidence, a re-evaluation is a guess.
  </Card>

  <Card title="Security review before write access" icon="shield-check">
    The first agent that writes to your systems is the one most likely to fail a
    security review. It ships behind permission scoping and human confirmation on
    every write, not ahead of them.
  </Card>

  <Card title="Customer demand" icon="users">
    Within a stage, sequence follows what customers are asking for.
  </Card>
</CardGroup>

## Availability language

| Label         | Means                                |
| ------------- | ------------------------------------ |
| **Available** | You can use it today                 |
| **Upcoming**  | On the way, not yet usable. No dates |

Every Gradientflo page uses these two labels. Everything on them is Upcoming.

## Related

<div className="kb-links">
  *   <span className="kb-ico">
        <Icon icon="graduation-cap" />
      </span>
    [Gradientflo](/gradientflo/overview).
  *   <span className="kb-ico">
        <Icon icon="bot" />
      </span>
    [Gradientflo Agents](/agents/gradientflo).
</div>