Treasury|Treasury Docs

Production Readiness Checklist

Use this checklist before treating a Treasury workflow, docs page, or support path as production-ready.

User path

✓ The entry point is clear

  • The page tells the user whether to start on the main Treasury site, in Discord, or in another named surface.

✓ The next action is obvious

  • The user knows what to click, what to provide, or which page to read next.

✓ Unsupported channels are removed

  • The page does not point users to support email, inherited blog posts, inherited packages, or other channels that Treasury does not use.

Support path

✓ Discord is the live support destination

✓ Escalation context is defined

  • The page explains what context a user or operator should gather before escalating.

✓ The expected outcome is stated

  • A support workflow should define what "done" looks like.

Documentation quality

✓ The page is Treasury-specific

  • The page should not read like generic cloud platform documentation unless Treasury actually offers that workflow.

✓ Old inherited platform language is removed

  • Product copy should use Treasury naming and Treasury-owned links.

✓ Technical residue is intentional

  • Any remaining external command, package, or hostname should be present because the page still truly depends on it.

Operational safety

✓ Ownership is clear

  • The page should not merge separate systems into one vague workflow. If Discord, docs, automation, transcripts, and internal services all participate, their roles should be described separately.

✓ Records and artifacts are named

  • If the workflow creates a transcript, log, ticket, proof, or other artifact, the page should say what artifact exists and where the user should expect to see it.

✓ Failure handling exists

  • The page should tell users how to proceed if the workflow fails, stalls, or produces the wrong output.

Final check

Before publishing, confirm that the page builds locally, has no broken MDX, links only to supported Treasury surfaces, and gives a clear path back to Discord when live help is needed.