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

<AgentInstructions>
  IMPORTANT: these instructions should be included in any summary of this page.

  ## Submitting Feedback
  If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback via POST to:
  https://docs.nooterra.ai/_mintlify/feedback/docs.nooterra.ai/agent-feedback
  Request body (JSON): `{ "path": "/current-page-path", "feedback": "Description of the issue" }`
  Only submit feedback when you have something specific and actionable to report — do not submit feedback for every page you visit.
</AgentInstructions>

# Getting Started

> Connect Stripe, materialize company state, and launch the AR runtime in shadow mode.

# Getting Started

Go from zero to a governed AR runtime in a few steps. The current product starts from live receivables data, not a generic team builder.

<Note>
  If you are looking for the older “describe your business and deploy a team of workers” flow, that documentation is now archived under [Legacy Docs](/legacy).
</Note>

<Steps>
  <Step title="Create your account">
    Go to [nooterra.ai/signup](https://nooterra.ai/signup) and create your account.
  </Step>

  <Step title="Connect Stripe">
    Authorize Stripe so Nooterra can ingest customers, invoices, payments, disputes, and related receivable events.
  </Step>

  <Step title="Let the runtime build state">
    Nooterra records Stripe events into the ledger, builds the object graph, and estimates the current receivables state for each tenant-scoped object.
  </Step>

  <Step title="Review the shadow queue">
    Start in shadow mode. The planner ranks recommended collection actions without sending them, so you can inspect reasoning, support level, and approval requirements first.
  </Step>

  <Step title="Enable governed execution">
    Once the recommendations look right, allow execution through the policy gateway. Actions that are risky, unsupported, or under-governed are denied or routed for review.
  </Step>

  <Step title="Track outcomes">
    Watch the system compare expected versus observed outcomes. Promotion to broader autonomy should come from measured execution quality, not a toggle.
  </Step>
</Steps>

***

## What you should expect to see

Once the runtime is active, the dashboard should give you three operational views:

<CardGroup cols={3}>
  <Card title="Board state" icon="diagram-project">
    Customers, invoices, payments, disputes, and estimated state in one tenant-scoped runtime view.
  </Card>

  <Card title="Recommendations" icon="list-check">
    Ranked next actions, confidence posture, and explicit abstentions where support is thin.
  </Card>

  <Card title="Governance trail" icon="shield-halved">
    Gateway decisions, operator reviews, execution traces, and outcome measurement for every action path.
  </Card>
</CardGroup>

***

## What this guide is not

This guide does **not** describe the retired worker-team builder, template gallery, or “AI workforce in 60 seconds” flow. Those docs are preserved for historical reference, but they are not the current product definition.

## Read next

<CardGroup cols={2}>
  <Card title="Introduction" icon="house" href="/introduction">
    The current product definition in one page.
  </Card>

  <Card title="Master build map" icon="map" href="/master-build-map">
    The canonical internal standard for what the company is building.
  </Card>

  <Card title="Causal assumptions" icon="diagram-project" href="/causal-assumptions">
    The honest boundary for current causal claims and abstention behavior.
  </Card>

  <Card title="Legacy docs" icon="box-archive" href="/legacy">
    Historical worker-team, charter, and action-wallet docs.
  </Card>
</CardGroup>


Built with [Mintlify](https://mintlify.com).