Frequently Asked Questions
Short, direct answers to what readers ask before they start. Nothing here is aspirational: if something is not built yet, it says so.
What is The Bridge Balance?
A free, three-stage curriculum that takes a student from zero to spec-driven AI-agent engineering. Spec-driven means you write down what you want built and what must not change before any code is generated; the agent implements inside those boundaries, and you verify its work (not only the result, but how it was built and the core of what it built) and take ownership of it.
The textbook is free forever. The business that funds it is a separate, optional catalogue of Claude Code sub-agents, skills, MCP servers, and plugins. Those are paid products. The curriculum itself never charges for content.
Who is it for?
Anyone who has never programmed. The book starts from zero: nothing is skipped, and nothing is left for you to guess.
No experience is needed to begin. A new word is explained the first two or three times you meet it. After that it becomes a link to the glossary, so a reminder is one tap away. A word that is too big for one sentence gets a short passage of its own before it is used.
Is it really free?
Yes. The textbook is free with no paywall, no locked chapter, and no email gate, and that holds across the whole curriculum. It is a standing project principle, not a launch offer.
The only paid surfaces are the optional digital products sold alongside the book — Claude Code sub-agents, skills, MCP servers, and plugins. You can complete every stage without buying any of them.
What are the stages?
- Stage 0 — Introduction to SDE. From zero: how a computer follows instructions, your first tools, your first Python and your first app built by asking an AI, then Spec-Driven Engineering and Code Literacy: reading and judging code, the ideas the rest of the book depends on.
- Stage 1 — SDE Mastery (AI-Driven). Foundations: architecture, programming, frontend, backend, databases, and Git, learned together with Claude Code, prompt and context engineering, skills and MCP servers, so you can lead a coding agent with engineering judgment rather than prompt and hope.
- Stage 2 — SDE Mastery (AI-Native). RAG, tool calling, multi-agent systems, and evaluations — shipping complete agentic systems.
Each stage page explains what it covers and links to its chapters. Stage 0's chapters are being written from scratch, so its text is off the site for now.
How long does it take, and how many chapters are there?
There is no fixed answer, and that is deliberate. The curriculum fixes three stages and commits to nothing below them: the topic, title, and scope of each chapter are decided when it is written, and the book keeps growing. A chapter count or a total-hours figure stated today would be wrong within weeks, so the project never commits to one in advance.
The book is self-paced. The stages lead into one another, and each chapter is one continuous read. A new word is explained when you meet it and later becomes a glossary link, so you can start in the middle and still look any word up in one tap.
How do the video and text fit together?
Every chapter ships twice: a detailed text chapter co-authored by the project owner and Claude Code, and a video lecture the owner records against that finished text. Neither stands alone — the text is the reference you return to, and the video is the walkthrough.
The order is deliberate, and it is the four steps shown on the homepage:
- Co-research. The owner and Claude Code work the topic together, and the spec leads.
- Text writing. Claude Code writes the chapter against that spec, and the owner reviews and edits it.
- Image integration. The owner makes the diagrams, and they are added with descriptive alt text.
- Video recording. The owner records against the now-complete text.
A chapter can go live with its text before its video exists. It says so on the page, and it counts as a finished milestone rather than an unfinished one.
Is there a community? How do I get help if I'm stuck?
There is no Discord, no forum, and no other live community channel today. Saying so plainly is more useful than implying one exists.
An AI help chatbot is planned. It would answer from the book's own chapters rather than from general knowledge, but it is not built. The platform is in its first phase, which today serves the pages themselves and a backend health check; accounts, payments, and anything that needs a signed-in user belong to later phases and are not live.
Until then, the whole book is searchable from the site's search bar, and every chapter is written to stand on its own.
Who maintains this, and how?
The project owner and Claude Code, working in the open. Each chapter is co-authored: the owner and Claude Code research it together, Claude Code writes the text against a spec, and the owner makes the images and records the video. Every stage is written this way.
There is no editorial board and no release schedule. Chapters land when they are ready, and the changelog records what shipped and when.
Can I contribute, or suggest a change?
Not today. The project has a public GitHub copy, but it is a one-time snapshot taken as off-computer insurance, not a working repository that is kept in sync. It is not a route for outside changes, and there is no live process for submitting one yet.
If a way to contribute opens up, the changelog will say so.