EDB — Start Here
Business and system context I've picked up on the job. The goal is a place to capture the things that aren't written down anywhere — how the domain works, what each application does, and how a request travels end-to-end across systems.
How this section is organised
| Area | Answers | What goes here |
|---|---|---|
| Glossary | "What does that acronym mean?" | One-line definitions of terms and acronyms |
| Systems & Applications | "What is this app and what does it do?" | Per-application notes |
| Domain & Business | "How does the business actually work?" | Grants, schemes, funding — concepts, not code |
| Flows & Processes | "How does a request travel end-to-end?" | Step-by-step walkthroughs across systems |
Filing guide
When you learn something new, drop it in the bucket that matches the question it answers:
- A new acronym or bit of jargon → add a line to the Glossary.
- "Here's what X app is for" → Systems.
- "Here's how grants/schemes/funding work" → Domain.
- "Here's the full path a request takes" → Flows.
Don't over-think placement — the Glossary is the safe default for a quick fact, and notes can always be moved once a pattern emerges.