Internal tool · Runs every weekday

A wiki that maintains itself.

My team's knowledge base: Markdown files I read in Obsidian, kept current by seven scheduled Claude routines.

Shape
Markdown · git · Obsidian
Keeps it current
7 scheduled Claude routines
Pattern
Karpathy's LLM Wiki
Writes outward
Drafts only — never sends
  • Curated — what is true
  • Meetings — what happened
  • Work — what we produced
  • Raw — what the source said
A bright curated core, evidence at the rim. Watch a meeting arrive and its fact get promoted into the page that owns it. Generated nodes, not real pages.

Note. The vault holds internal material. Nothing from it appears here — structure and mechanics only.

01Why

Ask an assistant anything and it re-reads the same raw sources from scratch, then throws the answer away. Nothing compounds.

So I gave it somewhere to keep what it works out. Synthesise once, at ingest. Questions get answered from a maintained page with a citation.

02Structure

Four zones. Each carries a different level of trust — which is what tells an agent what it may state as true.

  1. Curated

    What is true

    One page per thing. Actively maintained. Every answer comes from here.

  2. Meetings

    What happened

    Dated and distilled — never the raw transcript. History, not current state.

  3. Work

    What we produced

    Dated analyses and dashboards. Append-only; a later one supersedes an earlier one.

  4. Raw

    What the source said

    Verbatim material nobody authored here. Evidence, never current truth.

The one rule

A fact in the bottom three zones is evidence. Its conclusion belongs in a curated page that cites it — so promotion is a step in every routine, not a good intention.

One entity per page

A page covers one thing and links to its neighbours. That is what makes the graph a graph and not a pile.

Provenance · freshness · confidence

Three fields on every curated page. A claim with no source is a bug.

Structure, not live values

Definitions live here. This week's number comes from the system that owns it.

03What runs, and when

Seven routines. Narrow job, fixed time, a written limit on what each may change.

  1. Weekdays · morning

    File yesterday's meetings

    De-duplicates, resolves people by address, routes each meeting to its folder and distils it — then promotes the durable facts into the curated pages that own them.

    Writes meeting pages · the curated pages a fact touches

  2. Weekdays · morning

    Refresh the commitments ledger

    Rebuilds what I owe people and they owe me. Anything ticked by hand stays ticked.

    Writes one ledger page

  3. Monday

    Lint the vault

    Ages any page past its freshness threshold to stale — the one change it may make alone, because it follows from dates. Everything else is reported with a proposed fix, for a human.

    Writes a status field · otherwise reports only

  4. Monday · before kick-off

    Check delivery against the roadmap

    Rates each epic on track / at risk / delayed against live ticket status, and lists what each engineer is on next. Read-only: it never assigns, moves or creates.

    Writes a draft message — never sends

  5. Monday · weekly

    Post the weekly goal update

    Latest complete week per key result, partial weeks dropped. The one routine that publishes on its own — its output is a number with its source attached.

    Writes one recurring update

  6. Every other Monday

    Submit the goal check-ins

    Scores each outcome against its live target with a confidence call. Checks the fortnight first and exits doing nothing on an off week.

    Writes one check-in per outcome

  7. Every other Monday

    Rebuild a recurring dashboard

    Re-runs the queries, republishes to the same address, and messages me only if something moved past a threshold. A quiet run is a successful run.

    Writes one dashboard · alerts only on a real change

04The rules
Back to the work See Tabiya