Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 2.72 KB

File metadata and controls

42 lines (31 loc) · 2.72 KB

Architecture Decision Records

This directory contains architectural decisions for the Agent Debugger product evolution from local MVP to revenue-generating SaaS.

Each decision is numbered and self-contained. Decisions can be superseded but not deleted.

Index

ADR Title Status
001 Product Positioning Under Review — test positioning variants with beta users
002 Deployment Model Accepted
003 Pricing Strategy Under Review — validate price points, consider $19 + freemium
004 Target Users & Framework Priority Accepted
005 Architecture for Scale Accepted
006 SDK Distribution & Developer Experience Accepted
007 Replay Fidelity Strategy Under Review — test user reaction, consider cached replay mode
008 Security, Auth & Privacy Accepted
009 Frontend Strategy Under Review — reconsider lightweight VS Code extension
010 Competitive Differentiation Under Review — narrow to 1-2 hero features
011 Build Sequence Accepted
012 Key Assumptions & Constraints Under Review — adjust user targets to 20-50 first

Implementation Scope

The 6 accepted ADRs form the build foundation:

  • 002 (Open-source SDK + cloud SaaS) + 005 (same codebase, config-driven) = infrastructure approach
  • 004 (LangChain first) + 006 (three integration levels, <60s to first value) = SDK priority
  • 008 (API keys, tenant isolation, redaction) = security baseline
  • 011 (10 weeks: cloud backend → auth+teams → beta launch) = execution timeline

The 6 under-review ADRs are deferred decisions that will be validated through beta user feedback.

Current Reality

As of 2026-03-23, the accepted ADRs are at different implementation stages:

  • ADR-006: partially implemented. agent_debugger.init() and env-based config now exist in code.
  • ADR-008: partially implemented. API key helpers, auth models, and redaction modules exist, but tenant enforcement and write-path integration are still pending.
  • ADR-011: partially underway. The local debugger, benchmark seeds, and docs structure are strong; cloud-hardening work has started but is not complete.

Read ../progress.md for the implementation snapshot that complements these decisions.