internalREADME.md
erudeon — how we run
- Owner
- Bence
- Updated
- 20 August 2026
- Review
- quarterly
This repository is the business side of erudeon: the handbook, the procedures, the go-to-market plan, and the backlog of everything that is not code.
The code and every technical rule live in erudeon/passtheyear.
Start here
- New to the company? Read
people/handbook/welcome.md, thencompany/charter.md. - Looking for a task? The issues are the to-do list. Everything on the board is there.
- Need to do a thing properly? Look in
operations/sops/. - Something is broken?
operations/runbooks/. - Adding or changing a document? Read
CONTRIBUTING.mdfirst.
What is where
| Directory | What lives there |
|---|---|
company/ |
Who we are, how we decide, the operating rhythm, risks, brand |
go-to-market/ |
Positioning, channels, campaigns, content |
operations/ |
SOPs, runbooks, incidents, vendors, recurring obligations |
people/ |
Handbook, roles, hiring, onboarding |
finance/ |
Spending policy and how contractors are paid. Not the books |
legal/ |
Policies, agreements, the GDPR processing register |
product/ |
The business-side product story. Not technical documentation |
templates/ |
The shape every document type follows |
site/ |
The reader that renders all of the above at ops.erudeon.com |
What is deliberately not here
Personal data of students or customers, the accounts, and technical documentation.
CLAUDE.md explains why for each, and where each belongs instead.
Every area
CompanyWho erudeon is, how it decides, and the rhythm it runs on.company/README.mdFinanceconfidentialPolicy and decisions only.finance/README.mdGo to marketHow the next member arrives, and what we say to them.go-to-market/README.mdLegalconfidentialerudeon is a data controller, so the Article 30 record is a legal obligation rather than good practice. It names each processing activity, its purpose, its lawful basis, the categories of data and people, who it is shared with, and how l…legal/README.mdOperationsHow the company does things, what to do when they break, and what we depend on.operations/README.mdIncidentsAnybody may declare an incident, and declaring one too eagerly is never the mistake. The declarer owns communication until they hand it over explicitly. For a SEV1, say something to affected members before it is fully understood; silence…operations/incidents/README.mdRunbooksA runbook is followed under pressure by somebody who may not have done it before.operations/runbooks/README.mdSOPsA standard operating procedure is a repeatable process involving people.operations/sops/README.mdVendorsconfidentialEverything erudeon pays for or depends on.operations/vendors/README.mdPeoplecircumstances. Pay policy is in finance/contractor-pay.md; an individual's arrangement is not a document in a shared repository.people/README.mdHiringHow we find and assess trainers and writers, and who is on the bench today.people/hiring/README.mdProductThe business-side product story. The technical documentation is in erudeon/passtheyear/docs/, and the backlog is the Project board.product/README.mdSkillsPackaged instructions Claude loads when a particular kind of work comes up. A skill is how a procedure that would otherwise be re-explained every time becomes something the model just knows.skills/README.mdTemplatesCopy one of these rather than inventing a shape. A document whose shape is improvised is one nobody can scan.templates/README.md
Recently changed
Past its review date
Nothing is overdue. Every document is inside the review cadence it declares.