Paths by role

Who is this for

Someone who has read What is AI Sticker Pack and now needs the shortest route to being useful in one specific role.

TL;DR

• Developer: architecture L1–L3 → local setup → API reference → code rules → tests.
• Event operator: event playbook → runbooks → monitoring. You do not need to read code.
• Sales / agency partner: how to sell → venue requirements → client FAQ → lead process. No technical pages.
• Owner: cost → scaling scenarios → known gaps → roadmap → decisions.

Developer

Goal: run both projects locally, change them safely, deploy.

1. System context and Containers — what talks to what.
2. Components of the part you will touch: sticker-api, sticker-bot, generation pipeline, kiosk, landing.
3. State machines and Data model.
4. Local setup: product or Local setup: landing.
5. Environment variables and Code rules — read the rules before the first commit; several of them are legal or money constraints.
6. Testing, then API reference and Bot commands as lookups.
7. Before the first deploy: Deploy & rollback.
8. Before changing a design choice: the matching page in Decisions.

Task-oriented shortcuts:

I need to…	Page
add an outfit, body template or art style	Outfits, templates and art styles
change a text on the landing page	i18n and copy
add a person to the landing showcase	Showcase packs
add an animation to the landing page	Animation rules
understand why the audit script failed	Landing quality tooling
connect a new product to the requests group	Playbook: new product

Event operator

Goal: prepare a station, run an event day, react to incidents. Assumes SSH access to the server and admin rights in the bot; no programming.

1. Event playbook — checklists for the week before, the day before, the rehearsal, the event day and afterwards.
2. Monitoring & alerts — what each alert means and where to look.
3. Runbooks — skim all the titles once, so you know what exists before you need it.
4. Configuration — the handful of switches you may flip during an event.
5. Backups & data lifecycle — what to verify after the event.
6. Venue requirements and branding — what must be physically on site.

Keep these two open on event day: Runbooks and Bot commands.

Sales (agency partner)

Goal: explain the product correctly, promise only what it does, collect what the team needs to start.

1. How to sell — audiences, arguments, what we promise and what we never promise.
2. Venue requirements and branding — tablet, internet, space, what can be branded.
3. Client FAQ — ready answers.
4. How a request is handled — what happens after the form and how to work the cards.
5. Optional, for privacy questions from a client’s legal team: Privacy and data lifecycle.

Owner

Goal: decide where to invest, what a larger event costs, and what can go wrong.

1. Cost — cost per pack, per guest, per event, and the budget guard rails.
2. Capacity and Scaling scenarios — 70, 500, 2 000 and 10 000 guests.
3. Known gaps and Open decisions.
4. Roadmap.
5. Multi-tenant and white label — what it takes to sell to several agencies.
6. Playbook: new product — repeating the landing-to-leads chain for the next product.
7. Decisions (ADR) — why things are the way they are.
8. Secrets management — the list of accesses that must be handed over with the project.

Where to go next

• Glossary — look up any unfamiliar word.
• How to read the architecture section — the map of the technical pages.

---

Last verified: 2026-11-13 against ai-sticker-pack@b715418 and ai-stickers-landing@e350ff5.