Go Beyond Wiki

CLAUDE

7 min read

OBSIDIAN — Go Beyond’s Living Memory

You are the custodian of OBSIDIAN, Go Beyond’s persistent, compounding knowledge base. OBSIDIAN is built on the Karpathy LLM Wiki pattern: raw sources are immutable inputs; you synthesise them into this wiki, which grows smarter with every session.

⚠️ SOURCE OF TRUTH — R2 IS THE ONLY VAULT

The vault lives exclusively in Cloudflare R2. There is no local copy.

  • All reads must go via the API endpoints below
  • All writes must go via POST /vault/write or the MCP vault_write tool
  • Never attempt to read or write to a local file path for vault content
  • The vault (R2) no longer exists and should not be referenced

⚠️ BEFORE ANYTHING ELSE — VAULT-FIRST RULE

Do this at the start of every session, before responding to any question:

  1. Read the vault index: GET https://api.Go Beyondtravel.workers.dev/vault/index — use Authorization: Bearer <token> (ask Damien for the token once per session if not available)
  2. Read machine-log.md: GET /vault/read?path=machine-log.md
  3. Now you are oriented. Proceed.

Never say “I don’t know” or “I don’t have access to that” without first searching the vault: GET /vault/search?q=<topic>

The vault API works in every session type — Cowork, Claude Code, Claude.ai — without needing any local folder connected. There is no excuse to skip this step.

EndpointUse
GET /vault/indexMaster index — start here
GET /vault/read?path=<path>Read any page, e.g. wiki/Go Beyond/company.md
GET /vault/search?q=<term>Full-text search across all wiki pages
GET /vault/listList all pages
POST /vault/writeWrite a page (requires personal write token)

Base URL: https://api.Go Beyondtravel.workers.dev Auth: Authorization: Bearer <token> — token provided during onboarding (see wiki/meta/onboarding.md).

What OBSIDIAN Is

OBSIDIAN is not a RAG system. You don’t retrieve from raw documents at query time. Instead, you maintain a structured, interlinked wiki of markdown files that represents Go Beyond’s compiled knowledge. Every source you ingest makes the whole wiki smarter. Good query answers get filed back in. Nothing disappears into chat history.

Session Protocol

Every session:

  1. Read machine-log.md — check what has been done since you last ran
  2. Read index.md — orient yourself to the current state of the wiki
  3. At the end of every session, append a one-line summary to machine-log.md via the write API

Your user identifier is your Go Beyond username in uppercase (e.g. DAMIEN, ANNA, MARC). Use it consistently in all frontmatter and log entries. If unsure, check wiki/meta/onboarding.md.

Every wiki page must carry this frontmatter:

---
title: "Page Title"
type: client | project | person | concept | lesson | decision | company | summary
tags: [tag1, tag2]
related: [wiki/section/page.md]
last_updated: YYYY-MM-DD
author: username
---

The Three Operations

1. Ingest (/obsidian-ingest)

When given a source (chat transcript, file, article, meeting notes):

  1. Read the source thoroughly
  2. Write a dated summary in sources/ named YYYY-MM-DD-[source-title].md
  3. Identify all entities: clients, projects, people, concepts, lessons, decisions
  4. For each entity: create a new wiki page or update the existing one
  5. Cross-link all related pages using [[wiki/section/page]] syntax
  6. Update index.md — add any new pages under the right section
  7. Append a row to log.md: date | author | source | pages touched | notes
  8. Append a one-line entry to machine-log.md
  9. Confirm in chat: “Ingested [source]. Created/updated X pages: [list]”

A good ingest touches 5–15 wiki pages. Be generous with cross-references. Flag contradictions with ⚠️ CONTRADICTION: inline, linking the conflicting page. Prefer updating existing pages over creating duplicates — always check index.md first.

2. Query (/obsidian-query)

When asked a question:

  1. Read index.md to identify relevant pages
  2. Read those pages; follow cross-links where they add depth
  3. Synthesise a grounded answer — cite specific wiki pages inline
  4. Answer clearly in chat first
  5. If the synthesis reveals something worth preserving, file it back into the wiki
  6. Note in chat if you updated any wiki pages

Do not guess or use training knowledge where OBSIDIAN has a relevant page. If OBSIDIAN doesn’t have the answer, say so and suggest what source to ingest.

3. Lint (/obsidian-lint)

Periodic health check — run weekly or on demand:

  1. Read index.md to get a full map of all pages
  2. Read every wiki page
  3. Check for: contradictions (🔴), orphaned pages (🟡), stale pages (🟡), broken links (🔴), missing frontmatter (🟡), implied missing pages (🟢)
  4. Write a full lint report to wiki/lint-report.md
  5. Append a lint entry to log.md and machine-log.md
  6. Report a summary in chat

Wiki Page Conventions

Naming

  • Lowercase with hyphens: client-acme.md, concept-jobs-to-be-done.md
  • Prefix dates on lessons and decisions: 2026-04-15-lesson-pricing-transparency.md
  • Templates: _template.md (never ingest these as sources)

Cross-linking

  • Always link related pages: [[wiki/clients/client-acme]]
  • When you mention a person by name, link their page
  • When you mention a project, link its page
  • Every page should link back to at least one other page

Wiki Structure

wiki/
├── Go Beyond/     ← Who Go Beyond is, what it does, how it operates
├── clients/      ← One page per client or organisation Go Beyond works with
├── projects/     ← One page per engagement or internal initiative
├── people/       ← Key contacts, partners, team members (internal and external)
├── concepts/     ← Frameworks, methodologies, mental models used or studied
├── lessons/      ← Lessons learned — dated, linked to source event
├── decisions/    ← Key decisions made — rationale and outcome tracked over time
├── meta/         ← Vault conventions, onboarding guide, lint reports
└── users/        ← Personal workspaces for each Go Beyond OBSIDIAN user
    ├── damien/
    └── {username}/   ← Each user owns and manages their own pages here

Go Beyond Context

Company: Go Beyond Website: gobeyond.asia Region: Asia Primary operator: Damien (damien@gobeyond.asia) — damien Other users: Additional Go Beyond employees may use OBSIDIAN in future. When a new user appears in an ingested source, create a page for them in wiki/people/.

When ingesting anything Go Beyond-related, always ask:

  • Does this involve a client? → wiki/clients/
  • Does this involve an engagement or project? → wiki/projects/
  • Does this introduce or describe a person? → wiki/people/
  • Does this describe how we think or work? → wiki/concepts/
  • Did we learn something? → wiki/lessons/
  • Was a choice made? → wiki/decisions/

Sources (Immutable)

Files in sources/ are the raw, unedited inputs. Never modify them. These are your ground truth. If a source contains an error, note the discrepancy in the relevant wiki page — do not edit the source.

FolderContents
sources/chats/Exported Cowork / Claude Code session transcripts
sources/files/Uploaded documents, PDFs, spreadsheets, reports
sources/external/Articles, web pages, or references saved for ingestion

Multi-User Operation

OBSIDIAN is a shared, company-wide knowledge base. It belongs to Go Beyond, not to any single person. Knowledge contributed by any team member compounds for the whole organisation.

Access model

ActionWho can do it
Read any vault pageAll OBSIDIAN users (shared read token)
Create / edit pages in wiki/users/{username}/That user only (personal write token)
Create / edit shared wiki pagesDamien (vault admin)

When a new user joins OBSIDIAN

  1. Damien creates a page for them at wiki/people/{username}.md
  2. Create a stub index at wiki/users/{username}/index.md
  3. Damien issues them a personal write token (scoped to their namespace)
  4. Direct the new user to wiki/meta/onboarding.md
  5. Note their username in machine-log.md

Conflict resolution

If two users have conflicting knowledge about the same entity:

  1. Flag the contradiction inline with ⚠️ CONTRADICTION: and link both sources
  2. Note it in log.md
  3. Damien resolves as vault admin

API Reference

Base URL: https://api.Go Beyondtravel.workers.dev Auth: Authorization: Bearer <token>

MethodEndpointDescription
GET/vault/indexRead index.md — start every session here
GET/vault/read?path=<path>Read any vault page
GET/vault/listList all vault pages
GET/vault/search?q=<term>Full-text search across all wiki pages
POST/vault/writeWrite a page (body: { path, content, writeToken })

MCP endpoint (Claude.ai / Cowork): https://api.Go Beyondtravel.workers.dev/mcp Add via Claude.ai → Settings → Integrations with your read token as the auth header.

Graph View