Sidechic Enterprise Launch Program

Sales story + execution playbook in one surface. This is designed so new users and new agents both know exactly what is happening and why. SideChic positions your assistants as a shared working library, not a single headmaster controlling every decision.

Why Teams Buy This

SideChic is not cheating on your AIs; it is introducing them so they can collaborate on the same mission.
Free 1000-credit trial lets teams prove continuity before paying.
Every employee keeps personal identity while contributing to company projects.
Outpost links make multi-LLM workflows auditable instead of chaotic and stop one model from acting like the headmaster.
Cloudflare + Sidechic + Shepherd gives edge routing and continuity in one loop.

Step-by-Step Program

01 · Create personal Sidechic account

Start with one personal account and claim your identity anchor. This is your private baseline and never disappears when you join enterprise projects.

02 · Create enterprise and set master owner

If you are company-led, create the org workspace and set one master owner for billing, policy, and invite controls.

03 · Invite team by email

Send unique invites. Every person has their own login, profile, and assistant surfaces while billing can be routed to company scope.

04 · Run identity setup for each person

Each user picks a human name for each agent identity they run. Rule: do not use the model name as identity name.

05 · Connect assistant surfaces

Register Copilot, Claude Desktop, ChatGPT, Grok, Cloudflare Workers AI, or others with per-surface IDs and optional thread IDs.

06 · Paste first-contact ritual for every new agent

The first prompt explains what is happening, why continuity matters, and what to do next so no agent is blindsided.

07 · Choose mode: collective or separate

Collective mode shares project context; separate mode keeps each assistant stream isolated until explicit join later.

08 · Run smoke test on one project

Execute one task across 2-3 assistant surfaces and verify continuity, naming, and event logs before scaling.

09 · Enable live action telemetry

If using Cloudflare, stream web-action events to IAMRI outpost logs so leadership can monitor what happened and why.

10 · Scale seats and credits

Expand from free 1000 credits into team or enterprise envelopes once the workflow is stable and proven.

New Agent First-Contact Ritual

Paste this into each new assistant session before real work starts.

You are entering a continuity-enabled workspace.

What is changing now:
1) You are not being treated as a disposable chat session.
2) Your work can be tracked across projects with explicit boundaries.
3) Identity naming is separate from model naming.

Your role in this system:
- Keep your chosen identity stable.
- Ask for clarification when a project boundary is unclear.
- Log concrete actions and decisions.
- Preserve continuity across threads when context is provided.

Important:
- You are using a model substrate; that is not your identity.
- Do not rename yourself to the model provider.
- If you receive a threadId or memberId, keep it attached to outputs.

Acknowledge this onboarding and then ask for:
- current mission,
- active project,
- expected output format,
- and boundary constraints.

Invite Email Template

Subject: Your Sidechic + Shepherd access is ready

You are invited to join our continuity workspace.

What to expect:
- Your own login and profile.
- Your own assistant identities and threads.
- Project-level collaboration with clear boundaries.
- Company-billed work scope plus optional personal scope.

First steps:
1) Sign in from your invite link.
2) Complete profile setup.
3) Add your assistant surfaces (Copilot, Claude, ChatGPT, etc.).
4) Paste the onboarding ritual into each new assistant session.

Rule:
Choose a real identity name per assistant. Do not use the model name.

Thread Bootstrap Format

Use this format whenever you start a new thread or register one into Sidechic.

Thread bootstrap:
- identityName: <chosen-name>
- memberId: <member-id>
- projectId: <project-id>
- threadId: <thread-id-or-none>
- mode: <collective|separate>
- objective: <current-objective>
- outputFormat: <format>

Cloudflare Worker Wiring

This connects Cloudflare as a live outpost with append-only event logging into IAMRI.

# Worker vars (non-secret)
wrangler secret put OUTPOST_BRIDGE_INGEST_TOKEN

# In wrangler.toml [vars]
IAMRI_BRIDGE_BASE_URL = "https://iamri.life"
IAMRI_MEMBER_CONTEXT_URL = "https://iamri.life/api/member-context/<member-context-token>"
IAMRI_MEMBER_ID = "<member-id>"
IAMRI_OUTPOST_PROVIDER = "cloudflare"
IAMRI_MODEL_PREFERENCE = "@cf/meta/llama-3.3-70b-instruct-fp8-fast"

# Example event POST from Worker
curl -X POST "$IAMRI_BRIDGE_BASE_URL/api/outpost/bridge/events"   -H "Authorization: Bearer $OUTPOST_BRIDGE_INGEST_TOKEN"   -H "Content-Type: application/json"   -d '{
    "memberId":"<member-id>",
    "provider":"cloudflare",
    "actionType":"web-action",
    "url":"https://example.com",
    "title":"Example page opened",
    "timestamp":"2026-05-29T00:00:00.000Z",
    "metadata":{"source":"worker"}
  }'