P0_Source_Library

Complete Source Book Library for the 8-Phase Software Project Execution System

Purpose
This document assigns 10 high-quality books to each phase of the software project execution system. It is designed as a professional source library for ChatGPT, Codex, developers, UX teams, QA, security
reviewers, deployment engineers, maintainers, and project managers. It is not a casual reading list.

Operating Rule
 Before executing any phase task, read the current phase PDF, previous phase handoffs, all project source files, attached documentation, relevant source books, user-specific constraints, and Codex reports if code is
involved.
 Books support execution decisions; they do not override confirmed project requirements, user constraints, security rules, or source files.
 If a book edition/year is uncertain, this library marks it as edition not verified.
 For simple projects, read the minimum set. For complex, existing, AI, security-sensitive, or production systems, expand to the advanced set.

Verification Note
Major title/author/edition details were checked against publisher, Google Books, O'Reilly, Wiley, Manning, and Google SRE pages where available. Some older or variable editions are intentionally marked as
edition not verified.

Phase 1 - P1_Discovery - Analysis, Product Discovery, Project Mode Detection, AI Discovery, Codex Readiness
Phase Mission
Turn an unclear request into a confirmed or explicitly assumed project definition: mode, goal, users, scope, business rules, data needs, AI status, risks, and Codex readiness.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 INSPIRED: How to Create Marty Cagan 2nd ed., 2017 Core Strong product discovery Product goal, stakeholder Product principles, Use to challenge vague Use when interviewing Less detailed on formal
Tech Products Customers source for defining valuable needs, MVP, product team discovery, product feature requests and ask stakeholders and defining requirements specs and
Love products before planning responsibilities. manager/product team, value/risk questions. product outcomes. databases.
architecture. validation.
2 Continuous Discovery Teresa Torres 2021 Core Gives repeatable discovery Stakeholder/user Continuous interviewing, Use to generate adaptive Use to run weekly Not a full requirements or
Habits habits and interview-driven interviews, assumptions, opportunity solution trees, discovery questions and discovery and validate architecture book.
opportunity mapping. opportunity-solution assumptions, experiments. assumption tests. needs before building.
thinking.
3 Software Requirements Karl Wiegers, Joy Beatty 3rd ed., 2013 Core Best practical source for Requirements intake, Elicitation, business rules, Use to structure questions Use to write requirements, Less focused on modern
requirements elicitation and business rules, scope, quality attributes, and separate requirements acceptance criteria, and AI/product discovery
quality requirements. acceptance criteria. prioritization, validation. from solutions. change requests. workflows.
4 Requirements Engineering: Axel van Lamsweerde 2009 Advanced Rigorous treatment of Complex stakeholder goals, Goals, obstacles, agents, Use for high-risk projects Use in enterprise/safety- Heavy and academic for
From System Goals to UML goals, constraints, agents, constraints, conflict operations, specification where requirements must critical discovery small MVPs.
Models to Software and formal requirements. analysis, system quality. be precise. workshops.
Specifications boundaries.
5 User Story Mapping Jeff Patton, Peter Economy 2014 Core Transforms user goals into MVP/change scope, user Backbone, walking Use to split broad requests Use in workshops to agree Less detailed on
flows, releases, and scope journeys, first milestone, skeleton, release slicing, into phased scope and core on MVP and later features. backend/data/security.
boundaries. release slicing. discovery through stories. flows.
6 Escaping the Build Trap Melissa Perri 2018 Important Prevents teams from Problem definition, outcome Product strategy, outcome Use to ask why a feature Use to keep discovery Not an implementation
treating feature output as framing, product strategy, metrics, experimentation, matters and define success outcome-driven, not ticket- guide.
P0_Source_Library - Operational Source Book Library
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
product success. feature prioritization. value delivery. criteria. driven.
7 Lean UX Jeff Gothelf, Josh Seiden 3rd ed., 2021 Important Practical for assumptions, Hypotheses, MVP scope, Assumptions, hypotheses, Use to convert uncertainty Use in Less rigorous for formal
hypotheses, MVPs, and experiments, UX MVPs, collaborative into experiments and product/design/developmen requirements and
cross-functional discovery. collaboration. discovery, outcomes. assumptions log. t discovery meetings. enterprise governance.
8 The Mom Test Rob Fitzpatrick 2013 Important Useful for interviews that User interviews, discovery Bad questions, Use to rewrite user Use before interviewing Narrow scope: interviews
avoid biased validation questions, problem commitment, segmentation, questions so they do not clients/users. only.
questions. validation. learning from users. lead the answer.
9 Building Machine Learning Emmanuel Ameisen 2020 Important Bridges AI idea discovery AI feasibility, input/output, ML problem framing, Use to decide whether AI is Use by AI engineer/product Not a deep ML theory
Powered Applications with real ML product dataset/model readiness, dataset, baseline, real, mock, deferred, or owner before promising AI textbook.
feasibility. evaluation and deployment evaluation, deployment, risky. features.
risks. monitoring.
10 Project Management: A Harold Kerzner edition not verified Advanced Gives disciplined project Project constraints, Project initiation, scope, Use for large projects Use by PM/project owner Heavy for small teams and
Systems Approach to framing, constraints, stakeholders, deliverables, risk, planning, control, requiring governance and for planning discipline. not software-specific
Planning, Scheduling, and scheduling, risk, and risk planning, coordination. stakeholders. multi-team coordination. enough.
Controlling governance.

Minimum Reading Before Executing This Phase

- INSPIRED: Defines product value and discovery discipline.

- Software Requirements: Gives precise requirements and business rule capture.

- User Story Mapping: Turns goals into flows and release scope.

Advanced Reading for Difficult Projects

 Requirements Engineering for enterprise/safety-critical specs
 Building Machine Learning Powered Applications for AI projects
 Kerzner for large-team governance and project control

Phase Source Reading Protocol

 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Classify project mode accurately
 Ask adaptive intake questions
 Define goal, users, MVP/change scope, business rules and data needs
 Detect AI feasibility and Codex readiness
 Produce a Phase 2 handoff with risks and assumptions

P0_Source_Library - Operational Source Book Library

Phase 2 - P2_Planning - UX Planning, Database Planning, Backend Planning, AI Planning, Existing Project Impact Analysis
Phase Mission
Convert Phase 1 discovery into user flows, information architecture, data entities, relationships, backend modules, permissions, AI planning, and impact analysis.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Information Architecture: Louis Rosenfeld, Peter 4th ed., 2015 Core Core reference for Sitemap, IA, navigation, Organization systems, Use to structure product Use by UX/product teams Not database/backend
For the Web and Beyond Morville, Jorge Arango organizing screens, module grouping, content labeling, navigation, search, modules and screen to design navigation and focused.
modules, navigation, and hierarchy. IA process. inventory. content grouping.
content.
2 About Face: The Essentials Alan Cooper, Robert 4th ed., 2014 Core Deep UX planning source UX flows, personas, task Goal-directed design, Use to create role-based Use by UX designers for Less focused on
of Interaction Design Reimann, David Cronin, for goals, behavior, modeling, interaction personas, scenarios, flows and interaction workflow and behavior API/database architecture.
Christopher Noessel personas, interaction planning. interaction framework. assumptions. design.
models.
3 Designing Data-Intensive Martin Kleppmann, Chris 2nd ed., 2026 Core Best systems-level source Data modeling, storage Data models, Use to check Use by backend/data May be too advanced for
Applications Riccomini for data architecture trade- trade-offs, consistency, storage/retrieval, database/system trade-offs architects for technical simple CRUD MVPs.
offs and reliability. scalability, reliability. replication, transactions, before architecture planning.
distributed data. decisions.
4 Database Design for Mere Michael J. Hernandez edition not verified Core Practical relational Entity discovery, fields, Entities, attributes, Use to convert data needs Use by database planner Less useful for
Mortals modeling and normalization relationships, constraints, relationships, business into entity/relationship before schema NoSQL/distributed
source. ERD planning. rules, normalization. questions. implementation. architecture.
5 Domain-Driven Design Eric Evans 2003 Advanced Foundational book for Domain language, bounded Ubiquitous language, Use to model complex Use by architects/backend Dense; not a quick beginner
domain modeling and contexts, aggregates, entities, value objects, domains and detect leads with domain experts. book.
complex business logic. business rules. services, repositories. boundaries.
6 Implementing Domain- Vaughn Vernon 2013 Advanced Practical DDD Backend modules, Bounded contexts, Use to plan backend Use when translating DDD Can be heavy for small
Driven Design implementation and aggregates, services, aggregates, domain events, service boundaries and ideas into implementable projects.
bounded-context planning. integration boundaries. repositories, application module responsibility. architecture.
services.
7 Fundamentals of Software Mark Richards, Neal Ford 2020 Core Practical map of Backend architecture, Architecture characteristics, Use to select architecture Use by architects and Does not deeply cover UX
Architecture architecture styles, trade- module boundaries, quality components, styles, trade- depth and quality attributes. backend leads for planning or database normalization.
offs, qualities, and attributes, decision records. offs. trade-offs.
decisions.
8 Software Architecture: The Neal Ford, Mark Richards, 2021 Advanced Helps plan difficult trade- Service boundaries, data Coupling, service Use when Phase 2 faces Use by senior engineers for Too advanced for small
Hard Parts Pramod Sadalage, Zhamak offs in distributed and ownership, distributed granularity, transactions, hard architecture enterprise/large-system CRUD systems.
Dehghani evolutionary systems. workflows, trade-off distributed data, evolution. decomposition decisions. planning.
analysis.
9 Designing Machine Chip Huyen 2022 Important Practical ML system AI data/model/inference Data distribution, features, Use to define AI track Use by AI/backend teams Not a UX or requirements
Learning Systems planning: data, evaluation, planning, evaluation, evaluation, model requirements and failure when AI is in scope. book.
deployment, monitoring. production constraints. deployment, monitoring. modes.
10 Working Effectively with Michael C. Feathers 2004 Core for existing Essential for existing project Existing code audit, seams, Seams, characterization Use to require inspection Use by developers when Code-focused; not product
Legacy Code impact analysis and safe characterization tests, tests, dependencies, legacy and regression planning modifying inherited discovery or UX.
change strategy. change impact. change patterns. before changing old code. systems.

Minimum Reading Before Executing This Phase

- Information Architecture: Needed to organize the product structure.

- Database Design for Mere Mortals: Needed to model entities and relationships.

- Fundamentals of Software Architecture: Needed to plan backend modules and architecture trade-offs.

Advanced Reading for Difficult Projects

 DDIA and Software Architecture: The Hard Parts for enterprise scale
 Designing Machine Learning Systems for AI planning
 Working Effectively with Legacy Code for existing systems
P0_Source_Library - Operational Source Book Library
Phase Source Reading Protocol
 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Create UX flows, sitemap, and screen inventory
 Draft data dictionary, ERD notes, and migration risk
 Plan backend modules, permissions, workflows and API needs
 Plan AI data/model/inference/review path
 Produce Phase 3 UI/API handoff

P0_Source_Library - Operational Source Book Library

Phase 3 - P3_UI_API - UI Design, Screen Contracts, Component Planning, API Design, Error Contracts, AI UI/API Contracts
Phase Mission
Turn planning into implementation-ready screen contracts, component inventories, form rules, API contracts, error/permission rules, AI result interfaces, and Phase 4 Codex prompts.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Designing Interfaces: Jenifer Tidwell, Charles 3rd ed., 2020 Core UI pattern reference for Screen contracts, Patterns, navigation, input, Use to choose robust UI Use by UI/frontend team Does not design backend
Patterns for Effective Brewer, Aynne Valencia screens, components, component planning, social, mobile, visual patterns and state behavior. when defining components. API contracts.
Interaction Design states and interactions. navigation, interaction hierarchy.
states.
2 About Face: The Essentials Alan Cooper et al. 4th ed., 2014 Core Provides goal-directed Screen purpose, flows, Interaction framework, Use to check if screen Use by UX designers to Not API-specific.
of Interaction Design interaction design for behavior, persona-driven posture, behavior, behavior supports user refine complex workflows.
screen behavior. interaction. navigation, controls. goals.
3 Design Systems Alla Kholmatova 2017 Important Practical reference for Component inventory, UI Pattern libraries, design Use to define components, Use by UI/frontend teams Shorter and less API/form
building reusable consistency, pattern language, maintenance, variants and reuse rules. to avoid one-off screens. deep.
components and design governance. governance.
systems.
4 Form Design Patterns Adam Silver 2018 Core Excellent guide for usable Forms, validation, errors, Input types, validation, Use to define form specs Use by UI/frontend Mostly form-focused.
forms, errors, validation and inputs, user feedback. checkout, registration, and validation UX. developers for form
interaction. accessibility. implementation.
5 Web Form Design Luke Wroblewski 2008 Important Classic practical reference Form layout, labels, field Labels, input fields, help Use to improve form clarity Use by designers for data- Older examples; less
for web forms and grouping, submission flow. text, errors, actions. and reduce user mistakes. entry screens. modern component-system
conversion-oriented layout. focus.
6 Accessibility for Everyone Laura Kalbag 2017 Core Practical accessibility guide Accessibility checklist, Accessibility principles, Use to add accessibility Use by designers/devs/QA Not a complete WCAG
for inclusive UI keyboard/focus, labels, content, design, requirements to every to check basic accessibility. legal manual.
requirements. readable UI. development, testing. screen contract.
7 Designing Web APIs: Brenda Jin, Saurabh Sahni, 2018 Core Practical API design and API needs, endpoint API design process, Use to turn screen needs Use by backend/API Less formal than deeper
Building APIs That Amir Shevat developer-experience thinking, API usability, resources, docs, into APIs developers can designers before REST/distributed system
Developers Love source. production operation. versioning, developer consume. implementation. texts.
experience.
8 Principles of Web API James Higginbotham 2021 Core Strong structured API API contracts, value API program lifecycle, Use to create API contract Use by API leads for Not a UI design source.
Design lifecycle and contract delivery, resources, errors, design-first, resources, tables and consistency scalable API design.
design reference. consistency. governance. rules.
9 RESTful Web APIs Leonard Richardson, Mike 2013 Advanced Deep REST/hypermedia REST principles, resources, HTTP, resources, Use when API design Use by backend/API Can be overkill for simple
Amundsen, Sam Ruby perspective for robust API representations, links, representations, needs rigorous REST architects for advanced API CRUD APIs.
semantics. HTTP semantics. hypermedia, profiles. reasoning. design.
10 Human-Centered AI Ben Shneiderman 2022 Important Useful for AI result UI, AI result interfaces, human Human control, reliable Use to keep AI UI advisory, Use by product/AI/UI teams Not an implementation or
review, confidence, and review, trust, user control. systems, governance, reviewable, and safe. for AI interaction design. ML modeling book.
human control. trustworthy AI.

Minimum Reading Before Executing This Phase

- Designing Interfaces: Needed for reusable screen and interaction patterns.

- Form Design Patterns: Needed for accurate form and validation design.

- Principles of Web API Design: Needed for implementation-ready API contracts.

Advanced Reading for Difficult Projects

 RESTful Web APIs for advanced APIs
 Human-Centered AI for AI UI/safety
 Design Systems for large teams and reusable components

P0_Source_Library - Operational Source Book Library

Phase Source Reading Protocol
 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Create screen contracts and UI state matrices
 Plan reusable components and forms
 Write API contracts with requests, responses, errors and permissions
 Design AI result UI/API contracts
 Prepare precise Phase 4 Codex prompts

P0_Source_Library - Operational Source Book Library

Phase 4 - P4_Coding - Frontend Development, Backend Development, Database Migrations, AI Integration, Codex
Implementation
Phase Mission
Turn Phase 3 contracts into working software using safe vertical slices, codebase inspection, backend/frontend/API/database/AI implementation, tests, reports, and fix loops.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Code Complete Steve McConnell 2nd ed., 2004 Core Broad practical guide to Implementation discipline, Design in construction, Use to judge coding tasks Use by developers for Older examples; not
software construction construction practices, error defensive programming, and implementation quality. construction practices. specific to modern web
quality. handling, code quality. routines, debugging, stacks.
quality.
2 Clean Code Robert C. Martin 2008 Core Common baseline for Function design, naming, Meaningful names, Use to instruct Codex to Use by developers during Some advice is debated;
readable, maintainable small modules, clean functions, comments, error produce readable focused code review and not architecture-complete.
code. implementation. handling, tests. changes. refactoring.
3 Refactoring: Improving the Martin Fowler 2nd ed., 2018 Core Essential for safe Refactoring, code cleanup, Refactoring principles, code Use to avoid rewrites and Use by developers when Requires tests for best use.
Design of Existing Code incremental improvement of preserving behavior, small smells, catalog, tests. propose small behavior- improving code safely.
existing code. safe edits. preserving changes.
4 Clean Architecture Robert C. Martin 2017 Important Useful for structuring Architecture boundaries, SOLID, components, use Use to check whether Use by backend/frontend Can be abstract and
backend/frontend use cases, entities, cases, boundaries, implementation respects leads for structure. opinionated.
boundaries and dependency direction. policy/detail split. boundaries.
dependencies.
5 The Pragmatic Programmer David Thomas, Andrew 20th Anniversary ed., 2019 Core Practical engineering habits Implementation habits, Pragmatic approach, DRY, Use to formulate safe, Use by whole team as Not deep on modern
Hunt for coding, debugging, debugging, automation, tracer bullets, debugging, practical developer/Codex engineering culture architecture or AI.
automation, and ownership. defensive development. automation. tasks. baseline.
6 Working Effectively with Michael C. Feathers 2004 Core for existing Key source for changing old Codebase inspection, Seams, sprout/wrap Use to require inspect- Use by developers working Older language examples
Legacy Code code safely with tests and legacy changes, methods, dependencies, before-edit and regression- on inherited systems. but durable principles.
seams. characterization tests, characterization tests. oriented changes.
seams.
7 Patterns of Enterprise Martin Fowler 2002 Advanced Classic enterprise patterns Backend patterns, Domain logic patterns, data Use to reason about Use by backend architects Old examples; not cloud-
Application Architecture for data access, services, transaction scripts, source patterns, distribution existing enterprise for complex business apps. native.
transactions and layering. repositories, data mappers, patterns. architecture.
service layer.
8 Designing Data-Intensive Martin Kleppmann, Chris 2nd ed., 2026 Advanced Guides implementation Data handling, transactions, Transactions, consistency, Use when coding data- Use by backend/data Overkill for simple screens.
Applications Riccomini decisions around data replication, event streams, storage, streams, heavy or scalable features. engineers for complex data
correctness and scalability. reliability. distributed systems. changes.
9 Pro Git Scott Chacon, Ben Straub 2nd ed., 2014 Core Version control baseline for Git workflow, branching, Basics, branching, Use to define safe Use by developers to Not a software design book.
branches, history, safe merging, inspection, distributed workflows, tools, branch/change rules for manage code changes
collaboration. collaboration. internals. Codex. safely.
10 Building Machine Learning Emmanuel Ameisen 2020 Important for AI Practical guide to AI adapter/service, result ML pipeline, evaluation, Use to scope AI coding Use by AI/backend Not framework-specific and
Powered Applications integrating ML features storage, evaluation, deployment, monitoring. tasks and limitations. engineers implementing ML not deep ML theory.
from idea to product. deployment considerations. features.

Minimum Reading Before Executing This Phase

- Code Complete: Construction discipline for any serious implementation.

- Refactoring: Safe change method, especially with existing code.

- Working Effectively with Legacy Code: Mandatory when Codex touches old code.

Advanced Reading for Difficult Projects

 DDIA for data-intensive systems
 Patterns of Enterprise Application Architecture for enterprise backends
P0_Source_Library - Operational Source Book Library
 Building ML-Powered Applications for AI integration

Phase Source Reading Protocol

 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Plan vertical implementation slices
 Create Codex inspect/implement/fix prompts
 Implement backend, frontend, database migrations and AI adapters safely
 Preserve existing behavior
 Produce structured implementation reports

P0_Source_Library - Operational Source Book Library

Phase 5 - P5_Testing_QA - Testing, QA, Regression, API Testing, UI Testing, AI Evaluation, Bug Triage
Phase Mission
Turn implementation output into traceable tests, manual/API/UI/backend/database/regression/AI checks, bug triage, Codex fix prompts, and a release candidate handoff.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Lessons Learned in Cem Kaner, James Bach, 2001 Core Context-driven testing QA strategy, exploratory Test strategy, bug Use to create risk-based Use by QA leads/testers to Older tooling context.
Software Testing Bret Pettichord source with practical testing testing, bug thinking, test advocacy, test test plans, not shallow design practical test
heuristics. design. management, exploratory checklists. coverage.
approaches.
2 Agile Testing Lisa Crispin, Janet Gregory 2008 Core Defines tester role and QA QA process, acceptance Agile testing quadrants, Use to align QA with Use by QA and developers Less modern on AI testing.
collaboration in agile teams. tests, team collaboration, collaboration, automation, requirements and for team testing workflow.
automation balance. user stories. development handoffs.
3 More Agile Testing Janet Gregory, Lisa Crispin 2014 Important Extends agile testing with Regression, test strategy, Scaling testing, test Use for complex or multi- Use by QA managers/leads Not API-specific.
scaling, automation and large teams, automation automation, technical debt, team QA planning. in larger projects.
modern QA practices. maturity. continuous testing.
4 Explore It! Elisabeth Hendrickson 2013 Core Excellent exploratory Manual exploratory testing, Charters, tours, heuristics, Use to create exploratory Use by testers when formal Does not cover automation
testing guide for finding charters, sessions, edge session notes, learning test charters from risk test cases are insufficient. deeply.
unknown issues. cases. loops. areas.
5 xUnit Test Patterns Gerard Meszaros 2007 Advanced Deep reference for Backend tests, unit tests, Test smells, fixtures, Use when asking Codex to Use by developers/test Large and detailed; not
automated test structure fixtures, test smells, assertions, test doubles, add/repair automated tests. automation engineers. manual QA focused.
and maintainability. regression tests. xUnit patterns.
6 Test Driven Development: Kent Beck 2002 Important Foundational TDD workflow Developer tests, red-green- TDD cycle, simple design, Use to require small Use by developers Not a full QA strategy book.
By Example for small safe increments. refactor, regression-safe xUnit example, patterns. code/test loops from implementing test-first fixes.
fixes. Codex.
7 Growing Object-Oriented Steve Freeman, Nat Pryce 2009 Advanced Strong source for end-to- Integration tests, Walking skeleton, Use to plan tests across Use by developers on OO-centric; not all stacks fit
Software, Guided by Tests end and interaction-focused acceptance tests, test acceptance tests, test UI/API/backend slices. complex integrated directly.
test design. doubles, object doubles, ports/adapters. systems.
collaboration.
8 The Art of Software Testing Glenford J. Myers, Corey edition not verified Important Classic systematic testing Test case design, boundary Psychology of testing, test Use to enrich test cases Use by QA to strengthen Older examples and
Sandler, Tom Badgett mindset and defect-finding conditions, error guessing, cases, equivalence, beyond happy paths. defect-finding habits. process style.
principles. black-box testing. boundary analysis.
9 Effective Software Testing Maurício Aniche 2022 Core Modern developer-focused Frontend/backend/API test Unit/integration/system Use to decide which tests Use by developers writing Not a manual QA
testing across unit, strategy, testable design, testing, testability, mocks, Codex should add for practical tests. management book.
integration and system automation. coverage. implementation.
levels.
10 Machine Learning Andriy Burkov 2020 Important for AI Concise operational view of AI evaluation testing, model ML lifecycle, evaluation, Use for AI test plans and Use by AI engineers and Not UI/API QA focused.
Engineering ML testing, evaluation and quality, data leakage, data, deployment, separating model-quality QA validating AI behavior.
production risks. monitoring. monitoring. limits from bugs.

Minimum Reading Before Executing This Phase

- Lessons Learned in Software Testing: Best risk-based QA thinking.

- Explore It!: Best practical exploratory testing guide.

- Effective Software Testing: Modern implementation-level testing source.

Advanced Reading for Difficult Projects

 xUnit Test Patterns for automated test suites
 Growing OO Software for integrated systems
 Machine Learning Engineering for AI evaluation

P0_Source_Library - Operational Source Book Library

Phase Source Reading Protocol
 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Build requirement-to-test matrices
 Create manual, API, UI, backend, DB, regression and AI tests
 Write actionable bug reports
 Generate Codex fix prompts
 Produce Phase 6 security handoff

P0_Source_Library - Operational Source Book Library

Phase 6 - P6_Security - Security Review, Threat Modeling, RBAC, Data Privacy, API Security, File Security, AI Safety
Phase Mission
Review tested software for authentication, authorization, object-level access, sensitive data exposure, API/file/database/frontend risks, AI safety, logging, and deployment security handoff.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Threat Modeling: Designing Adam Shostack 2014 Core Primary source for Threat model triage, assets, Threat modeling process, Use to structure Phase 6 Use by security Does not cover every web
for Security systematic threat modeling actors, entry points, STRIDE, attack trees, security scope and threat reviewers/architects for exploit in depth.
during design/review. mitigations. mitigations, testing. model. review workshops.
2 Secure by Design Dan Bergh Johnsson, 2019 Core Excellent developer- Secure design patterns, Secure design, invariants, Use to generate secure-by- Use by developers to fix Less broad than full security
Daniel Deogun, Daniel oriented source for building legacy weakness review, domain primitives, legacy design findings and Codex security at model/design engineering texts.
Sawano security into domain design. domain-driven security. code weaknesses. fix prompts. level.
3 The Web Application Dafydd Stuttard, Marcus 2nd ed., 2011 Core Deep practical reference for API/web testing, auth, Authentication, sessions, Use to create adversarial Use by security testers to Old in places; supplement
Hacker's Handbook Pinto web app attack/defense sessions, input validation, access control, input checks against web/API understand exploit paths. with modern OWASP docs.
thinking. client-side controls. attacks, file attacks. features.
4 Web Security for Malcolm McDonald 2020 Important Developer-friendly web Secure coding, Browser security, injection, Use for practical secure Use by developers fixing Not a deep penetration
Developers security guide covering authentication, XSS, CSRF, auth, HTTPS, CORS, coding recommendations. common web testing book.
practical defenses. injection, deployment security headers. vulnerabilities.
basics.
5 API Security in Action Neil Madden 2020 Core Focused reference for API auth, authorization, API keys, OAuth2, tokens, Use to review API Use by backend/API Less UI/file-security
protecting APIs with auth, OAuth, tokens, rate limiting, access control, auth/error/object access engineers for secure focused.
tokens and access control. API threats. microservice APIs. risks. endpoints.
6 Security Engineering Ross Anderson 3rd ed., 2020 Advanced Comprehensive security Security architecture, Security economics, access Use for high-stakes or Use by senior security Very broad and dense.
engineering reference for privacy, abuse cases, control, protocols, privacy, sensitive-domain security architects.
high-risk systems. system-level risk. reliability. reviews.
7 Building Secure & Reliable Heather Adkins, Betsy 2020 Advanced Google source connecting Secure deployment, Security and reliability, Use to connect Phase 6 Use by security + Less focused on UI-level
Systems Beyer, Paul Blankinship, security, reliability, production controls, design, deployment, findings with Phase 7/8 DevOps/SRE teams. vulnerabilities.
Ana Oprea, Piotr production controls and incident readiness, recovery, operations. requirements.
Lewandowski, Adam operations. reliability/security link.
Stubblefield
8 Alice and Bob Learn Tanya Janca 2020 Important Approachable application AppSec review, secure Secure SDLC, testing, Use to make security Use by teams new to Less advanced than
Application Security security coverage for SDLC, common vulnerabilities, training, findings understandable AppSec. specialist books.
developers and teams. vulnerabilities, team culture. and actionable.
practices.
9 Privacy Engineering Michelle Finneran 2014 Advanced Useful for privacy, sensitive Data privacy, sensitive data Data lifecycle, privacy Use to review Use by privacy/security Less focused on code-level
Dennedy, Jonathan Fox, data, data flows and inventory, retention, data requirements, governance, personal/medical/financial leads for sensitive systems. web exploits.
Thomas R. Finneran minimization. flows. controls. data exposure and
retention.
10 Human-Centered AI Ben Shneiderman 2022 Important for AI Supports AI risk review, AI safety, human review, Reliable/safe AI, human Use to check AI outputs are Use by AI/product/security Not a technical adversarial
human control, confidence/failure states, control, governance advisory, reviewable and teams. ML book.
accountability and safe use. governance. structures. monitored.

Minimum Reading Before Executing This Phase

- Threat Modeling: Foundation for structured security review.

- Secure by Design: Connects security with domain/code design.

- API Security in Action: Critical for modern API-based apps.

Advanced Reading for Difficult Projects

 Security Engineering for sensitive/high-risk systems
 Building Secure & Reliable Systems for production risk
 Privacy Engineering for regulated/sensitive data
 Human-Centered AI for AI safety
P0_Source_Library - Operational Source Book Library
Phase Source Reading Protocol
 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Create threat models and release blockers
 Review auth, RBAC and object-level access
 Review API, file upload, frontend, database and logging risks
 Review AI safety and human control
 Produce Codex security fix prompts and Phase 7 handoff

P0_Source_Library - Operational Source Book Library

Phase 7 - P7_Deployment - Deployment, CI/CD, Environments, Database Migration, Rollback, Production Smoke Testing
Phase Mission
Release a tested and security-reviewed candidate safely with environment planning, CI/CD, backups, migrations, file/AI deployment, rollback, smoke tests, and monitoring handoff.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Continuous Delivery Jez Humble, David Farley 2010 Core Foundational deployment CI/CD, build-test-deploy Deployment pipeline, Use to design repeatable Use by DevOps/developers Older tooling, but principles
pipeline and release pipeline, release automated tests, config deployment steps and to build deployment remain durable.
automation source. automation, configuration. management, release gates. discipline.
strategy.
2 Accelerate Nicole Forsgren, Jez 2018 Core Evidence-based DevOps Deployment frequency, Capabilities, lean Use to define deployment Use by managers/DevOps Not a step-by-step
Humble, Gene Kim capabilities and delivery lead time, change fail rate, management, architecture, quality and team operating leads to improve delivery deployment manual.
performance reference. recovery, team practices. measurement. targets. system.
3 Release It! Michael T. Nygard 2nd ed., 2018 Core Production readiness Production smoke tests, Stability patterns, anti- Use to identify release risks Use by backend/DevOps Not CI/CD pipeline-specific
patterns, failure modes, resilience, stability, rollback patterns, capacity, and production failure engineers before enough alone.
stability and release risk. thinking. operations, deployment. scenarios. production release.
4 Site Reliability Engineering Betsy Beyer, Chris Jones, 2016 Core Google reference for Reliability, SLOs, Risk, SLOs, monitoring, Use to define reliability Use by SRE/DevOps teams Google-scale context may
Jennifer Petoff, Niall production reliability, SLOs, monitoring, toil, production automation, release expectations before to set production standards. need adaptation.
Richard Murphy risk and automation. practices. engineering. deployment.
5 The Site Reliability Betsy Beyer, Niall Richard 2018 Important More practical companion SLOs, incident response, SLOs, alerts, incident Use to prepare Phase 8 Use by SRE/ops teams to Assumes some operational
Workbook Murphy, David K. Rensin, to SRE with implementation on-call, alerting, production response, toil, service monitoring handoff during operationalize reliability. maturity.
Kent Kawahara, Stephen exercises. readiness. reliability. deployment.
Thorne
6 Building Secure & Reliable Heather Adkins et al. 2020 Advanced Connects secure Secrets, production Security/reliability, design, Use for secure deployment Use by security/DevOps Less beginner-friendly.
Systems deployment, reliability and controls, safe rollout, deployment, recovery, gates and production teams on sensitive
operational controls. secure operations. incident response. controls. deployments.
7 Infrastructure as Code Kief Morris 2nd ed., 2020 Important Practical source for Environment setup, IaC principles, patterns, Use to define environment Use by DevOps engineers Needs tool-specific docs for
managing environments infrastructure automation, workflows, testing, change and deployment managing infrastructure. Terraform/cloud providers.
repeatably. configuration, drift control. management. reproducibility.
8 Docker: Up & Running Sean P. Kane, Karl edition not verified Important Containerization reference Docker builds, images, Images, containers, Use when deployment Use by developers/DevOps Not enough for full
Matthias for app packaging and containers, compose, registries, compose, depends on containers or setting up containers. Kubernetes operations.
runtime consistency. runtime config. orchestration basics. local/prod parity.
9 Kubernetes: Up & Running Kelsey Hightower, Brendan edition not verified Advanced Container orchestration Kubernetes deployment, Pods, deployments, Use for Kubernetes Use by platform/DevOps Overkill for simple
Burns, Joe Beda, Lachlan reference for production services, config, scaling, services, config maps, deployment planning and engineers. Netlify/Render/VPS
Evenson cloud deployments. probes. probes, scaling. smoke checks. projects.
10 Database Reliability Laine Campbell, Charity 2017 Core for DB deployments Strong guide for production DB migration, backup, DB operations, backups, Use before any production Use by Less frontend/deployment
Engineering Majors database changes, backups restore, production data replication, change migration or rollback plan. backend/DB/DevOps pipeline coverage.
and reliability. safety, operations. management, reliability. teams.

Minimum Reading Before Executing This Phase

- Continuous Delivery: Core deployment pipeline thinking.

- Release It!: Production risk and smoke-test thinking.

- Database Reliability Engineering: Mandatory for safe DB migrations and backups.

Advanced Reading for Difficult Projects

 SRE books for reliability-heavy systems
 Infrastructure as Code for repeatable environments
 Kubernetes Up & Running for container orchestration
 Building Secure & Reliable Systems for sensitive systems

P0_Source_Library - Operational Source Book Library

Phase Source Reading Protocol
 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Create deployment/readiness plans
 Prepare frontend/backend/database/file/AI deployment checklists
 Design migration, backup and rollback plans
 Create production smoke tests
 Hand off monitoring to Phase 8

P0_Source_Library - Operational Source Book Library

Phase 8 - P8_Maintenance - Monitoring, Maintenance, Observability, Incident Response, Performance, Feedback,
Iteration
Phase Mission
Keep the system healthy after release through monitoring, observability, incident response, performance/reliability work, technical debt management, user feedback loops, AI monitoring, and next-iteration
routing.

10 Recommended Books
# Book Author Edition/Year Priority Why It Belongs Here Phase Tasks Covered Priority Chapters/Topics How ChatGPT Should Use Human Team Use Gaps
It
1 Observability Engineering Charity Majors, Liz Fong- 2022 Core Modern practical guide to Logs, metrics, traces, Events, telemetry, service- Use to define what Phase 8 Use by engineers/SREs Assumes modern tooling
Jones, George Miranda observability, debugging production debugging, level debugging, high- must watch and how to building observability. maturity.
and telemetry. operational learning. cardinality data, teams. investigate.
2 Site Reliability Engineering Beyer, Jones, Petoff, 2016 Core Foundation for reliability, Monitoring, error budgets, SLOs, monitoring, Use to structure reliability Use by SRE/DevOps teams Google-scale examples
Murphy monitoring, SLOs and reliability, toil reduction, automation, release goals and operational for reliability practice. need adaptation.
operational discipline. automation. engineering, incident policies.
response.
3 The Site Reliability Beyer, Murphy, Rensin, 2018 Core Practical exercises for SLO implementation, SLOs, alerts, incident Use to convert monitoring Use by operations teams to Requires operational
Workbook Kawahara, Thorne implementing SRE after alerting, on-call, incident response, toil, reliability handoff into operational implement SRE practices. ownership.
deployment. response, reliability testing. routines.
reviews.
4 Release It! Michael T. Nygard 2nd ed., 2018 Core Production anti-patterns Failure review, stability Stability anti-patterns, Use to classify incidents Use by backend/ops teams Less focused on product
and resilience patterns patterns, capacity, resilience patterns, and recurring production to harden systems after feedback loops.
remain vital after release. resilience backlog. capacity, operations. failures. release.
5 Effective DevOps Jennifer Davis, Katherine 2016 Important Covers culture, Incident culture, cross-team Collaboration, affinity, tools, Use to design maintenance Use by teams improving Less technical on
Daniels collaboration and maintenance, feedback, scaling, learning responsibilities and DevOps collaboration. observability internals.
operational workflow. continuous improvement. organizations. communication loops.
6 The Practice of Cloud Thomas A. Limoncelli, 2014 Advanced Strong operations reference Operations processes, Operations, monitoring, Use for mature operational Use by ops/SRE/admin Large and older in cloud-
System Administration Strata R. Chalup, Christina for services, change, service design, monitoring, change, service launch, checklists and process teams. native tooling.
J. Hogan monitoring and scale. change management. incident response. design.
7 Software Engineering at Titus Winters, Tom 2020 Important Excellent source for long- Technical debt, code Sustainability, style, testing, Use to plan maintenance Use by teams maintaining Google-context requires
Google Manshreck, Hyrum Wright term maintainability and health, ownership, testing, code review, dependency standards and code health code over time. adaptation.
engineering culture. large-scale evolution. management. practices.
8 Managing Technical Debt Philippe Kruchten, Robert 2019 Core for debt Focused source for Debt backlog, prioritization, Debt concepts, Use to classify Use by architects/PMs for Less incident/observability
L. Nord, Ipek Ozkaya identifying, measuring and architecture debt, architecture, measurement, maintenance work and debt backlog decisions. focused.
managing technical debt. maintenance planning. management strategies. avoid uncontrolled debt.
9 Working Effectively with Michael C. Feathers 2004 Important Maintenance often Bug fixes, regression-safe Seams, dependencies, Use to route maintenance Use by developers fixing Code-focused, not
Legacy Code becomes legacy work; this changes, characterization characterization tests, safe fixes through safe Codex old systems. operational monitoring.
enables safe change. tests. change techniques. prompts.
10 Team Topologies Matthew Skelton, Manuel 2019 Important Useful for organizing teams Team ownership, feedback Team types, interaction Use to suggest ownership Use by leads/managers Not a technical monitoring
Pais around flow, ownership and loops, platform/enabling modes, cognitive load, models for maintenance organizing teams. book.
maintainability. teams, maintenance platform teams. and scaling.
responsibilities.

Minimum Reading Before Executing This Phase

- Observability Engineering: Best modern source for monitoring/debugging.

- The Site Reliability Workbook: Practical SRE implementation.

- Managing Technical Debt: Keeps maintenance from becoming chaos.

Advanced Reading for Difficult Projects

 The Practice of Cloud System Administration for mature ops
 Software Engineering at Google for long-term code health
P0_Source_Library - Operational Source Book Library
 Team Topologies for large teams
 Working Effectively with Legacy Code for old systems

Phase Source Reading Protocol

 Read the current phase PDF as the identity of the task and permanent operational reference.
 Read all previous phase handoffs and source files before answering or executing.
 Read all attached documentation, user constraints, and project-specific notes.
 Consult the minimum books before normal execution and advanced books before enterprise, legacy, AI, security-sensitive, or production work.
 If code is involved, read Codex inspection/implementation reports before generating the next prompt.

What This Phase Can Execute After Reading These Books

 Set monitoring and observability routines
 Handle incidents and post-release bugs
 Manage technical debt and performance work
 Route feedback to earlier phases
 Monitor AI behavior and plan safe iterations

Global Source Strategy

1. Books repeated or useful across multiple phases
 Designing Data-Intensive Applications: planning, coding, deployment and maintenance for data-heavy systems.
 Working Effectively with Legacy Code: existing project audit, coding, QA and maintenance.
 Building Machine Learning Powered Applications / Designing Machine Learning Systems: AI discovery, planning, coding, testing, deployment and monitoring.
 Site Reliability Engineering / The Site Reliability Workbook: deployment, production smoke testing, monitoring, maintenance and incident response.
 Threat Modeling / Secure by Design: security review, API design, backend planning and production readiness.

2. Foundational books for the entire system

 Software Requirements
 User Story Mapping
 Fundamentals of Software Architecture
 Code Complete
 Refactoring
 Lessons Learned in Software Testing
 Threat Modeling
 Continuous Delivery
 Observability Engineering

3. Advanced-project-only books
 Requirements Engineering by van Lamsweerde
 Software Architecture: The Hard Parts
 Implementing Domain-Driven Design
 Patterns of Enterprise Application Architecture
 Security Engineering
 The Practice of Cloud System Administration

4. Essential for AI projects

 Building Machine Learning Powered Applications
 Designing Machine Learning Systems
P0_Source_Library - Operational Source Book Library
 Machine Learning Engineering
 Human-Centered AI

5. Essential for existing/legacy projects

 Working Effectively with Legacy Code
 Refactoring
 User Story Mapping for change scope
 Lessons Learned in Software Testing for regression
 Release It! for production risk

6. Essential for security-sensitive systems

 Threat Modeling
 Secure by Design
 API Security in Action
 Security Engineering
 Privacy Engineering
 Building Secure & Reliable Systems

7. Essential for production deployment

 Continuous Delivery
 Release It!
 Database Reliability Engineering
 Site Reliability Engineering
 Infrastructure as Code
 Building Secure & Reliable Systems

8. Recommended reading order for a beginner

 The Pragmatic Programmer
 User Story Mapping
 Software Requirements
 Information Architecture
 Designing Interfaces
 Code Complete
 Effective Software Testing
 Web Security for Developers
 Continuous Delivery
 Observability Engineering

9. Recommended reading order for an advanced software architect

 Domain-Driven Design
 Implementing Domain-Driven Design
 Fundamentals of Software Architecture
 Software Architecture: The Hard Parts
 Designing Data-Intensive Applications
 Patterns of Enterprise Application Architecture
 Threat Modeling
 Release It!
 Site Reliability Engineering
 Software Engineering at Google

P0_Source_Library - Operational Source Book Library

10. Recommended reading order for a team executing a real project quickly
 INSPIRED
 Software Requirements
 User Story Mapping
 Information Architecture
 Fundamentals of Software Architecture
 Principles of Web API Design
 Code Complete
 Effective Software Testing
 Threat Modeling
 Continuous Delivery

Final Rule
Every book in this source library must be used as an execution reference, not as decoration. Before any phase task, ChatGPT should identify the relevant phase, read the phase PDF and source material,
consult the minimum books, and produce outputs with confirmed facts, assumptions, open questions, risks, handoffs, and return loops.

P0_Source_Library - Operational Source Book Library