Intake
Capture title, audience, problem, tools, sanitized example, human-review point, never-automate line, publish permission, and safe contact.
moderation queue / spec
How submitted workflows become public pages safely.
The Builder's Exchange should accept community contributions without becoming a spam board or privacy risk. This is the human moderation path before any workflow goes live.
Privacy redaction
Reject or redact real names, phone numbers, emails, customer IDs, health data, financial data, private DMs, and unreleased product details.
Safety review
Block workflows that automate clinical/legal/financial decisions, harassment, protected-group targeting, credential handling, or private-data scraping.
Editorial draft
Rewrite into the standard workflow format: problem, outcome, tools, steps, human-review gate, privacy note, related workflows, CTA.
Contributor approval
Send the draft back to the submitter. Publish only after explicit written approval and attribution preference is confirmed.
Publish + measure
Add the page, template link when useful, newsletter mention, and track workflow_view / submission follow-on events.
Queue fields
| Field | Purpose | Privacy note |
|---|---|---|
| submission_id | Internal row key | No user identifiers |
| status | new, needs_redaction, needs_followup, approved_draft, published, rejected | Operational only |
| risk_level | low, medium, high, blocked | High/blocked requires documented reason |
| redaction_notes | What was removed before drafting | Never include removed PII itself |
| contributor_approval | pending, yes, no | Publish only when yes |
| publish_slug | Planned public URL slug | Must not contain person/company private names unless approved |
Do not publish.
- Medical, legal, or financial advice automation without licensed review.
- Workflows that use private data without consent.
- Credential/token handling, surveillance, harassment, scraping private communities, or impersonation.
- Fake testimonials, fake user claims, or unverifiable revenue/traction claims.
No auto-publish.
Every public workflow must have a human reviewer, contributor approval, sanitized examples, and a clear human-review gate. If a workflow cannot meet those conditions, it stays private or gets rejected.