Exports
Exports are sensitive administrative records. Bureaucramancer supports human-readable, machine-readable and spreadsheet-friendly templates from the same guild-scoped evidence bundle.
Targeting
/export player targets a verified Discord account. /export name can resolve usernames, display names, Tupper/proxy names or matching archived identity text. Date bounds and a configurable amount of surrounding message context can be included.
Templates
- Evidence bundle: HTML + JSON + CSV + Markdown.
- HTML: readable evidence timeline with edits, deleted-state markers and context.
- JSON: structured raw bundle for programmatic review or later processing.
- CSV: flat timeline for spreadsheet/filter workflows.
- Markdown: portable text report suitable for internal case notes and review.
Spreadsheet safety
User-controlled message content in CSV cells is neutralised when it begins with characters commonly interpreted as spreadsheet formulas. This reduces the risk of a Discord message becoming executable spreadsheet content when an exported CSV is opened.
What an export can contain
Depending on the target and available records: direct messages, Tupper audit attribution, context records, edit history, deleted-state records, private-thread indicators and attachment metadata. Protected attachment bytes remain a separate recovery object rather than being embedded into every evidence export.
Auditability
Export creation is recorded as a staff action. Dashboard Archive exports and sensitive reads also produce dedicated sensitive-read audit records. Keep downloaded exports only as long as the administrative purpose requires and restrict them to authorised staff.