Skip to content
Fork Docs
Guide v1

/social divorce

Dissolve your current stored relationship, engagement or marriage.

Availability

Section titled “Availability”

Public source-edition command; execution remains conditional on installation, server policy and the running service. This reference is built from the repository, not a live Discord registration probe. Explicit registration contexts: server, bot DM, private channel.

Syntax

Section titled “Syntax”
/social divorce

Angle brackets indicate required input; square brackets indicate optional input. In Discord, choose the command and fill its named options, rather than typing the brackets.

Parameters

Section titled “Parameters”

No registered options.

Permissions

Section titled “Permissions”

No native default-member permission is declared for this path, and no additional native member permission was identified in its reviewed direct handler.

Fork role access is evaluated using the underlying divorce policy key, even when the slash name is grouped. Native Discord permission checks remain separate from Fork role grants. Sensitive commands fail closed before valid setup; native Administrator bypasses Fork’s role matrix, not Discord’s bot permissions or target hierarchy. See Permission model.

Examples

Section titled “Examples”
Slash options
/social divorce
Prefix equivalent and aliases
Default prefix
f!divorce

Default prefix: f!; installations can configure another. Handler aliases: breakup, ayril, bosan. Aliases are prefix names, not additional slash commands.

Grouped prefix routes also delegate to the original handlers, but aliases retain that handler’s argument parsing. Conflicting aliases are rejected as ambiguous. Prefix replies are generally visible in the channel; prefer slash privacy controls for sensitive personal data.

Expected result

Section titled “Expected result”

The caller receives confirmation/cancel controls. Only the caller can confirm dissolution.

Failure cases

Section titled “Failure cases”

No existing relationship, cancellation, expired controls or storage failure can leave the relationship unchanged. Check the returned error, current bot status and the relevant server permissions. A timeout or uncertain receipt is not proof that nothing happened; inspect state before repeating a mutation.

Usage limits

Section titled “Usage limits”

The caller has 30 seconds to confirm or cancel. An expired control does not confirm dissolution.

Section titled “Related commands”
Section titled “Related guides”

Source edition v1 · Registration, direct handler and shared authorization review are hash-bound in the local documentation validation. This is not a production feature-availability certification.