Building and reviewing a charter from Slack

When a team already exists and works in Slack, Particulars can use recent channel history to draft a starting charter and later notice when the work has moved.

The system's output is evidence for an editor. It is not the truth until a person reviews it.

How it works

1. Install the app. One install per Slack workspace. The button above begins the authorization flow.
2. Connect the workspace to an organization. After Slack returns you to Particulars, choose or create the organization the workspace belongs to. The bot token is scoped to that organization and encrypted at rest.
3. Choose channels. From the organization dashboard, choose New team → From Slack. Particulars lists channels the bot has joined. For a private channel, invite @Particulars in Slack, then reopen the picker. Connecting a channel from a charter's Settings → Sources is the separate, ongoing review connection.
4. Build a draft. Particulars reads recent messages, identifies evidence about the team's purpose, work, roles, decisions, and interfaces, and proposes a draft. If there are fewer than 30 substantive human messages across at least 3 active days, it stops before calling the model.
5. Review the evidence. Every proposed item links to numbered Slack excerpts. Edit anything, choose the optional measures, decision rights, and guidelines that fit, and add what the channel cannot know. Nothing becomes the published model until an editor confirms it.
6. Keep it connected. On a regular cadence, Particulars compares the current charter with recent evidence and flags meaningful drift.

Scopes and data

Particulars requests only the Slack scopes needed for connected channels:

• channels:history, groups:history — read messages in channels a charter is connected to
• channels:read, groups:read — list channels so an editor can choose them
• users:read, users:read.email — resolve Slack IDs to people
• app_mentions:read — receive questions that explicitly mention Particulars; team guidance runs only in a channel connected to one team
• commands — handle the /charter command
• chat:write — answer commands and mentions, send requested messages, and post enabled team intelligence

Particulars does not read direct messages, files, or unconnected channel history. An explicit mention in another joined channel is used only to explain that a team connection is required.

Raw message text is not kept as a permanent record. Temporary draft-job data is retained only long enough to complete or retry the requested generation, then deleted according to the Privacy Policy. Stored outputs are the charter, the editor-confirmed record, and limited derived signals needed for the product to work.

AI usage and limits

Ordinary AI is unmetered on paid plans. Drafts, scheduled reviews, decision detection, and enabled team intelligence do not create token overages.

The free plan limits how much of the model can be connected and reviewed, rather than presenting a running token counter.

Evidence quality

Particulars drops any model claim that does not cite an excerpt it actually supplied. Role suggestions use a separate deterministic check: a Slack email must resolve to a verified Particulars identity that is currently a member of the same organization. Unmatched people remain visible as Slack contributors but the role stays unassigned.

Removing the integration

A Slack workspace administrator can uninstall Particulars from Apps → Manage Apps. Tokens are revoked immediately.

An organization owner can also disconnect Slack from Organization settings → Connectors.

What's next

• Linking & nesting — turn references into relationships
• Security & privacy — what is stored and where
• Agents — use the model as operating context