chore: remove unused PostgreSQL and Azure database infrastructure by bkrabach · Pull Request #5 · microsoft/amplifier

Brian Krabach (bkrabach) · 2025-09-10T22:30:27Z

Remove all PostgreSQL-related code and dependencies that were never actually
used by the application. Analysis revealed that all modules use file-based
storage (JSON/JSONL in .data/) rather than PostgreSQL.

Changes:

Remove psycopg2-binary dependency
Delete unused db_setup module (connection, schema, setup)
Delete Azure PostgreSQL infrastructure scripts and Bicep templates
Remove DATABASE_URL configuration from .env.example
Remove 67 lines of unused Makefile targets (azure-*, *-db)
Delete PostgreSQL setup documentation
Add REMOVED_POSTGRESQL.md to document what was removed and why

This aligns with the ruthless simplicity philosophy - removing ~1900 lines
of unused complexity. All storage remains file-based as it always was.
The knowledge system, memory system, and claude-web continue to function
exactly as before.

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Remove all PostgreSQL-related code and dependencies that were never actually used by the application. Analysis revealed that all modules use file-based storage (JSON/JSONL in .data/) rather than PostgreSQL. Changes: - Remove psycopg2-binary dependency - Delete unused db_setup module (connection, schema, setup) - Delete Azure PostgreSQL infrastructure scripts and Bicep templates - Remove DATABASE_URL configuration from .env.example - Remove 67 lines of unused Makefile targets (azure-*, *-db) - Delete PostgreSQL setup documentation - Add REMOVED_POSTGRESQL.md to document what was removed and why This aligns with the ruthless simplicity philosophy - removing ~1900 lines of unused complexity. All storage remains file-based as it always was. The knowledge system, memory system, and claude-web continue to function exactly as before. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>

Complete comprehensive technical specification library with all 44 principles: **People (6 specs)** - #1 Small AI-first working groups - #2 Strategic human touchpoints only - #3 Prompt engineering as core skill - microsoft#4 Test-based verification over code review - microsoft#5 Conversation-driven development - microsoft#6 Human escape hatches always available **Process (13 specs)** - microsoft#7 Regenerate, don't edit - microsoft#8 Contract-first everything - microsoft#9 Tests as the quality gate - microsoft#10 Git as safety net - microsoft#11 Continuous validation with fast feedback - microsoft#12 Incremental processing as default - microsoft#13 Parallel exploration by default - microsoft#14 Context management as discipline - microsoft#15 Git-based everything - microsoft#16 Docs define, not describe - microsoft#17 Prompt versioning and testing - microsoft#18 Contract evolution with migration paths - microsoft#19 Cost and token budgeting **Technology (18 specs)** - microsoft#20 Self-modifying AI-first codebase - microsoft#21 Limited and domain-specific by design - microsoft#22 Layered virtualization - microsoft#23 Protected self-healing kernel - microsoft#24 Long-running agent processes - microsoft#25 Simple interfaces by design - microsoft#26 Stateless by default - microsoft#27 Disposable components everywhere - microsoft#28 CLI-first design - microsoft#29 Tool ecosystems as extensions - microsoft#30 Observability baked in - microsoft#31 Idempotency by design (reference) - microsoft#32 Error recovery patterns built in - microsoft#33 Graceful degradation by design - microsoft#34 Feature flags as deployment strategy - microsoft#35 Least-privilege automation - microsoft#36 Dependency pinning and security scanning - microsoft#37 Declarative over imperative **Governance (7 specs)** - microsoft#38 Access control and compliance - microsoft#39 Metrics and evaluation everywhere - microsoft#40 Knowledge stewardship and institutional memory - microsoft#41 Adaptive sandboxing with explicit approvals - microsoft#42 Data governance and privacy controls - microsoft#43 Model lifecycle management - microsoft#44 Self-serve recovery with known-good snapshots Each specification includes: - Plain-language definition - AI-first development rationale - 4-6 implementation approaches - 5 good/bad example pairs with working code - 6 related principles with relationships - 7 common pitfalls with examples - Tools organized by category - 12 actionable checklist items Statistics: - 44 specifications totaling ~10,000+ lines - 220+ good/bad code example pairs - 240+ implementation approaches - 300+ documented anti-patterns - 500+ tools and frameworks - 250+ cross-principle relationships Created through parallel AI agent execution demonstrating Principle microsoft#13 (Parallel Exploration by Default). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>

CRITICAL BUG FIX - Tool invocation was failing with Anthropic API error: "unexpected tool_use_id found in tool_result blocks: unknown" Root Causes: 1. Missing assistant message with tool_use blocks in context 2. Missing tool_call_id in tool result messages 3. Improper message conversion losing tool_use information Fixes Applied: - BasicOrchestrator: Add assistant message with tool_calls to context before executing tools (required by Anthropic API) - BasicOrchestrator: Include tool_call_id when adding tool results - AnthropicProvider: Preserve tool_use blocks in message conversion Impact: System was completely non-functional for tool invocation Status: VERIFIED FIXED by bug-hunter agent Files Modified: - amplifier-mod-loop-basic/__init__.py (lines 102-144) - amplifier-mod-provider-anthropic/__init__.py (message conversion) - BUGFIX_REPORT.md (documented issue #5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>

…crosoft#5) * chore: remove unused PostgreSQL and Azure database infrastructure Remove all PostgreSQL-related code and dependencies that were never actually used by the application. Analysis revealed that all modules use file-based storage (JSON/JSONL in .data/) rather than PostgreSQL. Changes: - Remove psycopg2-binary dependency - Delete unused db_setup module (connection, schema, setup) - Delete Azure PostgreSQL infrastructure scripts and Bicep templates - Remove DATABASE_URL configuration from .env.example - Remove 67 lines of unused Makefile targets (azure-*, *-db) - Delete PostgreSQL setup documentation - Add REMOVED_POSTGRESQL.md to document what was removed and why This aligns with the ruthless simplicity philosophy - removing ~1900 lines of unused complexity. All storage remains file-based as it always was. The knowledge system, memory system, and claude-web continue to function exactly as before. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Merge remote-tracking branch 'origin/main' into remove-postgres

… for v0.3.0 Created feature scope and sprint plan for v0.3.0 "Test Case + Basic Regeneration" focusing on template-based document regeneration with diff preview workflow. Convergence Session (2025-11-19): - Defined 5 must-have features for reliable doc regeneration - Created test case template for amplifier/README.md - Deferred 21 features to backlog (updated MASTER_BACKLOG to 57 items) - Captured convergence completion summary Sprint Planning (v0.3.0): - Sprint 8 (4 days): Template parser & manual regen command - Sprint 9 (3 days): Source context & structure preservation - Sprint 10 (3 days): Change detection & user confirmation - Integrated issues microsoft#4, microsoft#5, microsoft#6, microsoft#7 into sprint work Workflow Improvements: - Fixed convergence-architect to create all 4 required outputs - Fixed sprint-planner to use proper versioned directory structure - Added test case template creation to convergence Phase 3 - Added validation checklists to prevent incomplete workflows Test Case: - Created templates/amplifier_readme.json as primary test case - 9 sections covering real-world README structure - Will validate all v0.3.0 features against actual project 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>

…-patterns (#269) Surface recent ecosystem changes in amplifier-expert so it routes researchers correctly: agents/amplifier-expert.md: - Tier 0 Key Documents: add @core:CONTRACTS.md (was missing) as the authoritative source for module protocols and lifecycle methods - Key Kernel Concepts: add Module Lifecycle as the 5th concept (mount + optional on_session_ready), with pointer to core-expert and CONTRACTS.md for depth — placed in concepts, not Module Types Reference, to keep lifecycle distinct from module type taxonomy - Anti-Patterns to Flag: append two entries * register_capability for shared channels — symptom (events invisible to collect_contributions), cause, fix (use register_contributor); cites CONTRIBUTION_CHANNELS.md * Polluted test environment masking runtime deps — symptom (smoke tests pass, clean install fails), cause (transitive deps mask missing runtime declarations), fix (pristine-import test in python:*-slim Docker); cites release-mandate Incident #5 Light touch — preserves existing item numbering for any external references; appends rather than reorders. 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-authored-by: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>

Brian Krabach (bkrabach)and others added 2 commits September 10, 2025 15:19

Merge remote-tracking branch 'origin/main' into remove-postgres
8ef46ee

Brian Krabach (bkrabach) merged commit 534c7cc into mainSep 10, 2025
1 check passed

Brian Krabach (bkrabach) deleted the remove-postgres branch September 10, 2025 22:31

Brian Krabach (bkrabach) mentioned this pull request Apr 25, 2026
docs(amplifier-expert): add CONTRACTS.md + lifecycle concept + 2 anti-patterns #269
Merged

Navigation Menu

Uh oh!

chore: remove unused PostgreSQL and Azure database infrastructure - #5

chore: remove unused PostgreSQL and Azure database infrastructure#5
Brian Krabach (bkrabach) merged 2 commits into
mainfrom
remove-postgres

Brian Krabach (bkrabach) commented Sep 10, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant