Advanced Usage

Advanced Treasury docs should explain how workflows fit together without turning public documentation into an internal code map. The useful detail is the boundary: what starts the workflow, what system owns it, what output is expected, and where the work escalates when something fails.

Ownership boundaries

A Treasury workflow can span multiple services, but each page should still identify the surface that owns the user interaction.

Common ownership surfaces include:

• Public site - Brand and public entry.
• Discord - Live community, support, coordination, and ticket-style interaction.
• Docs - Stable reference and runbook material.
• Internal services - Background workers, APIs, transcript tools, automation, and shared infrastructure.

Do not document an internal service as a user-facing feature unless the user directly interacts with it.

Discord-operated workflows

Many Treasury workflows are coordinated through Discord. These docs should explain the user's action, the information they need to provide, and what response they should expect.

For Discord-operated workflows, document:

• Where the user starts.
• What context they need.
• What staff or automation will do.
• What completion looks like.
• What to do if the workflow stalls.

Automation and background work

Automation should be documented by outcome rather than implementation detail. A user usually does not need to know which worker, queue, or service handled the task. They need to know what the automation watches, when it acts, and how to escalate an incorrect result.

Use implementation details only when they help an operator diagnose a failure.

Transcript and recordkeeping flows

Any workflow that creates a transcript, audit trail, or persistent record should describe the source of truth. The page should make it clear where the record is created, where it can be viewed, and who should be contacted if the record is wrong or missing.

Integration pages

Integration docs should only name systems Treasury actually supports. If an external package, CLI, blog, or support channel is not Treasury-owned, avoid presenting it as part of the Treasury product.

For now, unresolved integration questions should route to the Treasury Discord.

Operational checks

Advanced workflows should include verification steps when the outcome matters. Good checks include:

• Confirming the user reached the correct surface.
• Confirming the expected artifact was created.
• Confirming the workflow completed in the right channel.
• Confirming escalation has enough context to continue without re-asking basic questions.