◆
Obsidian
✦
AI Agent
◉
Human Interaction
The vault.
Markdown, in a graph. Plain files I can read in any tool, forever.
Football · Data · AI

The Compounding
Second Brain

Persistent Memory for Football Data

Inspired by Andrej Karpathy

Every time we start a task...

...we lose time explaining context.

We fine-tune the same answers,
over and over.

And when the conversation ends,
the knowledge ends with it.

There has to be a better way.

The proposal

A wiki that remembers for me.

Persistent. Linked. Compounding.

Pillar · 01
Pillar · 02
Pillar · 03
Architecture

Three layers, one graph.

Layer 01
Raw
Articles, PDFs, HTML, JSON, YAML. Immutable. Read from, never modified.
Layer 02
Wiki
LLM-written markdown. Entity pages, concept pages, source summaries. Linked.
Layer 03
Schema
CLAUDE.md — co-evolved rules. The conventions the agent follows.
388
wiki pages, today.
7Providers
0Orphan pages
0Broken links
~270Match-data pages
124Physical-data pages
SkillCorner
60 pages
StatsBomb
12 pages
OPTA
98 pages
Sportradar
46 pages
Wyscout
46 pages
Catapult
112 pages
VALD
9 pages
IMPECT
4 pages
Make it yours

One vault. Any agent.

Wire Claude Code or Codex so the vault is available from any folder, in any session.

01
Access
~/.claude/settings.json or ~/.codex/config.toml grants the agent access to the vault folder.
02
Global awareness
~/.claude/CLAUDE.md or ~/.codex/AGENTS.md tells every session the vault exists.
03
Vault contract
<vault>/CLAUDE.md or <vault>/AGENTS.md points to the durable wiki conventions.
Step 01 · Grant access

Add the folder to permissions.

~/.claude/settings.json
{
  "permissions": {
    "additionalDirectories": [
      "/path/to/your/wiki"
    ]
  }
}

Every Claude Code session can now read and write inside that folder — regardless of which directory you launched from.

Step 02 · Make Claude aware

Drop a global pointer.

~/.claude/CLAUDE.md
# Persistent Football Knowledge Vault

Path:   /path/to/your/wiki/Football Knowledge Vault
Schema: /path/to/your/wiki/CLAUDE.md

When the user mentions "the vault", wants to ingest a
football source, or names a provider (SkillCorner,
StatsBomb, OPTA, Wyscout, ...) — engage with this
vault and read its CLAUDE.md for full conventions.

Loads into every session. The keywords become Claude's auto-triggers.

Step 03 · The schema

The contract between you and the agent.

<vault>/CLAUDE.md

The schema document tells Claude how to behave inside the vault.

  1. The three-layer architecture (raw / wiki / schema)
  2. Ingest · Query · Lint — the workflow steps to follow
  3. Obsidian wikilink rules (no [ or ] in filenames)
  4. Log format and date conventions (absolute dates only)

Update it when reality teaches you something new.

Codex setup

Same idea. Codex names.

Codex uses global AGENTS.md for awareness and config.toml for persistent writable roots.

01
~/.codex/config.toml
Add the vault to writable_roots so workspace-write sessions can use it from unrelated folders.
02
~/.codex/AGENTS.md
Global instructions: where the vault lives, what triggers it, and how Codex should query it.
03
<vault>/AGENTS.md + codex.md
Local bridge plus the detailed operating manual for wiki maintenance.
Codex · Grant access

Add the vault to writable roots.

~/.codex/config.toml
# Persistent extra directory for workspace-write sessions
[sandbox_workspace_write]
writable_roots = ['C:\Users\Tiago\Wiki Knowledge']

This is the Codex config equivalent of Claude Code's additionalDirectories. One-off sessions can also use codex --add-dir "C:\Users\Tiago\Wiki Knowledge".

Codex · Make it aware

Create a global AGENTS.md.

~/.codex/AGENTS.md
# Global Persistent Context

Vault:  C:\Users\Tiago\Wiki Knowledge\Football Knowledge Vault
Manual: C:\Users\Tiago\Wiki Knowledge\codex.md
Index:  ...\Football Knowledge Vault\index.md

When Tiago mentions "the vault", "ingest", SkillCorner,
StatsBomb, OPTA, Wyscout, IMPECT, Catapult, VALD,
or tracking/event/physical data — read codex.md,
then read the vault index, then search with rg.

Codex reads this global file before work starts, even when launched from another project.

Codex · Vault bridge

Keep a local entry point.

<vault-workspace>/AGENTS.md
# AGENTS.md

This directory is Tiago's persistent football knowledge
vault workspace.

Before answering vault questions:
1. Read codex.md.
2. Read Football Knowledge Vault/index.md.
3. Search the vault with rg.
4. Do not ask the user to resend local vault content.

When Codex starts inside the vault, this file points it to the detailed schema in codex.md.

Thank you

Build your own.
Stop forgetting.

Tiago Monteiro · Football Data Scientist

Twelve Day Conference · 2026

Twelve
Tiago Monteiro · Twelve 2026
—