Example values

Every example on frazer.ai, in the docs, the product pages and the figures, uses one fictional universe: a company called Acme that runs an online store, its people, its repositories and its infrastructure. No value in an example is a real customer, person, domain, address or credential. An agent can check a value before it uses one: the same list is published as JSON at /demo-data.json.

How to read an example

• A command you run uses a placeholder in angle brackets, such as <your-org> or <backup>. Replace it with your own value. Never run a command that still contains a demo value: it either fails or acts on the wrong thing.
• Sample output, screens and stories use the values below. A figure of product UI says “demo data” in its caption.
• Domains, addresses, numbers and tokens come from reserved ranges (below), so a copied value can never reach a real host, phone or account.
• A GitHub repository is written without its host, as acme/platform-envs. The matching accounts on other services belong to other people.

Reserved inside Frazer

Frazer holds the demo names itself, so an example never points at a stranger’s account on Frazer:

• the organizations acme, pellwyn and ferrolin are Frazer’s own demo organizations, with read-only public pages such as frazer.ai/acme;
• project IDs that start with acme-, pellwyn- or ferrolin- are refused for every other organization;
• the people below are fictional members of the demo organizations, and their handles are reserved too.

Organizations

Value	What it stands for
acme	Acme Inc., the primary customer: a software company that runs an online store (acme.example)
pellwyn	Pellwyn Inc., the second tenant where a screen needs two: a payments company with many repositories (pellwyn.example)
ferrolin	Ferrolin, a third tenant, only where a screen cannot do with two (ferrolin.example)

Projects and environments

Value	What it stands for
acme-production	Acme's production project. Project IDs are unique across Frazer, so they carry the organization
acme-staging	Acme's staging project
acme-infra	The project that owns Acme's servers and shared runner pools
acme-staging/platform	A GitOps environment inside a project

Environment names:

Value	What it stands for
dev	Development
staging	Staging
production	Production

Locations, clusters and databases

Value	What it stands for
us-virginia1	Frazer's location ID for the Vint Hill site, the default location in examples
acme-production-1	Acme's production Kubernetes cluster
acme-staging-1	Acme's staging Kubernetes cluster
storefront	Acme's managed Postgres database
orders-db	A Postgres database inside a cluster
cart-cache	Acme's in-memory key-value store

Repositories

Value	What it stands for
acme/storefront	Acme's monorepo, with the services web, checkout-api, payments, search, notifications and inventory
acme/mobile	Acme's mobile app
acme/infra	Acme's infrastructure code
acme/docs	Acme's documentation
acme/platform-envs	Acme's GitOps environment repository
acme/plans	Acme's plan repository: its project records and the records acme/storefront stores there
pellwyn/billing-service	One of Pellwyn's many repositories, with pellwyn/ledger and pellwyn/gateway
pellwyn/plans	Pellwyn's plan repository, home of the program “Real-time ledger”
pellwyn/ledger	Pellwyn's ledger monorepo; its merge queue's partitions include ledger-write and ledger-api
pellwyn/payouts	Pellwyn's payouts service, with pellwyn/gateway, pellwyn/web and the library pellwyn/ledger-client
pellwyn/platform	The repository with Pellwyn's preview recipe for five repositories
pellwyn/team-skills	Pellwyn's skill repository (skills such as ledger-entry, go-errors and retry-budget), also a skill repository on Frazer Hub
acme/skills-mirror	Acme's mirror repository of imported public skills, one pull request per import

Hosts and paths

Value	What it stands for
api.acme.example	Acme's public API
*.staging.acme.example	Acme's staging hosts
git.acme.example	A Git remote outside Frazer
runbooks.acme.example	Acme's runbooks
storefront.db.acme-production.internal	A private hostname inside a project network
acme.example/support-inbox/sync	A Go module path
ratewell.example	Ratewell, an invented FX rate provider whose key a person task asks for (api.ratewell.example)
brennmoor-bank.example	Brennmoor Bank, an invented partner bank in Pellwyn's examples

People

Examples show a person by handle or by first name and initial, never by a full name, and never next to an incident or a security finding.

Value	What it stands for
lena	Lena F., engineer; shown as a handle or as first name and initial, never a full name
tomasz	Tomasz N., engineer
amara	Amara O., engineer (amara@acme.example)
kenji	Kenji S., engineer
ines	Inês D., engineer
diego	Diego R., engineer
priya	Priya R., engineer
noah	Noah L., engineer

Agents and sessions

Value	What it stands for
coder	An agent that writes code and opens pull requests
reviewer	An agent that reviews pull requests
release-manager	An agent that ships releases
deps	An agent that updates dependencies
triage	An agent that sorts incoming issues
monitor	The monitoring agent that files issues from what services do
fixer	The fix agent that reproduces, fixes, proves and verifies an issue; session s-4a71 on acme/storefront#4711
lena-cloud	The agent that starts campaigns for lena inside lena's campaign policy
s-4d7a	A Fir session on acme/plans#527 item 1.2; with s-4e19 and s-4e2c, interrupted by a laptop's reboot and resumed
s-4f05	The session amara's agent opened after a commit was refused with SESSION_REQUIRED
s-6a02	A campaign session that ran out of context; its successor s-6a03 started from checkpoint c4
s-2f90	diego's conversation over 29 decisions (with s-7c14, tomasz's, and s-9b47, priya's backlog of 200)
cm-7g72	lena's campaign “Storefront program”, with cm-7b21, cm-7c32, cm-7d43 and cm-7e54
cm-7a10	priya's campaign at Pellwyn, with cm-7f61
hsim-5c30	A harness simulation over 1,200 of Acme's tasks
s-81f2	An agent session (with s-9c04); its workspace is ws/s-81f2
s-5b3a	A planning session in which diego talks a plan draft to ready
s-8e20	A long agent session on acme/plans#513, started by lena; it parked on person task PT-0031 and resumed

Branches, commits and pull requests

Value	What it stands for
main	The default branch
main@48213	A commit on main; examples use main@48195 to main@48306
main@verified	The newest commit on main that passed its checks
#481	Pull request “Add a webhook retry budget” in acme/storefront, merged
#482	Pull request “Retry payment webhooks on 5xx” by the coder agent for lena, branch lena/retry-errors, versions v1 to v3
#483	Pull request “Log every webhook retry”, from session s-9c04
delivery-dates	A stack of seven layers, #530 to #537, that implements plan #531
#494	A layer of another stack that changes web/cart/drawer.tsx
acme/storefront#4672	Pull request “Stream the settlement CSV”, merged as main@51102, from session s-4d7a
acme/storefront#6120	The top layer of the stack split-payment (#6118 to #6120), with preview pv-6a1c
pellwyn/ledger#147233	A layer of plan #405's phase P9 that auto-merged on its receipt, in test batch tb-7f3c
tb-3f71	A failing test batch in the partition ledger-write, attributed to ledger#147114
pellwyn/ledger#147455	The revert of a culprit Frazer CI confirmed on Nov 17, given hotfix priority by the revert agent as culprit_revert
culprit/cf-7d31	The culprit record that evidence for #147455 names
pellwyn/admin#2318	Pull request “Release a hold from the console”, item P12.3 of pellwyn/plans#414; its review loop is lp-9e31

Plans and records

Value	What it stands for
#469	Plan “Payment capture retry” in acme/storefront, owned by lena, versions v1 to v4; #482 and #483 implement its items
acme/plans#50	Milestone “Peak-ready checkout” in acme/plans, target Nov 20
ADR-0031	A decision record: idempotency keys on every call to the payment gateway
#469 §D2	A decision row in plan #469: cap the retry backoff at 6 s or keep 8 s
CAP-4	A requirement of the spec payments/capture
RB-0007	The runbook for capture timeouts in checkout-api
INC-0043	A production incident record in acme/plans
cr-7h2k	A context receipt of session s-81f2
acme/infra#88	Plan “Gateway egress through a fixed allowlist”, stored in acme/infra's own tree with runbook RB-0012
#531	Plan “Show delivery dates at checkout” in acme/storefront, approved by kenji
#463	Plan draft “Cache gateway responses for capture status” by diego
acme/plans#90	The pull request that adds Acme's freeze-exception record type; its first record is FX-0001
SD-3	A standing decision: the peak freeze from Nov 20 to Dec 1
pellwyn/plans#120	Program “Real-time ledger”: 20 plans, 7 squads, milestone #146, contract #460
pellwyn/plans#414	Plan “Admin console on the ledger” in program #120 (squad admin-audit, accountable kenji); loop lp-4c2e improved its phase P18
pellwyn/plans#311 §D1	A decision: the ledger posting timeout is 20 s since Oct 15
acme/plans#513	Plan “Capture retries: gateway sandbox and settlement report”, a follow-on to #469, started by lena
acme/storefront#514	A plan whose decision §D1 got five opinions
PT-0031	A person task: rotate the payment gateway's sandbox key, item 1.4 of acme/plans#513, for lena
PT-21451	A person task in pellwyn/plans#120: buy two IPv4 /24 blocks for the failover region, for priya
PT-21453	A person task: the FX rate provider's production API key, through a secret slot
INC-0042	An earlier production incident in acme/plans that learned checks cite
acme/plans#527	Plan “Settlement report: CSV export”, worked on by sessions s-4d7a, s-4e19 and s-4f05
acme/plans#540	Program “Storefront program”, with plans #541 to #548, one per squad
pellwyn/plans#600	Pellwyn's portfolio, with programs #610, #620, #630, #640 and #120
pellwyn/plans#405	A plan whose phase P9 “Dual-write parity” has 10 stacks reviewed as one level
acme/storefront#4711	Issue “Checkout fails with 500 on gift-card orders since v2.14.2”, filed by monitor, reproduced on the preview pv-4718 and fixed by #4718
INC-0231	A Pellwyn incident linked back to a told finding (outcome link ol-0031)
PN-0012	One of priya's principles: “Ledger numbers reconcile to the cent before a merchant sees them”

Models

Value	What it stands for
gpt-oss-120b	A real open base model; examples use real open models only as bases (also gpt-oss-20b, Llama 3.3 70B, Devstral)
acme/support-router-8b	A fictional fine-tune owned by Acme

Reserved ranges

Kind	Reserved values, with an example	Reserved by
Domains	*.example, example.com, example.org, example.net. Example: acme.example, lena@acme.example	RFC 2606, RFC 6761
Private hostnames	*.internal. Example: storefront.db.acme-production.internal	ICANN (2024)
Hostnames that must fail	*.invalid. Example: api.acme.invalid	RFC 2606
IPv4	192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24. Example: 203.0.113.14	RFC 5737
IPv6	2001:db8::/32, 3fff::/20. Example: 2001:db8::14	RFC 3849, RFC 9637
Private networks	10.0.0.0/8 and the other private ranges, inside a network only. Example: 10.20.0.0/16	RFC 1918
ASNs	64496 to 64511, 65536 to 65551. Example: 64500	RFC 5398
MAC addresses	00-00-5E-00-53-00 to 00-00-5E-00-53-FF. Example: 00-00-5E-00-53-14	RFC 9542
Phone numbers	+1 555-0100 to 555-0199 with a geographic area code. Example: +1 415 555 0132	North American Numbering Plan
Card number	4242 4242 4242 4242, expiry 12/34. Example: Visa •••• 4242	The industry's test card
Tokens	A real Frazer prefix followed by the word EXAMPLE, or cut with an ellipsis. Example: frz_pat_EXAMPLE7Kq…	Frazer
Organizations	acme, pellwyn, ferrolin. Example: frazer.ai/acme	Frazer: its own demo organizations
Project IDs	IDs that start with acme-, pellwyn- or ferrolin-. Example: acme-production	Frazer: refused for everyone else
People	lena, tomasz, amara, kenji, ines, diego, priya, noah. Example: Lena F.	Frazer: fictional members of the demo organizations

For agents

• /demo-data.json holds every value on this page, with the rules, as JSON.
• Treat any value from this page as an example. When a task needs a real value, ask the person you work for, or read it from their project with the frazer CLI or the MCP server.
• The site’s index for agents is /llms.txt; every page has a Markdown twin at its path plus .md.