Content launch — 30 days

Goal: Make developers, ecosystem teams and auditors see CoreGuard as the name for execution proof. One message, repeated everywhere: Logs assert. CoreGuard proves.

Weekly rhythm

Post on X daily, LinkedIn 3× a week, one GitHub Discussion post a week.

15 ready posts

1. EN: An AI agent just moved money on-chain. Can you prove it did only what it was authorized to do? Its log can't. CoreGuard can. 🧵 AR: وكيل AI لسه حرّك فلوس على السلسلة. تقدر تثبت إنه عمل بس اللي اتصرّحله؟ السجل مايقدرش. CoreGuard يقدر.
2. EN: A log is written by the same process that executed. That's not evidence, that's testimony. AR: السجل بيكتبه نفس البرنامج اللي نفّذ. ده مش دليل، ده شهادة.
3. EN: Proof Artifact #1: block 38712625 on Core Mainnet. Agent signed an intent, Firewall said ALLOW, receipt re-derived independently. L1 VERIFIED. Check it yourself ↓
4. EN: Our rule: UNKNOWN stays HELD. If we can't verify it, it doesn't execute. Fail-closed by design. AR: قاعدتنا: أي حاجة UNKNOWN بتفضل HELD. لو مش هنقدر نتحقق منها، مش هتتنفّذ.
5. EN: VERIFIED ≠ SAFE. We publish what we did NOT check (3 honest NOT_RUN entries). Security vendors who hide their gaps are just another log.
6. EN: npm install && npm run demo:90s:live — 90 seconds to re-verify a real Mainnet execution. No keys, no funds.
7. EN: Building for #PiHackathon: every Pi payment gets a receipt anyone can verify. Day 1 👇
8. AR: بنبني لـ #PiHackathon: كل دفعة Pi هيبقى ليها إيصال أي حد يتحقق منه. اليوم الأول 👇
9. EN: The Verified Merchant badge only renders from verified receipts. Change one byte and it fails closed. Trust badges should work like this.
10. EN: Disputes shouldn't be screenshots. DDE/1 creates an offline evidence pack any arbitrator can replay.
11. EN: Core records execution truth. CoreGuard verifies it conformed to authorization. Complementary, not competing. @Coredao_Org
12. EN: Soroban + Freighter + a fail-closed Firewall: what remittance rails need before settlement. Coming to Stellar. @StellarOrg
13. EN: Free forever: the protocol, the spec, every verifier. We sell infrastructure, never facts.
14. AR: من مصر للعالم: بنبني طبقة الإثبات لاقتصاد الوكلاء. مفتوحة المصدر، وأي حد يقدر يتحقق.
15. EN: Looking for 3 integration pilots: a wallet, a DEX and an AI-agent platform. If you want receipts in front of your users, DM us.

3 articles (outlines)

Article 1 — "Your agent's log is not evidence"

Hook → why logs fail (self-written, unanchored, editable) → what evidence requires (re-derivable, anchored, independent) → CoreGuard's chain → call to run the demo.

Article 2 — "Anatomy of Proof Artifact #1"

Walk through the Mainnet tx line by line: intent, signer recovery, policy, receipt, anchor, and the three NOT_RUN entries and why we publish them.

Article 3 — "One ladder, three networks"

Core DAO (BTCFi receipts, live), Stellar (Soroban anchors, remittance disputes), Pi (commerce shield). Same engine, different product for each ecosystem.

Publish on dev.to, Medium, Mirror and Hashnode; cross-post a short version on LinkedIn.

GitHub & search visibility

Repo description: Verifiable execution truth layer for Bitcoin DeFi & AI agents — receipts, fail-closed firewall, dispute evidence. Live on Core Mainnet. Core DAO · Stellar · Pi Network.

Topics to add: ai-agents, bitcoin-defi, core-dao, stellar, soroban, pi-network, web3-security, smart-contract-security, verifiable-computing, eip-712, firewall, escrow, blockchain, defi, agent-economy, zero-trust, solidity, typescript.

Do also:

• Pin CoreGuard and .github on the org profile.
• Set the website field to the published site URL.
• Add a social preview image (Settings → Social preview) using og-cover.svg exported to PNG 1280×640.
• Publish a GitHub Release (v0.x with release notes) — releases show up in feeds and search.
• Enable Discussions and open "Show & tell: verify Proof Artifact #1 yourself".
• Submit to awesome lists: awesome-web3-security, awesome-ai-agents, awesome-stellar, awesome-core.