SetupHow the two brains were built
Teleport went from a folder of Obsidian notes to two live, cited brains in one sitting. Here's the whole path.
Two brains, one project
A public Help brain for customers and a private Internal brain for the team — separate on purpose, so nothing internal can ever leak into a customer answer.
Export the team's knowledge
The team already wrote everything down in Obsidian. One zip of the vault — 1.4 MB of notes, decisions, and playbooks — is the whole starting point.
Import — every note becomes a source
Drop the vault into the Internal brain. Each note is read, synthesized into a clean wiki page, embedded, and graphed — grounded, cited, and askable.
171 sources, synthesized
The Internal brain now holds 171 ready sources — the Marketing Playbook, Posted Log, agent specs, campaign notes — every one a clean wiki page the agents can pull by name.
The Help brain stays public-safe
Only customer-facing material goes here — Features and the Help & FAQ pulled from teleport.eco. This is the only brain the public FAQ widget will ever read.
Information flowWho reads what, who writes what, where approval sits
Teal = reading context. Indigo = writing knowledge in. Amber = a human approval gate. Grey = live status in the tracker. Note the privacy boundary: nothing internal reaches the public widget except content you deliberately curate into the Help brain.
The contractWhat each agent reads, writes, and is gated by
This is the precise version of the diagram — drop it straight into each agent's role/SKILL prompt so behaviour is explicit.
| Agent | Reads from | Writes to | Gated by |
|---|---|---|---|
| Marketing / Social | Internal — Playbook, Product Context, Posted Log + State — what's shipped & announceable | Internal — a new Posted Log entry + Assets — the creative it made | Founder approval before any post goes live |
| Analytics | Post platforms (X / Instagram) — raw stats | Internal — stats appended to Posted Log; weekly Performance Insights (raw numbers only, never its own conclusions as new sources) | None — append-only, raw data |
| Dev · Claude Code | Internal — Product Context, Decisions + State — approved tickets / specs | Code → repo; on ship: close ticket (State) + a "Shipped" note (Internal) | Founder approval before deploy |
| Public FAQ widget | Help brain only | Nothing (optionally: unanswered-questions log to founders) | Hard boundary — never reads Internal |
Anchor docsFive templates to drop into the Internal brain
Add each as a note source in the Internal brain. Keep the titles exactly as written — the agents find them by asking for them by name. Replace the [bracketed] placeholders with your real content.
The first thing the Marketing agent reads every time — voice, pillars, and the rules of the road.
# Teleport — Marketing Playbook _Last updated: [date] · owner: [founder]_ ## Brand voice - Tone: [confident, plain-spoken, builder-to-business-owner] - We sound like: [a helpful operator, not a hype machine] - We never sound like: [jargon, "revolutionary", "game-changing"] ## What Teleport is (one line) [Free iOS app to capture your business in 360 and publish to Google Maps.] ## Audience & their pain - Primary: [restaurants, retail, real estate, hotels, museums] - Pain: [static photos underperform; pro tours cost $300-$10k] ## Content pillars (rotate — never twice in a row) 1. Local SEO wins — Google Business Profile / Maps engagement 2. "Shot on iPhone" — no gear, ~60-second capture 3. Industry use cases — retail, real estate, hospitality 4. Before / after — flat listing vs. a 360 space 5. Customer results — visits, time-on-listing, conversions ## Do / Don't - DO: lead with the business outcome; one clear CTA per post - DO: cite a real number only if it's in the brain - DON'T: mention unreleased features (check State first) - DON'T: invent metrics; DON'T repeat a recent angle ## CTAs & links - Primary CTA: [Download free] / [See a live tour] - Canonical links: [App Store URL] · [teleport.eco/tours] ## Channels & cadence - Instagram [daily] · X [daily] - Handles / hashtags: [@teleporteco · #...] ## Current campaign focus (update me often) [e.g. push the free Business Audit this month]
What each feature is and how to talk about it — for both Marketing and Dev. Status is NOT here; it lives in the tracker.
# Teleport — Product Context _Context only. Feature STATUS lives in the tracker, not here._ ## Feature: [360 Video Capture] - What it is: [record a walkthrough video inside a space] - Who it's for: [Pro users; real estate, hospitality] - Positioning angle: [motion sells a space better than stills] - Key benefit: [more time-on-listing] - Proof points: [stat or quote — only if grounded] ## Feature: [Shoppable product tags] - What it is: [tag items with buy-now links] - Who it's for: [retail / e-commerce] - Positioning angle: [turn a tour into a storefront] - Key benefit: [browse-to-buy in one tap] - Proof points: [...] (repeat one clear heading per feature) ## Shipped log (append-only — additive, never edited) - [2026-06-01] — Shipped: [feature] — announce angle: [...]
The freshness memory. The Marketing agent reads it to avoid repeats; the Analytics agent appends stats to it later.
# Teleport — Posted Log _Append-only. Newest on top. One block per post. Stats filled in ~72h after posting._ ## [2026-06-15] · Instagram · Pillar: Local SEO - Hook: [the line that opens the post] - Angle: [the specific take] - Asset: [link to the creative] - Live link: [post URL] - Stats: reach [__] · saves [__] · CTR [__] · profile taps [__] ## [2026-06-14] · X · Pillar: Shot on iPhone - Hook: [...] - Angle: [...] - Asset: [...] - Live link: [...] - Stats: [pending]
Themes, not raw numbers — the Analytics agent refreshes this weekly so Marketing can pick what to do more of.
# Teleport — Performance Insights _Refreshed weekly. Patterns & learnings — raw numbers stay in the Posted Log._ ## Week of [date] - Top performer: [post] — why we think it worked: [...] - Underperformer: [post] — hypothesis: [...] - Pattern so far: [e.g. before/after beats talking-head 2:1] - Angles to try next: [...] - Don't repeat: [angle that's now stale]
Why you chose things. The highest-value grounding for the Dev agent — and it keeps the two co-founders aligned.
# Teleport — Decisions (ADRs) _Append-only record of why. Newest on top._ ## [2026-06-10] — [Decision title] - Decision: [what we decided] - Context: [the situation that forced it] - Options considered: [A] / [B] / [C] - Why this one: [the reasoning] - Implications: [what it changes for product / marketing] - Owner: [founder]
Two conventions that keep this working.Raw sources in Ounie are immutable and synthesis isn't instant, so treat every log as append-only— add a dated entry, never rewrite history. And never store live status here: "is feature X done?" is answered by the tracker, not the brain. The brain tells the agents what and why; the tracker tells them where it stands right now.
One topic per doc with the exact titles above. Retrieval is semantic, so clear, consistent titles are what let an agent reliably pull "the Playbook" or "the Posted Log" when its prompt asks for them.
Build logHow the Teleport brain came together
The steps we completed setting up Teleport's two brains — each one grounded, cited, and done.
Added “Teleport Help & FAQ”
HelpLink · teleport.eco · ready
Added “Teleport Features”
HelpLink · teleport.eco · ready
Anchor docs synthesized — Playbook, Product Context, Posted Log, Insights, Decisions
Internal5 notes
Imported 171 sources from Obsidian
Internalteleport-vault.zip · all Ready
What's nextWiring the brains into the business
The brains are built. Two moves turn them into a working part of the team.
FAQ widget on teleport.eco Next
Embed the Help brain's Ask bubble so visitors get cited answers on pricing, features, and how 360° capture works — drawn only from the public-safe Help brain, never the Internal one.
Connect the Internal brain to TabTab AI agents Next
The Marketing agent reads context from the brain — Playbook, Product Context, Posted Log — drafts social posts, and (after a founder approves) writes each one back to the Posted Log so the brain never repeats an angle.
Want this setup running your work?
Two brains, the same loop — feed it, wire in your agents, let it answer with citations.
Build your brain