Kenjaku — your second brain
Never miss what matters — and never drown in the rest.
🧠 Just ask. Sit down and relax. — your second brain handles the rest.
By Thomas Pierrain (VP Tech at shodo)
Kenjaku is a Karpathy-style LLM wiki, reinforced where it counts with battle-tested software.
Ask it like you'd ask a personal assistant — no dev skills required — and pull up any decision or
piece of info from your work in seconds, always with the sources. In Claude Desktop or on the
command line, your call.
🧠 What's a second brain? · 🚀 Install yours now · 📖 View the articles
🧑 "Where are we on the billing project — who owns what, and what's been decided?"
🧠 "At the January 15 team sync: the database was settled (PostgreSQL over MongoDB),
and Jane Doe — platform Tech Lead — is pushing to get ahead of technical debt as early
as sprint 1.
→ decision of January 10 · → team sync of January 15"
🧑 "What does 'MEDDIC' mean — that thing the sales team keeps repeating in their meetings?"
🧠 "MEDDIC = the opportunity-qualification method adopted by sales: Metrics, Economic
buyer, Decision criteria, Decision process, Identify pain, Champion. Introduced by John Smith (VP
Sales) at the sales kickoff on February 12 to make the forecast more reliable.
→ sales kickoff of February 12 · → sales playbook"
Why you need it
"Wait — you hadn't heard?" · "That was decided last week." · "You didn't see Sarah's email?" ·
"It's in the #product Slack thread…"
We've all been on the receiving end of that — behind, never having had the chance to catch up, to
read it all, to digest it all. The faster the world moves, the more sources you plug into (Slack, mail,
Drive, meeting transcripts, your own notes) and the more the signal drowns in the noise. Staying on top
of it is a second full-time job — unless your memory does it for you.
What it does for you — never forget · never let anyone down · never drown
The whole point, in three everyday aches it takes off your plate. No jargon — the mechanics live in the
small "if you're curious:" strip on each board.
🧠 Never forget — the decision made last quarter, the message you know you saw somewhere: pulled back
in seconds, always with its source. From your own notes; never invented, never off to the web.
✅ Never let anyone down — live with a customer, or juggling ten threads: know at a glance what's on
you and what others owe you, and by when. A spoken "I'll take care of it" lands on the right
to-do list by itself.
🌊 Never drown — back from a week off, or freshly wired into the CRM and call transcripts: instead of
drowning in the flood, ask, and it filters it down to what concerns you, with the source and the
date. Read-only: it reads your sources, never changes them.
Whoever you are — Head of Engineering, PM, Customer Success, sales, consultant, researcher — it
keeps your thread: your teams and 1-1s, the why behind a product decision, a client's whole context.
All-audience by design — that's the whole point. It was conceived so non-tech profiles can use
it: use-case-driven, nothing to manage, and no temporal coupling to track (never a "did it
refresh before I asked?" — freshness, backup and recovery are all handled). If you can chat with
Claude, you can use it. Just ask. Sit down and relax. (Only the one-time install is technical,
and it's guided end-to-end.)
How a question flows — answer now, verify in the background
The web's stale-while-revalidate pattern, applied to your memory: you get a fast answer from
what's already indexed; freshness catches up behind the scenes and only amends the answer if
there's genuinely something new. (details in EN-QUOI §2)
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
