finish first round

Author: ijac13

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+  "dbt.enableNewLineagePanel": true
+}

claude/terminology.md

@@ -17,8 +17,12 @@ This guide helps maintain consistent, data-team-friendly language across all Rec
 | **validation results** | diff output, comparison data | What users see in Recce |
 | **impact analysis** | dependency analysis, lineage | Understanding downstream effects |
 | **data changes** | code changes, model changes | What users are validating |
+| **code change** | code modification | Specific term for data team workflows |
 | **validation workflow** | testing workflow, QA process | How teams use Recce |
 | **diff** | comparison, delta | Data teams familiar with git diff, use freely |
+| **Recce**| recce | this is the brand name, should always use "Recce" | 
+| **dbt** | DBT | this is the brand name, should always use lower cases| 
+
 
 ### Data vs Software Terms
 
@@ -27,6 +31,7 @@ This guide helps maintain consistent, data-team-friendly language across all Rec
 | **data warehouse** | database | Data teams distinguish warehouses from operational databases |
 | **development stage** | environment | "Environment" confuses (warehouse vs dev/prod) |
 | **data models** | components | dbt models vs software components |
+| **model** | node | Data teams think "model", software teams think "node" |
 | **release changes** | deploy | Data teams "release" changes, don't "deploy" infrastructure |
 | **validation checks** | unit tests | Data quality checks vs code functionality tests |
 | **automated validation** | CI/CD pipeline | Data processing vs deployment automation |

claude/writing-principles.md

@@ -155,9 +155,21 @@ These structure is to align users adoption process. Start from using in PR, coll
 
 
 
-## Content Structure Template
+## Content format guide
 
-Use markdown
+1. **Use markdown** for all content formatting
+2. **Add line breaks** between sentences and bullet points or numbered lists to ensure proper rendering
+3. **Page title capitalization**: Capitalize every word in the main page title (Title Case)
+4. **Heading capitalization**: For H2 headings and below, only capitalize the first word (Sentence case)
+5. **Image format**: Use the standardized figure format with shadow styling:
+
+```markdown
+<figure markdown>
+  ![Recce Lineage Diff](../assets/images/3-view-modified/lineage-diff.gif){: .shadow}
+  <figcaption>Interactive lineage graph showing modified models</figcaption>
+</figure>
+```
+6. Use bold only when it's neccessary. Too many highlight will lose focus and not easy to read. 
 
 ### Page Structure Template
 ```markdown

docs/2-getting-started/start-free-with-cloud.md

@@ -59,7 +59,7 @@ If you don't have a dbt project, you can just click "Launch" to see the Jaffle S
 ## Step 4: Automate Everything → CI/CD Integration
 
 - **What you'll unlock**: Automatic validation on every PR
-- **Setup needed**: [Set up automated workflows](../7-workflow-integration/automate-in-pr.md)
+- **Setup needed**: [Set up automated workflows](../7-cicd/scenario-ci.md)
 - **Ultimate value**:
     - ✅ **Automatic PR checks** - validation runs on every push
     - ✅ **Team workflows** - standardized validation across team
@@ -69,7 +69,7 @@ If you don't have a dbt project, you can just click "Launch" to see the Jaffle S
 
 After launching Recce, explore:
 
-- [View modified](../3-view-modified/lineage.md)
+- [View modified](../3-visualized-change/lineage.md)
 - [View downstream impacts](../4-downstream-impacts/impact-radius.md)
 - [Data diffing](../5-data-diffing/query.md)
 

docs/3-view-modified/column-level-lineage.md

@@ -1,16 +1,16 @@
 ---
-title: Code Diff
+title: Code Change
 ---
 
-# Code Diff
+# Code Change
 
-The Code Diff feature allows you to compare the SQL code changes between your current branch and the base branch, helping you understand exactly what has been modified in your dbt models.
+The Code Change feature allows you to compare the SQL code changes between your current branch and the base branch, helping you understand exactly what has been modified in your dbt models.
 
-## Viewing Code Changes
+## Viewing Code Change
 
 When you identify a modified model in the [Lineage Diff](lineage.md), you can examine the specific code changes to understand the nature of the modifications.
 
-### Opening Code Diff
+### Opening Code Change
 
 To view the code changes for a model:
 
@@ -19,7 +19,7 @@ To view the code changes for a model:
 3. The code diff will display showing the changes between branches
 
 <figure markdown>
-  ![View code changes for a model](../assets/images/3-view-modified/view-code-of-model.png){: .shadow}
+  ![View code changes for a model](../assets/images/3-visualized-change/view-code-of-model.png){: .shadow}
   <figcaption>Viewing code changes for a modified model</figcaption>
 </figure>
 
@@ -46,7 +46,7 @@ For complex changes or detailed review, you can expand the code diff to full scr
 3. Use this view when conducting thorough code reviews or sharing changes with team members
 
 <figure markdown>
-  ![Expanded full-screen view of code changes](../assets/images/3-view-modified/full-view-code-of-model.png){: .shadow}
+  ![Expanded full-screen view of code changes](../assets/images/3-visualized-change/full-view-code-of-model.png){: .shadow}
   <figcaption>Full-screen view for detailed code review</figcaption>
 </figure>
 

docs/3-view-modified/code-diff.md docs/3-visualized-change/code-change.mddocs/3-view-modified/code-diff.md renamed to docs/3-visualized-change/code-change.md

@@ -0,0 +1,39 @@
+---
+title: Column-Level Lineage
+---
+
+Column-Level Lineage provides visibility into the upstream and downstream relationships of a column.
+
+Common use-cases for column-level lineage are
+
+1. **Source Exploration**: During development, column-level lineage helps you understand how a column is derived.
+2. **Impact Analysis**: When modifying the logic of a column, column-level lineage enables you to assess the potential impact across the entire DAG.
+3. **Root Cause Analysis**: Column-level lineage helps identify the possible source of errors by tracing data lineage at the column level.
+
+## Usage
+
+1. Select a node in the lineage DAG, then click the column you want to view.
+
+    ![alt text](../assets/images/3-visualized-change/cll-1.png){: .shadow}
+
+1. The column-level lineage for the selected column will be displayed.
+
+    ![alt text](../assets/images/3-visualized-change/cll-2.png){: .shadow}
+
+1. To exit column-level lineage view, click the close button in the upper-left corner.
+
+    ![alt text](../assets/images/3-visualized-change/cll-3.png){: .shadow}
+
+# Transformation Types
+
+The transformation type is also displayed for each column, which will help you understand how the column was generated or modified.
+
+| Type | Description  |
+|------|--------------|
+| Pass-through  |The column is directly selected from the upstream table. |
+| Renamed | The column is selected from the upstream table but with a different name. |
+| Derived | The column is created through transformations applied to upstream columns, such as calculations, conditions, functions, or aggregations. |
+| Source | The column is not derived from any upstream data. It may originate from a seed/source node, literal value, or data generation function. |
+| Unknown | We have no information about the transformation type. This could be due to a parse error, or other unknown reason. |
+
+

docs/3-visualized-change/column-level-lineage.md

@@ -19,19 +19,45 @@ Data lineage tracks the flow and transformation of data through your dbt project
 From the Lineage view, you can determine which models to investigate further and perform various data validation checks that serve as proof-of-correctness of your work.
 
 <figure markdown>
-  ![Recce Lineage Diff](../assets/images/3-view-modified/lineage-diff.gif){: .shadow}
+  ![Recce Lineage Diff](../assets/images/3-visualized-change/lineage-diff.gif){: .shadow}
   <figcaption>Interactive lineage graph showing modified models</figcaption>
 </figure>
 
 !!! tip "Getting Started"
     When you first open Recce, the lineage graph automatically loads showing only the models affected by your changes. This focused view helps you quickly understand the impact of your work.
 
+### Filter Nodes
+
+In the top control bar, you can change the rule to filter the nodes:
+
+1. **Mode:**
+   - **Changed Models:** Modified nodes and their downstream + 1st degree of their parents.
+   - **All:** Show all nodes.
+1. **Package:** Filter by dbt package names.
+1. **Select:** Select nodes by [node selection](./node-selection.md).
+1. **Exclude:** Exclude nodes by [node selection](./node-selection.md).
+
+### Select Nodes
+
+Click a node to select it, or click the **Select nodes** button in the top-right corner to select multiple nodes for further operations. For detail, see the [Multi Nodes Selections](#multi-nodes-selection) section
+
+### Row Count Diff
+
+A row count diff can be performed on nodes selected using the `select` and `exclude` options:
+
+![](../assets/images/3-visualized-change/row-count-diff-selector.gif){: .shadow}
+
+After selecting nodes, run the row count diff by:
+
+1. Clicking the 3 dots (**...**) button in the top-right corner.
+2. Clicking **Row Count Diff by Selector**.
+
 ## Understanding Model Nodes
 
 ### Visual Status Indicators
 
 <figure markdown>
-  ![Node example](../assets/images/3-view-modified/node.png){: .shadow}
+  ![Node example](../assets/images/3-visualized-change/node.png){: .shadow}
   <figcaption>Example model node with status indicators</figcaption>
 </figure>
 
@@ -52,15 +78,15 @@ Each model node displays two icons in the bottom-right corner that indicate dete
 Grayed-out icons indicate no changes were detected in that category.
 
 <figure markdown>
-  ![Model with Schema Change detected](../assets/images/3-view-modified/model-schema-change-detected.png){: .shadow}
+  ![Model with Schema Change detected](../assets/images/3-visualized-change/model-schema-change-detected.png){: .shadow}
   <figcaption>Model with Schema Change detected</figcaption>
 </figure>
 
 !!! note "Row Count Detection"
     The row count icon only appears after you've run a row count diff on that specific model. This helps you track which models you've already validated.
 
 <figure markdown>
-  ![Open node details panel](../assets/images/3-view-modified/node-details-panel.gif){: .shadow}
+  ![Open node details panel](../assets/images/3-visualized-change/node-details-panel.gif){: .shadow}
   <figcaption>Open the node details panel</figcaption>
 </figure>
 
@@ -83,7 +109,7 @@ Schema diff helps you understand structural changes to your models.
 Click on a model to view its schema diff in the node details panel.
 
 <figure markdown>
-  ![Recce Schema Diff](../assets/images/3-view-modified/schema-diff.gif){: .shadow}
+  ![Recce Schema Diff](../assets/images/3-visualized-change/schema-diff.gif){: .shadow}
   <figcaption>Interactive schema diff showing column changes</figcaption>
 </figure>
 
@@ -97,7 +123,7 @@ Schema diff identifies:
 - **Data type changes**: Modifications to column types
 
 <figure markdown>
-  ![Recce Schema Diff](../assets/images/3-view-modified/schema-diff.png){: .shadow}
+  ![Recce Schema Diff](../assets/images/3-visualized-change/schema-diff.png){: .shadow}
   <figcaption>Schema diff showing renamed column</figcaption>
 </figure>
 
@@ -122,7 +148,7 @@ Learn more about viewing and analyzing code changes in the [Code Diff guide](cod
 The node details panel provides comprehensive information about the selected model:
 
 <figure markdown>
-  ![Explore the model](../assets/images/3-view-modified/explore-the-model.png){: .shadow}
+  ![Explore the model](../assets/images/3-visualized-change/explore-the-model.png){: .shadow}
   <figcaption>Node details panel with exploration options</figcaption>
 </figure>
 

docs/3-view-modified/lineage.md docs/3-visualized-change/lineage.mddocs/3-view-modified/lineage.md renamed to docs/3-visualized-change/lineage.md

@@ -0,0 +1,112 @@
+---
+title: Multi-Models 
+---
+
+
+## Multi-Models Selection
+
+Multiple models can be selected in the Lineage DAG. This enables actions to be performed on multiple models at the same time such as Row Count Diff, or Value Diff.
+
+### Select Models Individually
+
+To select multiple models individually, click the checkbox on the models you wish to select.
+
+<figure markdown>
+  ![Select multiple models individually](../assets/images/3-visualized-change/multi-node-selection.gif){: .shadow}
+  <figcaption>Select multiple models individually</figcaption>
+</figure>
+
+### Select Parent or Child models
+
+To select a node and all of its parents or children:
+
+1. Click the checkbox on the node.
+2. Right-click the node.
+3. Click to select either parent or child models.
+
+<figure markdown>
+  ![Select a node and its parents or children](../assets/images/3-visualized-change/select-node-children.gif){: .shadow}
+  <figcaption>Select a node and its parents or children</figcaption>
+</figure>
+
+### Perform actions on multiple models
+
+After selecting the desired models, use the Actions menu at the top right of the screen to perform diffs or add checks.
+
+<figure markdown>
+  ![Perform actions on multiple models](../assets/images/3-visualized-change/actions-menu.png){: .shadow}
+  <figcaption>Perform actions on multiple models</figcaption>
+</figure>
+
+### Example - Row Count Diff
+
+An example of selecting multiple models to perform a multi-node row count diff:
+
+<figure markdown>
+  ![Perform a Row Count Diff on multiple models](../assets/images/3-visualized-change/multi-node-row-count-diff.gif){: .shadow}
+  <figcaption>Perform a Row Count Diff on multiple models</figcaption>
+</figure>
+
+### Example - Value Diff
+
+An example of selecting multiple models to perform a multi-node Value Diff:
+
+<figure markdown>
+  ![Perform a Value Diff on multiple models](../assets/images/3-visualized-change/multi-node-value-diff.gif){: .shadow}
+  <figcaption>Perform a Value Diff on multiple models</figcaption>
+</figure>
+
+
+### Schema and Lineage Diff
+
+From the Lineage DAG, click the Actions dropdown menu and click Lineage Diff or Schema Diff from the Add to Checklist section. This will add:
+
+- Lineage Diff: The current Lineage view, dependent on your <a href="#select-models">model selection</a> options.
+- Schema Diff: A diff of all models if none are selected, or specific <a href="#multi-node-selection">selected models</a>.
+
+<figure markdown>
+  ![Add a Lineage Diff Check or Schema Check via the Actions dropdown menu](../assets/images/3-visualized-change/actions-dropdown.png){: .shadow}
+  <figcaption>Add a Lineage Diff Check or Schema Check via the Actions dropdown menu</figcaption>
+</figure>
+
+
+
+Recce supports dbt [node selection](https://docs.getdbt.com/reference/node-selection/syntax) in the [lineage diff](./lineage.md#lineage-diff). This enables you to target specific resources with data checks by selecting or excluding models.
+
+## Supported syntax and methods
+
+Since Recce uses dbt's built-in node selector, it supports most of the selecting methods. Here are some examples:
+
+- Select a node: `my_model`
+- select by tag: `tag:nightly`
+- Select by wildcard: `customer*`
+- Select by graph operators:  `my_model+`, `+my_model`, `+my_model`, `1+my_model+`
+- Select by union: `model1 model2`
+- Select by intersection: `stg_invoices+,stg_accounts+`
+- Select by state: `state:modified`, `state:modified+`
+
+
+### Use `state` method
+
+In dbt, you need to specify the `--state` option in the CLI. In Recce, we use the base environment as the state, allowing you to use the selector on the fly.
+
+
+### Removed models
+Another difference is that in dbt, you cannot select removed models. However, in Recce, you can select removed models and also find them using the graph operator. This is a notable distinction from dbt's node selection capabilities.
+
+
+## Supported Diff
+
+In addition to lineage diff, other types of diff also support node selection. You can find these features in the **...** button in the top right corner. Currently supported diffs include:
+
+- Lineage diff
+- Row count diff
+- Schema diff
+
+![](../assets/images/3-visualized-change/node-selection.png){: .shadow}
+
+## Limitation
+
+- ["result" method](https://docs.getdbt.com/reference/node-selection/syntax#the-result-status) not supported
+- ["source_status" method](https://docs.getdbt.com/reference/node-selection/syntax#the-source_status-status) not supported.
+- [YAML selectors](https://docs.getdbt.com/reference/node-selection/yaml-selectors) not supported.