# 30-day content calendar

## Calendar rules

This calendar is counted from public launch day. Recommended draft launch start: Monday at 09:00 PT, board/legal-review required. If the public date moves, keep the sequence intact and shift day numbers.

Every post should follow these rules:

- Lead with product utility: portable memory, local-first custody, MCP, receipts, verifier output, relay/witness/gateway education.
- Use proof/demo assets rather than unsupported adjectives.
- Keep token language utility/governance/network-access oriented and legally cautious.
- Do not discuss secondary-market activity, speculative value, access promises, or benefit promises.
- Do not claim provider deletion, model forgetting, semantic forgetting, complete side-channel absence, or legal/compliance outcomes.
- Include anti-phishing and no-DM-token-sales reminders on token/governance/operator days.

## Reusable CTA bank

- Install Enigma locally.
- Create your first verifiable memory.
- Connect your MCP-capable agent.
- Verify a receipt offline.
- Join the community.
- Ask a question in the builder channel.
- Request an enterprise architecture review.
- Join the operator education list.
- Read the token utility model when legal-reviewed materials are published.

## 30-day schedule

| Day | Theme | Primary channel | Copy | CTA | Proof/demo asset |
| --- | --- | --- | --- | --- | --- |
| 1 | Category reveal | X + LinkedIn | Enigma is the memory card for AI: portable context, local-first custody, and offline-verifiable receipts across models and agents. AI work is becoming long-running; memory should not be trapped in one provider or hidden inside one app. | Watch the 60-second proof loop and install locally. | 60-second video: install → memory → receipt → offline verify. |
| 2 | Start-here community post | Discord + Telegram | Start here: install Enigma, create one local memory, export a proof bundle, and verify it. Official support is in public channels only. Enigma team members will never DM first to sell tokens, request wallet connection, or ask for seed phrases/private keys. | Run the local quickstart and post a redacted verifier screenshot. | Pinned command card with local install commands. |
| 3 | Local install walkthrough | X + Discord | The fastest way to understand Enigma is to run it. From this repository: `cd enigma`, `npm install -g .`, then initialize a local bundle, remember one preference, export, and verify. Local proof starts with a local vault. | Create your first verifiable memory. | Terminal GIF using `enigma init`, `enigma remember`, `enigma export`, `enigma verify`. |
| 4 | What receipts prove | LinkedIn + X | A valid Enigma receipt proves that a declared Enigma-mediated operation was signed, ordered, and committed under a stated policy boundary. It does not prove factual truth, model intent, hidden provider behavior, or deletion from external systems. | Read the proof boundary note and verify a sample receipt. | Receipt anatomy image: signed event, policy boundary, verifier verdict. |
| 5 | MCP setup | Discord + Farcaster | Enigma connects to MCP-capable agents over stdio. Run `ENIGMA_BUNDLE="$HOME/.enigma/bundle.json" enigma-mcp` or `ENIGMA_BUNDLE="$HOME/.enigma/bundle.json" enigma mcp serve`, then point your client at `enigma-mcp`. | Connect one MCP client. | Short clip showing generic MCP JSON and tools list. |
| 6 | Supported clients | X + Discord | Enigma connector profiles cover Claude Desktop, Cursor, Kimi Code, VS Code/Cline, Roo Code, OpenCode, and generic MCP. The generated entry points at `enigma-mcp` and sets `ENIGMA_BUNDLE` to your local vault bundle. | Run `enigma doctor` and connect your client. | Screenshot grid of connector IDs and `enigma connect` commands. |
| 7 | Verification challenge | Discord + Farcaster | Challenge: verify a sample receipt, then verify a tampered copy. A verifier that rejects changed evidence is doing its job. Trust is clearer when failure states are visible. | Post your valid and failed verifier results with private content redacted. | Valid-vs-tampered receipt demo clip. |
| 8 | User workflow: research memory | X | Stop rebuilding context from old chats. Save project preferences into an Enigma vault, retrieve scoped context for the next session, and keep provider-native memory as cache rather than the system of record. | Try a research-assistant memory workflow. | Demo card: save → search → context pack. |
| 9 | Builder office hours invite | Discord + X | Builder office hours: MCP setup, receipt fields, connector configs, and safe integration patterns. Bring a local bundle, a client, and one workflow you want an agent to remember. | Join office hours and ask in `#mcp-builders`. | Event card plus MCP command snippet. |
| 10 | Browser extension boundary | X + Discord | The browser extension scaffold is for explicit user-approved context insertion on supported provider pages. It stores target and receipt metadata for insertion records, not raw memory plaintext. It cannot force a provider to delete or forget. | Review the browser extension flow. | Screen recording: extension control requiring explicit click. |
| 11 | Enterprise framing | LinkedIn | Durable AI memory needs a control plane. Enigma keeps memory in local-first or customer-controlled vaults, retrieves scoped context under policy, and emits receipts that support audit review without claiming to prove closed-provider internals. | Request an enterprise architecture review. | Architecture diagram: vault → policy → gateway → receipt → verifier. |
| 12 | Gateway demo | LinkedIn + Discord | The gateway evaluates Enigma enterprise policy and signs decisions. It does not call model providers. Try `enigma gateway demo`, then inspect health and policy with the local server. | Run the gateway demo or ask for a private walkthrough. | Terminal clip: `enigma gateway demo`, `/health`, `/policy`. |
| 13 | Data minimization | X + LinkedIn | Public proof artifacts should contain commitments, roots, receipt IDs, addresses, and encrypted payloads where appropriate — not raw memory plaintext. Proof should reduce what people must reveal. | Review what is safe to share before posting support logs. | Safe-to-share checklist image. |
| 14 | Weekly shipped/current/next | Discord + LinkedIn | Week 1 update: shipped the launch proof loop, MCP setup sessions, receipt challenge, and enterprise gateway walkthrough. Current focus: setup friction, receipt literacy, and safe support. Next: relay/witness/gateway education. | Join the next demo or support clinic. | Weekly update card with one verifier screenshot. |
| 15 | Relay role education | Farcaster + Discord | Relays are optional infrastructure for opaque encrypted records and routing. They should not receive memory plaintext, prompts, transcripts, or conversation bodies. Local demo: `enigma relay demo`. | Learn the relay role and run the local demo. | Relay flow diagram: encrypted capsule only. |
| 16 | Witness/checkpoint education | Farcaster + X | Witnesses and checkpoints can help attest receipt/proof events and commitments without reading plaintext memory. Enigma receipts remain portable and offline-verifiable; network witnessing is an optional coordination layer. | Read the network roles guide when published. | Explainer image: local receipt plus optional witness checkpoint. |
| 17 | Token utility boundaries | Discord + Telegram | Token materials, if published, are about utility, governance participation, and access/coordination for optional relay/witness/gateway infrastructure. Token ownership is not company ownership, user-data ownership, holder proceeds, or a promise of compensation. Legal review is required before publication. | Read pinned token boundaries before posting token questions. | Pinned token-boundary card and anti-phishing notice. |
| 18 | Anti-phishing reminder | Telegram + Discord | Safety reminder: official team members will never DM first about token sales, special token access, wallet connection, seed phrases/private keys, or paid support. There are no official DM token sales. Use pinned links only and report impersonators. | Report suspicious accounts to moderators. | Safety graphic: no DMs, no seed phrases, no wallet-drainer links. |
| 19 | Governance boundaries | Farcaster + Discord | Governance for Enigma network infrastructure should be bounded to protocol parameters such as fee bands, operator thresholds, witness quorum rules, schema upgrades, grants, and verifier requirements. It does not control private memories or company operations. | Join the governance education thread. | Table: governance powers vs non-powers. |
| 20 | Solana implementation facts | Farcaster + X | Solana token planning should stay technical and precise. SPL tokens use Mint Accounts and Token Accounts. Token-2022 adds optional extensions; most extensions must be planned at mint creation. MetadataPointer can point to metadata; TokenMetadata can store name, symbol, URI, update authority, and custom metadata on the mint. | Review token utility docs after legal signoff. | Technical card: SPL Token vs Token-2022 planning notes. |
| 21 | Operator readiness | Discord + Farcaster | Future relay, witness, and gateway operators should expect published role requirements, service accountability, challenge rules, and legal/technical review before official participation. Joining an education list does not imply selection, compensation, token access, or service demand. | Join the operator education list. | Operator role matrix. |
| 22 | Developer integration idea | X + Farcaster | Build idea: a receipt viewer that loads an Enigma export, shows the lifecycle events, and explains what each event proves and does not prove. Good tools make boundaries obvious. | Build a receipt viewer prototype. | Mock receipt viewer screenshot. |
| 23 | Import/export caveats | Discord + X | Imports from provider exports or memory systems become canonical only after candidates are written through an Enigma vault and receive Enigma receipts. Source exports carry their own limitations. | Try an import workflow with non-sensitive test data. | Diagram: source export → candidate → Enigma vault → receipt. |
| 24 | Privacy boundaries | LinkedIn + Discord | Enigma reduces reliance on provider-native memory by keeping durable memory in local-first or customer-controlled vaults and injecting only scoped context. It does not claim that no side channel exists in every environment or that external systems deleted hidden copies. | Read the trust boundary FAQ. | Trust-boundaries graphic. |
| 25 | Portable memory challenge | Discord + X | Day 1 of the 7-day portable AI memory challenge: save one preference, retrieve it through an MCP-capable agent, export the receipt, and verify it. Redact private content before sharing. | Join the challenge. | Challenge card with commands. |
| 26 | Challenge: cross-client recall | Discord + Farcaster | Challenge day 2: use one client to save memory and another MCP-capable client to recall scoped context. The point is provider-neutral memory, not provider replacement. | Share a safe cross-client demo. | Split-screen: client A save, client B recall. |
| 27 | Challenge: delete/tombstone boundary | Discord + X | Challenge day 3: remove an Enigma-served memory from active use and verify the Enigma receipt trail. Boundary: this concerns Enigma-controlled state, not hidden provider copies or model weights. | Run the deletion/tombstone workflow and read the boundary note. | Demo card: remove from active Enigma serving → verify receipt. |
| 28 | Enterprise pilot invite | LinkedIn | For enterprise teams: Enigma can support private pilots focused on customer-controlled memory custody, policy-gated retrieval, signed boundary receipts, and audit-bundle review. No blanket compliance claims; the pilot produces evidence for your review. | Request a 2-week technical evaluation. | Pilot plan one-page image. |
| 29 | Community showcase | Discord + X | Showcase day: verified demos, MCP recipes, receipt viewer prototypes, safe support improvements, and proof-boundary corrections. We will feature clear mechanisms over broad claims. | Submit a demo for review. | Community showcase montage. |
| 30 | Month-one recap | LinkedIn + X + Discord | Month one recap: portable memory works when people can install it, use it across agent surfaces, and verify what happened later. Next focus: better workflows, clearer receipt UX, more MCP recipes, and legally reviewed network-role education. | Keep building, verify receipts, and join the next AMA. | Recap deck: shipped/current/next plus proof assets. |

## Daily channel notes

### Discord daily cadence

- Morning: one pinned daily action in `#announcements`.
- Midday: moderator-supported help block in `#install-help` or `#mcp-builders`.
- Afternoon: proof/demo artifact in the relevant channel.
- End of day: summarize common issues and one corrected misconception.

### Telegram daily cadence

- One announcement per day maximum during launch week.
- Event reminders and phishing/fraud alerts only after launch week.
- Redirect technical support to Discord and docs.

### X daily cadence

- One primary post or thread per day.
- One reply thread with a command snippet, screenshot, or proof boundary.
- Avoid token discussion outside scheduled utility-boundary posts.

### Farcaster daily cadence

- Developer/protocol-oriented posts on MCP, receipts, relay/witness/gateway, and governance boundaries.
- Invite implementation critique rather than speculation.

### LinkedIn daily cadence

- Two to three posts per week only.
- Use enterprise, category, architecture, and pilot language.
- Avoid casual crypto slang and unsupported privacy/compliance claims.

## Approved copy snippets

### Product one-liner

> Enigma is provider-neutral AI memory/proof infrastructure: portable Memory Passports, local-first vaults, MCP connectivity, and signed receipts for Enigma-mediated memory events.

### Receipt boundary

> Receipts prove that declared Enigma-mediated operations were signed, ordered, and committed under a stated policy boundary. They do not prove factual truth, model intent, uninstrumented side-channel absence, or deletion from external systems unless those systems provide independent evidence.

### Token boundary

> The Enigma token, if launched, is intended for utility, governance, and network access within optional relay/witness/gateway infrastructure. It is not company ownership, not a claim on assets or user data, does not grant holder proceeds, and does not promise compensation. Legal review is required before publication.

### Anti-phishing boundary

> Enigma team members and moderators will never DM first to sell tokens, offer special token access, request wallet connection, ask for seed phrases/private keys, provide secret token links, or offer paid support. There are no official DM token sales.

## Asset production checklist

For each asset, confirm before posting:

- It names a concrete product mechanism or command.
- It has one primary CTA.
- It avoids secondary-market, scarcity, and benefit-promise framing.
- It states proof boundaries when discussing receipts, deletion, privacy, enterprise, or token/network topics.
- It does not reveal raw memory plaintext, private keys, credentials, customer data, or private vault content.
- Token-related assets have legal review before publication.