Goal: decide whether AI Dev Brain (adb) was safe to open-source, and if so, ship it with a social campaign built on brain.mp4. Outcome: a pre-publication audit found the code secret-clean but flagged real confidentiality problems — a full OpenClaw/Propella business plan reachable from published tags v1.7.0–v1.9.0, pervasive Amazon fingerprints, and private-fleet over-share. On your call ("scrub every trace"), the tree was scrubbed (commit 8850c13, 31 files, +210 / −2362), verified green (build, vet, Go tests, extension 293/293), and republished as a fresh-history public repo (github.com/valter-silva-au/ai-dev-brain, single commit 4e74d41, no tags). The old repo was preserved private as ai-dev-brain-private. The campaign then went live: the brain.mp4 Gource render is posted on LinkedIn and this report captures its first-hour analytics plus a concrete next-steps plan.
Recap reflects available context + git facts; a long/compacted session may omit earlier steps. File lists are derived from git, not memory.
v1.7–v1.9, plus Amazon paths/Bedrock/internal codenames and private-fleet detail.8850c13: deleted stale/confidential docs + dead code + hive-era images, trimmed STORY.md, genericized employer/identity references across code, templates, docs, tests.go build/vet clean; affected Go tests pass; VS Code extension 293/293; full tracked-file sweep clean.ai-dev-brain-private (backup w/ full history+tags), created new public ai-dev-brain, pushed pristine single commit 4e74d41 over SSH.brain.mp4 "This looks like generative art… how I now run a business" post published on LinkedIn; analytics pulled (screenshots + omnictx).Honest read (too early to judge — give it 24–48h): a <1h post at 19 impressions / 13 reached with 0 visible engagement means LinkedIn hasn't decided to push it — the first-hour engagement signal is the gate, and it wasn't pulled. The 10s average watch on the clip says the "generative art" hook works (people start it) but they don't finish. 0 followers / 0 profile-views-from-post = views aren't converting to relationship yet.
The post runs under your "Cloud Architect @ Amazon Web Services (AWS)" badge, framed as "how I now run a business" with #entrepreneurship / #buildinpublic — while you're also job-hunting (AWS ProServe / Anthropic / OpenAI, per the fleet). That's the same employer/IP/moonlighting tension flagged during the repo scrub, now public under your AWS identity. Your call, but decide it on purpose: (a) keep it (you've judged you're clear), (b) soften "run a business" → "how I work" to cut moonlighting optics, or (c) confirm with AWS if unsure. Nothing in the code forces this — it's a positioning choice.
xurl installed on her box; it just needs your X API creds (dev app + funded plan) before she can post/measure.content skill + clip pipeline (this is TASK-00056: 2-week daily short-form cadence, Nina-drafted → you-approved).TASK-00031/00033 = "omnictx micro-SaaS — a private AI Dev Brain from a company link." The public adb + "I run my business on an AI Dev Brain" narrative is the top-of-funnel for that offer. Make the series ladder toward "I'll build yours."There is no LinkedIn analytics API — screenshot → omnictx (what you did) is the working loop for LinkedIn. X analytics need xurl + a funded API plan. The clip campaign's real dashboard is the content skill (tools/clip/content.json → reports/content.html). This is TASK-00053 (social-perf tracking, in progress).
| Artifact | What it is |
|---|---|
| github.com/valter-silva-au/ai-dev-brain | The shipped public open-source repo — fresh single-commit history (4e74d41), no tags, anonymously reachable (HTTP 200). |
| C:\Users\valte\adb-public-staging | Pristine fresh-history snapshot that was pushed to the public repo (tracked files only, no old history/tags). Disposable now. |
| memory/ai-dev-brain-public-release-prep.md | Durable release record — the audit verdict, the tag-leak warning ("never make ai-dev-brain-private public"), and what shipped. |
| reports/session-report-2026-07-16-0930.html | This report. |
| LinkedIn post (activity 7483316990091210752) | The live brain.mp4 campaign post ("how I now run a business"). |
| File | Change |
|---|---|
| docs/architecture/hive-mind-design.md | deleted −1422 — private 8-bot fleet design, /home/valter paths, OpenClaw |
| docs/adb-llm-wiki-monorepo-assessment.md | deleted −311 — stale internal critique, leaked local path |
| prd.json | deleted −164 — spec for the removed hive-mind (OpenClaw/Bedrock) |
| pkg/models/hive.go | deleted −137 — dead code (zero importers) |
| docs/images/08–12*.png | deleted — 5 hive-era campaign images |
| STORY.md | trimmed −250 — removed Ch 9–10 (Hive Mind / migration); fixed image paths |
| templates/claude/rules/standing-dos-donts.md · task-context.md | genericized — "Valter"→"project owner", ~/Code/amazon→$ADB_HOME, Bedrock note |
| internal/observability/chat.go | Bedrock model default → sonnet; identity string genericized |
issuesync select.go/sync_issues.go + tests, eventlog.go, launch.go/.ts, bootstrap*.go, hookengine_test.go, package.json | genericized code.amazon.com/code.aws.dev/CRUX/Taskei/proserve and local usernames |
| .pre-commit-config.yaml | removed fleet-specific comments (roots-co / Hermes / .env.aws) |
v1.7–v1.9; only a fresh history guarantees it can't leak.ai-dev-brain-private).brain.mp4 — "how I run a business" build-in-public angle.| Task | Status | Relevance |
|---|---|---|
| TASK-00053 — track personal-brand social performance (LI/X/IG) | in progress | This report + the screenshot→omnictx loop is that tracking. No LinkedIn API exists. |
| TASK-00056 — 2-week daily short-form cadence (TikTok-first, Nina-drafted) | backlog | Repurpose the brain clip across channels; this is the vehicle. |
| TASK-00031 / 00033 — omnictx micro-SaaS ("private AI Dev Brain from a company link") | backlog | The public adb + campaign is top-of-funnel for this product. |
| TASK-00029 — Content Agency v1 (productized recurring AI-content offer) | backlog | The distribution muscle this campaign is building. |
Fact sources used this run: git (commit 8850c13) adb tasks LinkedIn analytics (your screenshots) omnictx (corroboration) gstack (thin — 1 entry) transcript (wrong session).
8850c13) landed 2026-07-15, so it was pulled explicitly.2026-07-16 01:27, but the CLI only ranks/lists (content-read is MCP-only), so the below-the-fold engagement counts weren't retrieved. Numbers above come from your screenshots (authoritative).