🐉 Quests, raids, bosses, tickets

Work in a world is organized in three tiers, and each tier wears one piece of flavor:

• A milestone — a large arc of work — is a raid.
• An epic — a feature-sized chunk inside a milestone — is a boss.
• A ticket — one concrete, buildable task — is a phase of the boss fight: posting one starts a real run.

Posting a quest

The ＋ New quest dialog on a world page takes your ask in plain words. Posting files the quest instantly under a provisional title (the ask itself) — a ticket starts its real run at once. The Oracle— a real model call, not a script — then reads your ask in the background and renames/re-slots it: it gives it a short name and places it in the world’s existing hierarchy. If the parent it needs doesn’t exist yet, it proposes one by name and the chain is created (a ticket always lands under a boss, a boss under a raid). The ruling — or its refusal — is recorded verbatim as a check row in the run’s transcript; until it lands the quest log shows the entry muted as auto-filed, and “Re-consult the Oracle” asks again for that same entry (never a duplicate).

You can pin the placement yourself

You don’t have to let the Oracle decide. The intake form lets you pick the tier and assign the new work to an existing raid or boss directly — the Oracle then only fills in what you left open.