Conversation
…mory Rename P03 from Persistent Memory to Checkpoint Recovery and P04 from Memory Lifecycle to Agent Memory. Update the narrative flow so P04 is on the main path instead of an optional branch off P03.
…entions Replace Exercises and Trade-offs sections with What You Have Learned. Add numbered implementation walkthrough structure and endpoints.http mention. Skip When to Use and Verification sections by default.
Replace verbose code excerpts, exercises, and trade-off tables with numbered walkthrough steps, file references, and What You Have Learned takeaways. Update next-pattern links to point to checkpoint recovery.
Add persistence module with create_postgres_pool, setup_checkpointer, and close_checkpointer. Add postgres_uri to Settings and export new helpers from agent_common. Deps: langgraph-checkpoint-postgres, psycopg[binary,pool].
Add Pattern 03 with PostgreSQL-backed checkpointer, resume-after-failure semantics, human-in-the-loop interrupt/resume, and the same 5-agent fan-out/fan-in graph from P02. Includes FastAPI service, MCP server, Docker Compose with PostgreSQL, and full test suite.
…ocstring P03 README claimed the graph was unchanged from P02 but it adds project_verifier and project_selector nodes. Update the At a Glance table, Mermaid diagram, and description paragraph. Add P03 CHANGELOG entry. Remove stale plan reference from intelligence_compiler docstring in both P02 and P03.
Owner
Author
|
Review complete. All three findings addressed in fd7965c: README graph description corrected (verifier/selector now shown), CHANGELOG P03 entry added, intelligence_compiler docstring fixed in P02 and P03. CI green (6/6). Ready to merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Complete foundation tier (Patterns 01-03) with infrastructure, shared library, documentation, and CI/CD.
Patterns
01-multi-agent-single-systeminto a clean 3-agent sequential pipeline (planner → scanner → compiler) with FastAPI, typed state, graceful degradation, and full test suite.agent_common.persistencemodule inlibs/common.Infrastructure & Shared Library
libs/common(agent_common): standardized Settings, LLM provider selection, LangSmith tracing with per-example tags, and PostgreSQL persistence helpers.Dockerfile.agent), per-exampledocker-compose.yml.run_test_suite.pyandrun_mypy.pywrapper scripts to avoid cross-example conflicts. Pre-commit hooks with ruff, secrets detection, and conventional commit checks.Documentation
Test plan
uv run python scripts/testing/run_test_suite.pypasses for all three examplesuv run python scripts/linting/run_mypy.pypassesuv run ruff check .anduv run ruff format --check .passdocker compose upworks for each example (01, 02, 03)