PassLee Project Bible – Publishing Framework

Framework Version 1.0 – established Sprint 16. This page defines how the Project Bible is structured and written; it does not yet contain the substantive chapters themselves.

Document Purpose

The Project Bible is a single, readable, narrative compilation of PassLee’s project knowledge – written to be read start to finish or dipped into by chapter, rather than browsed record-by-record. It exists alongside the Control Centre’s structured Knowledge Articles, Decisions, Tasks, Technical Notes, and Changes, not instead of them.

Intended Audience

Lee, as a single-document reference to the whole project’s reasoning and current state.
Any future collaborator (human or AI) who needs the full picture quickly, without navigating dozens of individual records.
A future version of the project team, if PassLee ever grows beyond a single-person operation.

Relationship Between the Project Bible and the Control Centre

The Control Centre remains authoritative. The Project Bible is a curated, narrative derivative of it – each chapter is compiled from specific Knowledge Articles, Decisions, and Technical Notes, which remain the source of truth. If the Bible and the Control Centre ever disagree, the Control Centre is correct and the Bible chapter should be updated to match, not the reverse. The Bible is read-friendly; the Control Centre is edit-friendly and queryable. Neither replaces the other.

Versioning Approach

The Bible as a whole carries one version number (this framework is v1.0).
A structural change (adding/removing/reordering Parts or Chapters) increments the minor version (1.0 -> 1.1).
A full content rewrite of the Bible increments the major version (1.x -> 2.0).
Individual chapters are not separately versioned – they inherit the Bible’s version, but each chapter should note which source articles’ article_version and article_last_reviewed it was compiled from, so staleness can be detected later.
See Change History at the end of this page for the running log.

Document Conventions

Structure: Part (Roman numeral) > Chapter (numbered within its Part).
Each chapter opens with a one-line summary of what it covers.
Each chapter ends with a “Sources” list linking to the Knowledge Article(s), Decision(s), and Technical Note(s) it was compiled from.
Chapters describe conclusions and reasoning in prose; they do not simply repeat bullet lists verbatim from source articles – the Bible’s value is narrative synthesis, not duplication.
Where a chapter’s topic is still evolving (e.g. an ongoing recurring Task), the chapter says so explicitly rather than presenting it as settled.

Cross-Reference Strategy

The Project Bible is a WordPress Page, not a Knowledge Article, so it cannot participate in the Control Centre’s post-relationship system (the same limitation noted throughout the migration for Pages generally). Cross-references therefore work as:

Plain hyperlinks from each chapter to its source Knowledge Articles, Decisions, and Technical Notes.
A consistent “Sources” list per chapter (see Document Conventions) rather than scattered inline links only.
Chapters may link to each other within the Bible using normal in-page anchors once written.

Table of Contents / Major Parts and Chapters

Chapters are listed with their intended primary source(s). None are written yet.

Part I – Introduction (Written – Sprint 17)

1. What PassLee Is and Why This Bible Exists

Part II – Business Foundation (Written – Sprint 18)

2. Business Identity & Positioning (source: Business Identity & Positioning)
3. Target Audience (source: Target Audience Evolution)

Part III – Website & SEO Strategy

4. SEO Strategy & Its Evolution (source: PassLee SEO Strategy)
5. Homepage: History, Maturity, and Principles (source: Homepage Evolution, Homepage Blueprint)
6. Search Console as a Decision Tool (source: Search Console Strategy, SEO Investigation Methodology)
7. Common Misconceptions Corrected (source: Common SEO Misconceptions Corrected)

Part IV – Content & Reputation

8. Pass Stories & Authentic Content (source: Pass Stories Strategy)
9. Google Reviews & Reputation (source: Google Reviews Guidance, Review Strategy Evolution)
10. Google Business Profile (source: Google Business Profile Strategy)
11. Trust as an Ecosystem (source: Trust Signals section, PassLee SEO Strategy)

Part V – Security & Technical History

12. The Security Incident (source: Security Incident – Website Compromise, Website Recovery Timeline)
13. Security Hardening as Standing Practice (source: Security Hardening Strategy)
14. passlee.com Technical History (source: passlee.com Technical & SEO History)

Part VI – The Control Centre

15. Why the Control Centre Exists (source: Mission Control & Control Centre Development, Why the Knowledge Site Exists)
16. System Architecture (source: System Architecture)
17. AI Collaboration & Governance (source: AI Collaboration Workflow, Project Governance, Conversation Migration Process)
18. Operational Workflow & Continuity (source: Operational Workflow, Project Continuity Strategy)

Part VII – Appendices

A. Known Historical Gaps (source: Known Historical Gaps)
B. Migration Completion Report (source: Migration Completion Report)
C. Decision Register (index of all Decisions, generated from the Decisions archive)
D. Glossary of terms

Part I – Introduction

Chapter 1 – Executive Summary

PassLee is a driving instruction business operating in Worcester and the surrounding towns of Pershore and Droitwich, specialising in automatic driving lessons. Alongside the business itself, the project encompasses its public website (passlee.com), its search and reputation presence, and – since mid-2026 – a dedicated internal system, the PassLee Control Centre, built to hold the project’s accumulated knowledge, decisions, and working practices in one permanent place.

The purpose of the project, at its core, is straightforward: grow PassLee’s business through a website and online presence that genuinely reflects what the business does well, supported by a way of working that doesn’t lose important knowledge to time or to the limits of any single conversation. The Control Centre exists to serve that growth – it is infrastructure in support of the business, not an end in itself.

As of this writing, the project is mature on both fronts. The SEO and content strategy has moved through a full cycle of learning – from an initial focus on homepage content and keyword coverage, through a data-led reassessment using Google Search Console, to a settled strategy built on authority, trust, and authentic experience rather than continued homepage expansion. The Control Centre itself is architecturally complete: nine build phases established its structure, live dashboard, and design, and a subsequent, deliberate effort migrated the project’s accumulated historical knowledge into it, verified complete after fifteen sprints.

This Project Bible exists because the Control Centre’s structured records – articles, decisions, tasks, technical notes – are excellent for reference and cross-linking, but not naturally suited to being read as a single, coherent story. The Bible is that story: a narrative account of what PassLee is, how its strategy came to be what it is, and where the project stands, compiled from and cross-referenced back to the structured knowledge that remains the project’s authoritative source.

Sources

Chapter 2 – Business Overview

PassLee’s core service is automatic driving lessons, delivered across Worcester and the surrounding areas of Pershore and Droitwich. The business has deliberately moved away from generic “driving school” positioning towards a more distinctive identity built around calm, patient, supportive instruction – a characteristic the project treats as a genuine differentiator rather than incidental marketing language.

The project’s understanding of its ideal audience has sharpened over time to focus on: nervous learners, mature learners, automatic-only learners, learners specifically seeking a calm teaching style, and local Worcester residents. These audiences were not chosen arbitrarily – each aligns directly with what PassLee already does well, so messaging aimed at them reinforces the business’s actual strengths rather than diluting them with broad, generic appeal.

PassLee’s core business objective is to compete primarily through teaching quality, local expertise, trust, authentic learner experience, and consistency – deliberately not through price competition alone. This is treated as a considered strategic choice, not just an incidental preference.

Sources

Chapter 3 – Project Scope

The PassLee project, as understood by the Control Centre, includes: the business’s public-facing website (passlee.com) and its content; the business’s search presence, including SEO strategy and Google Search Console monitoring; its Google Business Profile and review activity; and the Control Centre itself as the system recording and supporting all of the above. A second site, automaticdrivinglessonsworcester.co.uk, also sits within the broader PassLee web portfolio, though it has received comparatively little dedicated attention in the project’s history to date.

Outside the project’s scope, as currently documented: the operational mechanics of delivering driving lessons themselves (scheduling, vehicle logistics, instructor certification) are not part of the Control Centre’s subject matter – the project is concerned with the business’s presence and reputation, not its day-to-day service delivery.

The relationship between these pieces is deliberately hierarchical: the business is the point; the websites and SEO work serve the business; the Control Centre serves the websites and SEO work by preserving the reasoning and decisions behind them. The Control Centre exists to support the growth of passlee.com – not the reverse.

Sources

Chapter 4 – Current Status

Websites: passlee.com is live in production, having previously moved through a staging environment; a mobile display defect (a black header background caused by the hero image’s desktop-only behaviour) and a caching configuration bug were identified and fixed during this history.

SEO direction: the project’s current strategy prioritises authority-building – Google Business Profile growth, reviews, Pass Stories, local and Worcester-specific content, and internal linking – over further homepage rewriting, which is now considered to have reached diminishing returns. Decisions are increasingly evidence-led, using Search Console data before making strategic changes rather than reacting to short-term ranking movement.

Documentation maturity: historical knowledge migration is formally complete as of Sprint 15, covering business identity, SEO strategy, content and reputation strategy, homepage history, security history, and the Control Centre’s own development, with known and explicitly documented gaps rather than silent ones.

Control Centre maturity: architecturally complete through nine build phases (custom content types, metadata, relationships, editor integrity, a live dashboard, and a full visual redesign into a “Control Centre” application), with a working, verified relationship system and zero known broken relationships as of the most recent check.

Project Bible status: its publishing framework was established in Sprint 16; this Part I – Introduction is the first substantive content written under that framework.

Sources

Chapter 5 – Vision & Objectives

The project’s long-term vision is for the Control Centre to function as the permanent memory of the PassLee project – a place where every meaningful design decision, SEO strategy, homepage evolution, and technical lesson eventually exists in structured, cross-linked form, in service of growing passlee.com, which remains the primary mission throughout.

Strategic objectives currently in motion include executing the authority-building content roadmap (ongoing Pass Stories, Google Reviews, Worcester-specific and local-authority content), keeping the homepage to incremental, trust-focused improvements rather than repeated redesigns, and continuing to treat Search Console evidence as the basis for SEO decisions rather than instinct or short-term ranking noise.

The principles guiding future development are: preserve before improving; expand existing knowledge before creating new records; avoid duplication; prefer evidence over assumptions; solve root causes rather than symptoms; and keep the Knowledge Site coherent rather than merely comprehensive. Every work session is expected to leave the project a little stronger than it found it, whether through new work, a recorded decision, or preserved knowledge.

Sources

Chapter 6 – Success Measures

Business outcomes are expected to follow from differentiation through experience rather than price – success looks like a growing base of pupils drawn by trust and reputation, not discounting. SEO outcomes are judged over long-term trends rather than isolated snapshots, with a single ranking movement never treated as a trigger for major changes; the working assumption is that authority-building activity, sustained over time, is what moves rankings meaningfully.

Documentation quality is judged against the project’s own Knowledge Quality Principles – clear scope, minimal duplication, appropriate granularity, strong cross-linking, historical accuracy, and explicit rationale where applicable. Knowledge management success means the Control Centre continuing to function as the single authoritative source, with no significant project knowledge left to exist only inside a conversation.

AI collaboration is judged by whether the ChatGPT/Claude division of labour – strategic planning and continuity with ChatGPT, repository implementation and structured migration with Claude – continues to hold up in practice, including sound judgement calls that reduce duplication while preserving meaning, rather than rigid, literal execution of instructions at the expense of a coherent Knowledge Site.

Sources

Part II – Business Foundation

Note on structure: the approved Sprint 16 framework defines two chapters for this Part. To cover everything Sprint 18 requires (identity, services, geography, audience, brand values, and customer journey) without renumbering the chapters that follow in Part III onward, both chapters below are organised with clear subheadings rather than being split into additional numbered chapters.

Chapter 2 – Business Identity, Values & Audience

Identity

PassLee’s positioning did not arrive fully formed. It developed from an initial, fairly generic “driving school” presentation into a more distinctive identity built around calm, patient, supportive instruction – a quality the project treats as central to who PassLee is, not as an incidental tone of voice. This shift was deliberate: generic messaging competes on the same terms as every other local driving school, whereas a distinctive, consistently-held identity gives PassLee something a competitor cannot simply copy by rewriting their own homepage.

Brand Principles & Values

PassLee’s agreed core differentiators are: automatic specialism, local knowledge, patient instruction, real learner success, and an authentic reputation built over time rather than manufactured. These are held together by a single consistency principle: the website, Google Business Profile, reviews, Pass Stories, and general branding are all expected to reinforce the same identity and the same customer expectations. Where these channels drift out of alignment with one another, the trust the business otherwise relies on is undermined – so consistency across channels is treated as a value in its own right, not just good housekeeping.

Target Audience

The project’s understanding of its ideal customer sharpened over time toward five overlapping groups: nervous learners, mature learners, automatic-only learners, learners specifically seeking a calm teaching style, and local Worcester residents. None of these were chosen for their size as a market segment; each was chosen because it aligns directly with what PassLee’s identity already promises. Messaging aimed at a nervous or mature learner, for instance, plays directly to patient, calm instruction in a way that generic messaging aimed at “anyone learning to drive” cannot.

Competing on Experience, Not Price

PassLee’s agreed competitive stance is to compete primarily through teaching quality, local expertise, trust, authentic learner experience, and consistency – rather than price. This is the audience-facing counterpart to the project’s SEO strategy: both rest on the same underlying belief, that authentic, hard-to-replicate experience is a stronger long-term asset than either price competition or generic content ever could be.

Sources

Chapter 3 – Services, Geography & Customer Journey

Services Offered

The Control Centre documents one core service: automatic driving lessons. No broader service catalogue – for example, intensive courses, Pass Plus, motorway tuition, or refresher lessons – is currently recorded anywhere in the Knowledge Site. This chapter therefore describes automatic driving lessons as the documented core service, without implying a wider range that has not actually been recorded.

Geographic Operating Area

PassLee operates in Worcester and the surrounding towns of Pershore and Droitwich. A second website, automaticdrivinglessonsworcester.co.uk, also sits within the broader PassLee web portfolio, though the Control Centre’s history shows comparatively little dedicated strategic attention to it so far compared to passlee.com.

Customer Journey – Known Gap

This is a genuine, documented gap rather than an omission being quietly filled. The Control Centre records PassLee’s positioning, audience, and competitive strategy in detail, but does not currently document the actual customer journey – what happens from initial enquiry, through booking and lesson delivery, to post-test engagement (for example, whether and how Pass Story collection or review requests are timed relative to a pupil’s test date). Rather than invent a plausible-sounding journey to complete this chapter, the gap is recorded here explicitly, consistent with how Known Historical Gaps was handled at the end of the historical migration. A Task has been created to close this gap with real information rather than assumption – see Sources below.

Sources

Business Identity & Positioning
Target Audience Evolution
Customer Journey: no source currently exists – see the “Document the PassLee customer journey” Task.

Change History

Date	Version	Change
2026-07-21	1.0	Framework established (Sprint 16): purpose, audience, versioning, conventions, cross-reference strategy, and full Table of Contents defined. No chapters written yet.
2026-07-21	1.1	Part I – Introduction (Chapters 1-6: Executive Summary, Business Overview, Project Scope, Current Status, Vision & Objectives, Success Measures) written in full, per Sprint 17. Synthesised from existing Knowledge Articles and Decisions; no new strategic decisions introduced.
2026-07-21	1.2	Part II – Business Foundation (Chapters 2-3: Business Identity/Values/Audience, Services/Geography/Customer Journey) written, per Sprint 18. One genuine gap discovered and documented (Customer Journey) rather than fabricated; a Task was created to close it with real information.