Skip to main content

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.

​
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.
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.
1

Create your account

Go to nooterra.ai/signup and create your account.
2

Connect Stripe

Authorize Stripe so Nooterra can ingest customers, invoices, payments, disputes, and related receivable events.
3

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.
4

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.
5

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.
6

Track outcomes

Watch the system compare expected versus observed outcomes. Promotion to broader autonomy should come from measured execution quality, not a toggle.

​
What you should expect to see

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

Board state

Customers, invoices, payments, disputes, and estimated state in one tenant-scoped runtime view.

Recommendations

Ranked next actions, confidence posture, and explicit abstentions where support is thin.

Governance trail

Gateway decisions, operator reviews, execution traces, and outcome measurement for every action path.

​
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.

Introduction

The current product definition in one page.

Master build map

The canonical internal standard for what the company is building.

Causal assumptions

The honest boundary for current causal claims and abstention behavior.

Legacy docs

Historical worker-team, charter, and action-wallet docs.