Worlds

A world is the starting point for an attempt: which tools exist and what data they hold. Ancha builds a fresh copy of the world for every attempt, so one attempt’s writes never reach another.

Starter data

Every tool ships with versioned starter data for one fictional company, Acme, which sells warehouse analytics, and its customers: Ridgeway Robotics, whose pilot starts this week, Pinecrest Health, Bluefield Logistics, Kestrel Credit Union, Summit Freight, Harbor Foods and Helix Manufacturing. The records are linked across tools: the Ridgeway Robotics account in Salesforce, the deal in HubSpot and the discovery call in Gong describe the same customer, and the same people, Ben Carter, Rachel Moore, Mike Turner and their colleagues, appear in Slack, GitHub and PagerDuty.

Tool	Starter data (dataset `<tool>-starter`, version 1.1.0)
Slack	Workspace “Acme”, a bot and nine people, ten channels (#general, #support, #growth, #orders-incident, #product, #sales, #customer-success, #data-platform, #random and a private #leadership), 52 messages with threads.
GitHub	Three repositories: `acme/orders` with seven commits, six pull requests and seven issues, plus `acme/web` and `acme/warehouse-sync`.
Datadog	Seven monitors, three dashboards, five events, eight metric series and seventeen log lines across six services.
PagerDuty	Four users, two escalation policies, four services and five resolved incidents.
HubSpot	Nine companies, thirteen contacts, eight deals and the default sales pipeline.
Salesforce	Seven accounts, six contacts, four leads, six opportunities, two campaigns and two campaign members.
Gong	Two users, two workspaces and seven calls, six with transcripts.
Google Analytics	Two properties and nineteen sessions of historical traffic.
Google Ads	A manager account with one client account, a separate restricted account, and a search campaign with a budget, ad group, ad, keyword and two days of reports.
LinkedIn Ads	Two ad accounts, a campaign group, two campaigns, two creatives and daily analytics.
ChatGPT Ads	Two ad accounts, two campaigns, an ad group, two ads and hourly insights.
Open-Meteo	Ten places (San Francisco, New York, London, Berlin, Tokyo, Sydney, Portland, Chicago, Toronto and Singapore) with a synthetic climate.
Gmail	The support mailbox with four labels, nineteen messages in threads, a draft and an attachment, plus Laura Kim’s mailbox.
Google Drive	Thirty files in company, customer, engineering, finance and leadership folders, with permissions, comments and a trashed copy.
Microsoft Word	Contracts, policies and templates as `.docx` files, one with an earlier version and one shared with a customer.
Notion	Engineering and product pages with blocks and comments, a customer feedback database and meeting notes.
Dropbox	Sales, marketing, customer upload and team folders with a revision, a deleted file, a public link and a shared folder.
Resend	Two domains, two segments, six contacts, five sent emails with outcomes and two broadcasts.
Better Stack	Six monitors, two heartbeats, four incidents, two on-call rotations and a status page.
Linear	Two teams, two projects, five labels and seventeen issues.
Jira	Three projects, thirteen issues, three sprints and two issue links.
Okta	Twelve users across every lifecycle state, nine groups, eight SAML apps and ten System Log events.
Amazon S3	Four buckets with read-write, read-only and no access, holding customer exports, a sync staging area, backups and web assets.
Clerk	Twelve users in five customer organizations, with pending invitations and sessions.
Attio	Seven companies, nine people, five deals, a renewals list, two notes and three tasks.
Stripe	Three products, five customers with test cards, four subscriptions, six invoices, two payments and a refund.
PayPal	A product with three plans, four subscriptions and five checkout orders.
Shopify	A store with two locations, five products, seven customers and eight orders.
Lob	Nine addresses, two bank accounts, three templates, two letters, two postcards and a check.
Kalshi	Three series with twelve markets and an account with five orders.

Some starter records exist to test boundaries. For example, Slack’s #leadership channel is private and the bot is not a member, and Salesforce and HubSpot each hold one account, Helix Manufacturing, that the agent’s token cannot read.

Presets

A preset is a ready-made set of tools whose data fits together. List them with ancha sandbox presets.

Preset	Name	Tools
`operations`	Engineering workspace	Slack, GitHub, Datadog, PagerDuty
`b2b-salesforce`	Salesforce revenue workspace	LinkedIn Ads, Salesforce, Gong, Google Ads, ChatGPT Ads, Google Analytics
`b2b-hubspot`	HubSpot revenue workspace	LinkedIn Ads, HubSpot, Gong, Google Ads, ChatGPT Ads, Google Analytics

A new hosted workspace also starts with a Support workspace world: Slack and GitHub with the starter data above.

Naming records with refs

Starter records have refs, short names that start with $. Checks and scene files use refs instead of generated IDs, for example $slack_support for the #support channel or $github_orders for acme/orders. Each tool page lists the refs its starter data declares. In a scene file, you declare your own refs with ref: and use them with $. See Test file.

Time

Each world runs on a simulated clock. A scene’s start_time sets when the world begins, and time_scale sets how fast simulated time runs. Starter history sits before the start, for example a Slack message posted 35 minutes earlier. Because the clock is simulated, the same world gives the same timestamps on every attempt.

Static and living worlds

Kind	Behavior
`static`	Nothing happens unless the agent acts. The starter scene is static.
`living`	The world has rules that act on their own while the agent works: a person posts in Slack after two minutes, a fault keeps a metric high until a fix is deployed, a monitor alerts and pages PagerDuty. This is the default for scene files.

Living-world rules are written in a scene’s world_rules. See Test file.

Versions

Worlds you save in the hosted console or with ancha world create are versioned. Editing a world creates a new revision. A test keeps the revision it was saved with until you choose a newer one, so old results stay comparable. Archiving hides a world from normal lists and keeps its history.

Where worlds come from

You use	Define the world with
`ancha run`	A scene file: `twins`, `seed` and optional `world_rules`. See Test file.
`ancha playground`	`ancha world create --tools slack,github`. See `ancha world`.
Hosted console	The Worlds page.
Exploring by hand	`ancha sandbox create --preset operations`. See `ancha sandbox`.

Get started

Guides

Concepts

Tools

CLI

Reference

Cloud

Help

Starter data

Presets

Naming records with refs

Time

Static and living worlds

Versions

Where worlds come from

​Starter data

​Presets

​Naming records with refs

​Time

​Static and living worlds

​Versions

​Where worlds come from

Starter data

Presets

Naming records with refs

Time

Static and living worlds

Versions

Where worlds come from