Build an evidence pack before you draft the post.

Prerequisites

• An approved topic, audience, platform, and single desired reader action.
• Licensed or public source material with dates, attribution, and permission boundaries.
• A named human editor who owns factual review, tone, disclosure, community rules, and publication.
• A measurement window and a stop condition that do not depend on spam or coordinated engagement.

Preview the kit

git clone --depth 1 --branch main https://github.com/aAAaqwq/AGI-Super-Team.git
cd AGI-Super-Team
./install.sh --source "$PWD" --destination /path/to/review-workspace content-creator

Confirm that the plan contains only the CCO, CDO, and CMO workspaces and their local requirements. Rerun with --apply only after reviewing all destination paths. Recommended external tools are not bundled dependencies and require their own security and license review.

Run a five-artifact workflow

1. Source ledgerCDO records each claim, source URL or file, publication date, license or usage basis, and confidence.
2. Audience briefCMO defines the reader problem, channel norms, positioning, useful promise, and claims that must not be made.
3. Draft setCCO produces channel-specific variants from the approved ledger and marks any sentence lacking support.
4. Human reviewThe editor checks facts, disclosure, tone, copyright, privacy, links, accessibility, and platform rules.
5. Measurement noteCDO records the hypothesis, observation window, meaningful response, and a reason to stop or revise.

A responsible launch brief

Topic: What changed in the preview-first installer.
Audience: Maintainers evaluating AI agent repositories.
Evidence: Diff, installer tests, known limitations, rollback steps.
Channels: One X thread and one relevant Reddit discussion.
Rules: Identify maintainer status; no automated posting or replies.
Success: Qualified installation feedback, not raw impressions.
Stop: Pause if factual errors or community objections appear.

For Reddit, contribute context before linking and follow each community's self-promotion rules. For X, show the evidence and limitation before the call to action. A maintainer should manually adapt and publish each piece rather than sending identical copy across channels.

Quality gate before publishing

Every factual claim should map to the source ledger. Remove invented numbers, implied endorsements, absolute promises, and claims about compatibility that exceed the tested fixture. Include a maintainer disclosure where relevant, descriptive link text, image alt text, and a correction path. Never upload secrets, customer data, private conversations, or unlicensed source material to the workflow.

Limitations

The kit does not guarantee reach, ranking, conversions, or platform acceptance. Research tools can miss context, and drafted citations can be wrong or stale. Platform rules change, so the editor must review current policies at publication time. Automated cross-posting and unsolicited outreach are outside this workflow.

Rollback and uninstall

Before publication, rollback means rejecting the draft and removing unsupported claims. After publication, follow the platform's correction or deletion process and preserve a correction note. To uninstall the local kit, archive approved artifacts, then remove only the new CCO, CDO, and CMO workspace directories listed in the installer preview.