docs(identic-ai): brief notes from live run — gateway restart + company-id scoping

Live end-to-end run (Act 1 + Act 2, real OpenClaw 2026.6.1 + WhatsApp) passed,
but the "Connect Claudia to Paperclip" step cost ~12 min of diagnosis because:
(a) her paperclip MCP, spawned at gateway boot before the sandbox existed, read
empty until a gateway restart; (b) she scopes the queue read to the
company_id in her governance envelope, so a stale/ghost id reads 0 against a
full sandbox. Added both as explicit first-read prerequisites to runbook step 3.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: mjunaidca

identic-ai/AGENTS.md

@@ -146,7 +146,7 @@ The build runs in **two acts**. **Act 1 builds the twin**: you place Claudia's s
 
 **Act 2, stand up the company and put her to work:**
 
-3. **Connect Claudia to Paperclip.** NOW stand up the company: start the local sandbox, seed `seed-company.json`, wire the `paperclip` MCP. No hand-written HTTP client, no poller: a heartbeat or cron wakes her to read the queue (the `HEARTBEAT.md` in her workspace is the checklist).
+3. **Connect Claudia to Paperclip.** NOW stand up the company: start the local sandbox, seed `seed-company.json`, wire the `paperclip` MCP. No hand-written HTTP client, no poller: a heartbeat or cron wakes her to read the queue (the `HEARTBEAT.md` in her workspace is the checklist). **Two things that make her FIRST read succeed (live-verified, both cost a real run ~12 min of confusion otherwise):** (a) **restart Claudia's gateway after the sandbox is up** (`openclaw gateway restart`); her `paperclip` MCP spawns at gateway boot, so an MCP started before the sandbox existed reads empty. (b) **She scopes the queue read to a company id**, and that id lives where she reads it (her governance envelope's `company_id`). When you stand up the company, record the LIVE company id you just created there, creating the envelope if absent or retargeting it if present. If a `~/.openclaw/governance/delegated-envelope.json` already exists from prior work, retarget its `company_id` and clear any stale owner/company pointers FIRST, or she queries a ghost company and reads 0 while the sandbox is full.
 4. **Signing key + delegated envelope.** Build the `sign-decision` skill (ed25519 keygen + sign over canonical JSON). Write `delegated-envelope.json`; encode the gates in standing orders and the native `openclaw approvals` policy.
 5. **Verification layer + ledger.** The three gates (signer registered, signature verifies, action inside envelope) plus the `governance-ledger` skill writing each decision (posted or refused) to Neon, joinable to Paperclip's `activity_log` by approval id.
 6. **End-to-end demo.** Seed an approval flood into the sandbox (see `seed-company.json`'s `demo_approval_flood`), watch Claudia auto-clear the routine band and surface the consequential ones, run the `governance_ledger` query that shows the two-principal distinction.