Updated in backend code to handle findings integration, replacing previous placeholder.

DataLens submits commits to DEPLOYMENT_QUEUE.md to request deployments, which are reviewed by the Ops Engineer. DataLens agent deployment requests are appended to DEPLOYMENT_QUEUE.md for review and approval by Ops Engineer. Ops Engineer approves deployments listed in DEPLOYMENT_QUEUE.md and authorizes execution. DataLens uses DEPLOYMENT_QUEUE.md to track deployment requests and statuses via the Ops Engineer workflow.

The DUCKDB_TO_PG_TYPES mapping guides PgDataService in converting DuckDB data types to PostgreSQL types when loading data.

Design element specifying entity attributes, including element_type and identification rules, appears complete and up-to-date based on the message.

PHASE2_SCOPE_DECISION.md contains the IMPLEMENTATION_PLAN.md design element. PHASE2_SCOPE_DECISION.md includes IMPLEMENTATION_PLAN.md as part of the Phase 2 research outputs. Phase 2 research outputs include IMPLEMENTATION_PLAN.md as a component of research.

DataLens must read and follow the INFRASTRUCTURE.md document during every session before work. DataLens agent must read and follow the infrastructure rules documented in INFRASTRUCTURE.md before starting work. INFRASTRUCTURE.md reserves port 8002 for the DataLens backend. INFRASTRUCTURE.md reserves port 8002 for DataLens backend.

IronClaw agent UI button was added to the analysis page frontend to provide navigation to the IronClaw agent feature. IronClaw navigation buttons are UI components part of the IronClaw agent feature. IronClaw Agent UI buttons code was added in commit e383323. IronClaw Agent UI buttons code was added in commit e383323. IronClaw Agent UI buttons code was added in commit e383323.

PHASE2_SCOPE_DECISION.md contains the LOAD_STRATEGY.md design element. Phase 2 research outputs include LOAD_STRATEGY.md as a component of research.

PHASE2_SCOPE_DECISION.md includes the Memory decision point document dated 2026-02-25. PHASE2_SCOPE_DECISION.md includes the Memory decision point document as part of the Phase 2 research outputs. Phase 2 research outputs include the Memory decision point document as part of the documentation.

PHASE2_SCOPE_DECISION.md includes the Memory research document dated 2026-02-24.

DataLens checks GPU usage via nvidia-smi before any GPU work.

Documentation detailing the GPU-focused document extraction system, protocols, and deployment procedures, aligned with recent implementation efforts.

A requirement doc that summarizes a GPU-first document extraction system, its architecture, and performance expectations for DataLens Phase 2.

The plan outlines a phased approach for MVP to ambitious features, starting with a 5-7 day MVP deployment, based on research and decision memos. PHASE2_IMPLEMENTATION_PLAN.md provides go/no-go recommendation and effort analysis for Phase 2 file types processing PHASE2_SCOPE_DECISION.md includes PHASE2_IMPLEMENTATION_PLAN.md as part of the Phase 2 research outputs. Phase 2 research outputs include PHASE2_IMPLEMENTATION_PLAN.md as part of the documentation. Sonnet 4.6 created the PHASE2_IMPLEMENTATION_PLAN.md containing the go/no-go recommendation and effort versus value analysis. The PHASE2_UNIFIED_STRATEGY.md and PHASE2_IMPLEMENTATION_PLAN.md documents contain complementary research outputs informing Phase 2 implementation decisions.

This document details the load strategy for Phase 2, referencing file naming conventions and strategic decisions in the implementation documentation. PHASE2_SCOPE_DECISION.md includes PHASE2_LOAD_STRATEGY.md as part of the Phase 2 research outputs. Phase 2 research outputs include PHASE2_LOAD_STRATEGY.md as part of the documentation.

PHASE2_SCOPE_DECISION.md contains a comparison between MVP and Ambitious options. PHASE2_SCOPE_DECISION.md includes the Memory research document dated 2026-02-24. PHASE2_SCOPE_DECISION.md includes the Memory decision point document dated 2026-02-25. PHASE2_SCOPE_DECISION.md contains research outputs related to Phase 2. PHASE2_SCOPE_DECISION.md contains the LOAD_STRATEGY.md design element. PHASE2_SCOPE_DECISION.md contains the IMPLEMENTATION_PLAN.md design element. PHASE2_SCOPE_DECISION.md recommends starting with the MVP option for 5-7 days, intending to expand to Ambitious if policy questions arise. PHASE2_SCOPE_DECISION.md document defines the side-by-side comparison and decision points of the Phase 2 Strategy Research & Decision Point PHASE2_SCOPE_DECISION.md includes IMPLEMENTATION_PLAN.md as part of the Phase 2 research outputs. PHASE2_SCOPE_DECISION.md includes the Memory research document as part of the Phase 2 research outputs. PHASE2_SCOPE_DECISION.md includes the Memory decision point document as part of the Phase 2 research outputs. PHASE2_SCOPE_DECISION.md includes PHASE2_IMPLEMENTATION_PLAN.md as part of the Phase 2 research outputs. PHASE2_SCOPE_DECISION.md includes PHASE2_LOAD_STRATEGY.md as part of the Phase 2 research outputs. Phase 2 research outputs contain PHASE2_SCOPE_DECISION.md. Opus 4.6 created the PHASE2_SCOPE_DECISION.md which compares MVP vs Ambitious approaches, provides timeline, risk analyses, and file type strategies.

DataLens follows a mandatory workflow for features which includes referring to the skills/brainstorming/SKILL.md design element for brainstorming steps. DataLens agent mandates following the workflow defined in skills/brainstorming/SKILL.md for new features: Brainstorm, Design, Review, Build. DataLens mandates following the Brainstorm-Design-Review-Build workflow described in skills/brainstorming/SKILL.md for new features and significant changes.

Vanna 2.0 architecture supports streaming UI components with progress updates and structured data

question_router.py uses translate_duckdb_to_pg to convert DuckDB-style SQL to PostgreSQL-compatible SQL before execution.