Getting started
Bring up the safe Shardwright foundations for a guild before enabling future modules.
Intro
Readiness content for the current Shardwright foundation. Deferred behavior stays labeled until the backing service slice exists.
Section `intro` documents the current Shardwright readiness boundary and links back to route-scoped guild behavior where applicable.
Invite
Readiness content for the current Shardwright foundation. Deferred behavior stays labeled until the backing service slice exists.
Section `invite` documents the current Shardwright readiness boundary and links back to route-scoped guild behavior where applicable.
Configure
Readiness content for the current Shardwright foundation. Deferred behavior stays labeled until the backing service slice exists.
Section `configure` documents the current Shardwright readiness boundary and links back to route-scoped guild behavior where applicable.
First Rule
Readiness content for the current Shardwright foundation. Deferred behavior stays labeled until the backing service slice exists.
Section `first-rule` documents the current Shardwright readiness boundary and links back to route-scoped guild behavior where applicable.
Next Steps
Readiness content for the current Shardwright foundation. Deferred behavior stays labeled until the backing service slice exists.
Section `next-steps` documents the current Shardwright readiness boundary and links back to route-scoped guild behavior where applicable.
Callout Permissions
Readiness content for the current Shardwright foundation. Deferred behavior stays labeled until the backing service slice exists.
Section `callout-permissions` documents the current Shardwright readiness boundary and links back to route-scoped guild behavior where applicable.
GuildId is explicit. Secrets stay server-side. Deferred actions fail closed.| Concept | Foundation behavior |
|---|---|
| Guild isolation | GuildId is required for scoped routes, commands, cache keys and audit records. |
| External URLs | OAuth, invite and support URLs stay disabled until configured. |
| Safe deferred states | Backend-pending behaviors render disabled or not-ready rather than simulated success. |