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

# Ways to use Adapt-1

> Compare Adapt-1 workflows by the structured result, continuity, feedback loop, or audit view your application needs.

export const OutcomeAtlas = () => {
  const goals = [{
    index: "01",
    title: "Continuity",
    detail: "Preserve useful constraints and let later evidence revise them.",
    loop: "record · reason · revise",
    result: "context + evidence",
    href: "/docs/neuroadapt/build-an-assistant-with-persistent-context"
  }, {
    index: "02",
    title: "Infer hidden structure",
    detail: "Form task-local structure from live evidence inside a declared scope.",
    loop: "scope · observe · form",
    result: "hypotheses + evidence",
    href: "/docs/neuroadapt/build-a-domain-aware-assistant"
  }, {
    index: "03",
    title: "Revise hypotheses",
    detail: "Compare supported interpretations as observations accumulate or disagree.",
    loop: "compare · update · revise",
    result: "ranked hypotheses + support",
    href: "/docs/neuroadapt/build-a-domain-aware-assistant"
  }, {
    index: "04",
    title: "Adapt from outcomes",
    detail: "Bind observed consequences to the decision and scope they can revise.",
    loop: "commit · transition · update",
    result: "scoped learned state",
    href: "/docs/neuroadapt/make-behavior-improve-from-feedback"
  }, {
    index: "05",
    title: "Structured prediction",
    detail: "Update the documented interval or scalar policy online.",
    loop: "reset · ingest · predict",
    result: "prediction.<output_key>",
    href: "/docs/neuroadapt/return-structured-adaptive-outputs"
  }, {
    index: "06",
    title: "Learn observable transitions",
    detail: "Configure event geometry, grouping, targets, and support. These settings let Core reuse equivalent evidence.",
    loop: "observe · predict · inspect",
    result: "transition prediction + evidence",
    href: "/docs/neuroadapt/design-transition-domains"
  }, {
    index: "07",
    title: "Explain and audit",
    detail: "Inspect support, route-defined conflicts, co-active associations, missing evidence, and predicted observations.",
    loop: "result · explain · inspect",
    result: "route-defined audit fields",
    href: "/docs/neuroadapt/explain-and-audit-responses"
  }, {
    index: "08",
    title: "Monitor adaptation",
    detail: "Follow acquisition, reuse, revision, and goal-directed behavior across ordered use.",
    loop: "observe · compare · inspect",
    result: "adaptive behavior + state",
    href: "/docs/neuroadapt/measure-online-adaptation"
  }];
  return <nav className="not-prose my-7" aria-label="Adapt-1 application patterns">
      <ul className="m-0 grid list-none gap-3 p-0 md:grid-cols-2">
        {goals.map(goal => <li key={goal.index} className="m-0">
            <a href={goal.href} className="group flex h-full flex-col rounded-xl border border-stone-200 bg-white p-4 no-underline transition-colors hover:border-amber-400 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-amber-500 focus-visible:ring-offset-2 dark:border-zinc-800 dark:bg-zinc-950 dark:hover:border-amber-600 dark:focus-visible:ring-offset-zinc-950">
              <div className="flex items-center justify-between">
                <span className="text-xs font-medium text-stone-500 dark:text-zinc-400">Example pattern</span>
                <span className="text-xs text-stone-500 group-hover:text-amber-700 group-focus-visible:text-amber-700 dark:text-zinc-400 dark:group-hover:text-amber-300 dark:group-focus-visible:text-amber-300">Open capability guide</span>
              </div>
              <div className="mt-3 text-sm font-semibold text-stone-900 dark:text-zinc-100">{goal.title}</div>
              <div className="mt-1 text-xs leading-5 text-stone-600 dark:text-zinc-400">{goal.detail}</div>
              <div className="mt-4 flex flex-wrap items-center justify-between gap-2 border-t border-stone-100 pt-3 dark:border-zinc-800">
                <span className="font-mono text-xs text-stone-600 dark:text-zinc-400">{goal.loop}</span>
                <code className="bg-transparent p-0 text-xs text-amber-800 dark:text-amber-300">{goal.result}</code>
              </div>
            </a>
          </li>)}
      </ul>
    </nav>;
};

Adapt-1 exposes Core as a self-contained adaptive reasoning substrate. It can preserve and revise state, form task-local structure, compare and revise hypotheses, learn from observations and outcomes, return route-defined predictions or decisions, and expose supporting evidence without requiring generated language. Perception adapters and controllers can connect it to external modalities and actuation; they do not perform its reasoning.

The API namespaces are gateways into that substrate. They are not separate products and do not describe Core's internal architecture.

## Usage patterns

<Info>
  **These are examples, not a compatibility checklist.** Your product does not need to match one card, and its category does not need to appear on this page. A single application can combine several patterns wherever they fit the task.
</Info>

The cards illustrate common ways to use Adapt-1. They are not a complete list of supported products, tasks, or problem types. Use them to find the nearest guide, then combine or adapt the patterns to the application.

<OutcomeAtlas />

## Structured results

Adapt-1 does not need to generate a paragraph to produce a useful result. A structured prediction, ranked hypothesis, route-defined decision, constraint set, or evidence packet can be consumed directly by application code.

The machine-readable form is the delivery contract, not the source of the capability. The result can reflect evidence and learned state accumulated and revised across use.

```text theme={null}
application input -> Adapt-1 -> structured result -> validator / executor / UI
```

The application owns the final side effect. Under a decision-producing contract, an Adapt-1 result can drive the next application decision. The application executes the operation.

## Guides

* [Build continuity across calls](/docs/neuroadapt/build-an-assistant-with-persistent-context)
* [Build domain-aware behavior](/docs/neuroadapt/build-a-domain-aware-assistant)
* [Design Domains for transition learning](/docs/neuroadapt/design-transition-domains)
* [Learn from feedback and outcomes](/docs/neuroadapt/make-behavior-improve-from-feedback)
* [Return a machine-actionable adaptive result](/docs/neuroadapt/return-structured-adaptive-outputs)
* [Explain and audit a result](/docs/neuroadapt/explain-and-audit-responses)
* [Start an inspectable stateful workflow](/docs/neuroadapt/run-a-reproducible-goal-workflow)
* [Operate stateful and adaptive workflows](/docs/neuroadapt/operational-behavior-and-retries)
* [Monitor online adaptation across use](/docs/neuroadapt/measure-online-adaptation)

Applications can combine these workflows. For example, an application can preserve operating constraints and revise hypotheses inside a Domain. The application can bind observed transitions and consequences to state. It can also return a route-defined prediction or decision.

When the workflow acts in an external environment, preserve the exact action-to-transition record beside learned scores or selections. This connects Adapt-1's reasoning to the committed action, observed consequence, reusable action-effect structure, and later goal-directed behavior.