feat(docs): update documentation for unified pattern architecture

Author: rstrahan

CLAUDE.md

@@ -29,7 +29,7 @@ python3 publish.py idp-1234567890 idp us-east-1 --verbose
 The build process:
 - Checks system dependencies (AWS CLI, SAM CLI, Docker, Python 3.12+, Node.js 22.12+)
 - Builds CloudFormation templates and assets using SAM
-- Pattern-2 functions are built as container images; Pattern-1 and Pattern-3 use ZIP-based Lambdas
+- All pattern functions are built within the unified pattern directory
 - Uploads artifacts to S3 bucket named `<cfn_bucket_basename>-<region>`
 
 ### Code Quality & Linting
@@ -106,7 +106,7 @@ idp-cli deploy \
 idp-cli deploy \
     --stack-name my-idp-stack \
     --pattern pattern-2 \
-    --custom-config ./config_library/pattern-2/bank-statement-sample/config.yaml \
+    --custom-config ./config_library/unified/bank-statement-sample/config.yaml \
     --wait
 
 # Process documents in batch
@@ -125,7 +125,7 @@ idp-cli download-results \
 ### Local Lambda Testing
 
 ```bash
-cd patterns/pattern-2/
+cd patterns/unified/
 sam build
 sam local invoke OCRFunction -e ../../testing/OCRFunction-event.json --env-vars ../../testing/env.json
 ```
@@ -153,30 +153,26 @@ The solution uses a modular architecture with the main template (`template.yaml`
 - Authentication (Cognito User Pool, Identity Pool)
 - AppSync GraphQL API (for UI-backend communication)
 
-**Pattern Stacks** (`patterns/pattern-*/template.yaml`) - Pattern-specific resources:
-- Step Functions State Machine
-- Pattern-specific Lambda Functions (OCR, Classification, Extraction)
-- Pattern-specific CloudWatch Dashboard
-- Model Endpoints and Configurations
+**Unified Pattern Stack** (`patterns/unified/template.yaml`) - Processing resources:
+- Step Functions State Machine (BDA branch + Pipeline branch + shared tail)
+- Lambda Functions (OCR, Classification, Extraction, Assessment, Summarization, Evaluation, etc.)
+- CloudWatch Dashboard
 
-### Processing Patterns
+### Processing Modes
 
-1. **Pattern 1: Bedrock Data Automation (BDA)**
+The unified architecture supports two processing modes, controlled by the `use_bda` configuration flag:
+
+1. **BDA Mode** (formerly Pattern 1)
    - Uses AWS Bedrock Data Automation for end-to-end processing
    - Handles packet or media documents with integrated OCR, classification, and extraction
-   - Location: `patterns/pattern-1/`
 
-2. **Pattern 2: Textract + Bedrock**
+2. **Pipeline Mode** (formerly Pattern 2)
    - OCR with Amazon Textract
    - Classification with Bedrock (page-level or holistic)
    - Extraction with Bedrock
    - Supports few-shot examples
-   - Location: `patterns/pattern-2/`
 
-3. **Pattern 3: Textract + UDOP + Bedrock**
-   - OCR with Amazon Textract
-   - Classification with UDOP model on SageMaker
-   - Extraction with Bedrock
+> **Note**: The separate `patterns/pattern-1/`, `patterns/pattern-2/`, and `patterns/pattern-3/` directories have been removed. All processing is now in `patterns/unified/`. See [pattern-1.md](docs/pattern-1.md) and [pattern-2.md](docs/pattern-2.md) for historical reference.
 
 ### Document Processing Flow
 

docs/assessment-bounding-boxes.md

@@ -20,7 +20,7 @@ The Assessment Service now supports **optional bounding box extraction** as part
 ### Core Capabilities
 
 - **Optional Feature**: Disabled by default, enabled via configuration
-- **UI Compatible**: Outputs geometry format compatible with existing pattern-1 UI
+- **UI Compatible**: Outputs geometry format compatible with existing BDA mode UI
 - **Multi-page Support**: Handles bounding boxes across multiple document pages
 - **Error Resilient**: Gracefully handles invalid or incomplete bounding box data
 - **Coordinate Normalization**: Converts from 0-1000 scale to 0-1 normalized coordinates
@@ -325,7 +325,7 @@ if explainability_info:
 
 ## Integration with UI
 
-The geometry format is fully compatible with the existing pattern-1 UI:
+The geometry format is fully compatible with the existing BDA mode UI:
 
 - **Coordinate System**: Normalized 0-1 coordinates
 - **Bounding Box Format**: `{top, left, width, height}`

docs/classification.md

@@ -172,7 +172,7 @@ The boundary detection is automatically included in the classification results.
 - Identifies distinct document segments within multi-page documents
 - Determines document type for each segment
 - Better suited for multi-document packets where context spans multiple pages
-- Deployed when you select the default pattern-2 configuration during stack deployment or update
+- Deployed when you select the default pipeline mode configuration during stack deployment or update
 
 The default configuration in `config_library/unified/default/config.yaml` implements this approach with a task prompt that instructs the model to:
 

lib/idp_common_pkg/idp_common/classification/README.md

@@ -604,14 +604,14 @@ classes:
               "sender_address": "206 Maple Street P.O. Box 1056 Murray Kentucky 42071-1056",
               "recipient_name": "The Honorable Wendell H. Ford",
               # ... other expected attributes
-        imagePath: "config_library/pattern-2/few_shot_example/example-images/letter1.jpg"
+        imagePath: "config_library/unified/few_shot_example/example-images/letter1.jpg"
       - classPrompt: "This is an example of the class 'letter'" 
         name: "Letter2"
         attributesPrompt: |
           expected attributes are:
               "sender_name": "William H. W. Anderson",
               # ... other expected attributes
-        imagePath: "config_library/pattern-2/few_shot_example/example-images/letter2.png"
+        imagePath: "config_library/unified/few_shot_example/example-images/letter2.png"
 ```
 
 ### Configuration Parameters
@@ -629,12 +629,12 @@ The `imagePath` field now supports multiple formats for maximum flexibility:
 
 **Single Image File (Original functionality)**:
 ```yaml
-imagePath: "config_library/pattern-2/few_shot_example/example-images/letter1.jpg"
+imagePath: "config_library/unified/few_shot_example/example-images/letter1.jpg"
 ```
 
 **Local Directory with Multiple Images (New)**:
 ```yaml
-imagePath: "config_library/pattern-2/few_shot_example/example-images/"
+imagePath: "config_library/unified/few_shot_example/example-images/"
 ```
 
 **S3 Prefix with Multiple Images (New)**:
@@ -767,7 +767,7 @@ classes:
              "to_address": "jane.smith@client.com", 
              "subject": "FW: Meeting Notes 4/20",
              "date_sent": "04/18/2024"
-        imagePath: "config_library/pattern-2/few_shot_example/example-images/email1.jpg"
+        imagePath: "config_library/unified/few_shot_example/example-images/email1.jpg"
 
 classification:
   task_prompt: |

lib/idp_common_pkg/idp_common/extraction/README.md

@@ -156,7 +156,7 @@ classes:
               "signature": "Will E. Clark",
               "cc": null,
               "reference_number": "TNJB 0008497"
-        imagePath: "config_library/pattern-2/few_shot_example/example-images/letter1.jpg"
+        imagePath: "config_library/unified/few_shot_example/example-images/letter1.jpg"
       - classPrompt: "This is an example of the class 'letter'"
         name: "Letter2"
         attributesPrompt: |
@@ -171,7 +171,7 @@ classes:
               "signature": "Bill",
               "cc": null,
               "reference_number": null
-        imagePath: "config_library/pattern-2/few_shot_example/example-images/letter2.png"
+        imagePath: "config_library/unified/few_shot_example/example-images/letter2.png"
 ```
 
 ### Configuration Parameters
@@ -190,13 +190,13 @@ The `imagePath` field now supports multiple formats for maximum flexibility:
 **Single Image File (Original functionality)**:
 
 ```yaml
-imagePath: "config_library/pattern-2/few_shot_example/example-images/letter1.jpg"
+imagePath: "config_library/unified/few_shot_example/example-images/letter1.jpg"
 ```
 
 **Local Directory with Multiple Images (New)**:
 
 ```yaml
-imagePath: "config_library/pattern-2/few_shot_example/example-images/"
+imagePath: "config_library/unified/few_shot_example/example-images/"
 ```
 
 **S3 Prefix with Multiple Images (New)**:
@@ -427,7 +427,7 @@ classes:
              "priority": null,
              "thread_id": null,
              "message_id": null
-        imagePath: "config_library/pattern-2/few_shot_example/example-images/email1.jpg"
+        imagePath: "config_library/unified/few_shot_example/example-images/email1.jpg"
 
 extraction:
   task_prompt: |
@@ -469,7 +469,7 @@ from idp_common.extraction.service import ExtractionService
 import yaml
 
 # Load configuration with examples
-with open('config_library/pattern-2/few_shot_example/config.yaml', 'r') as f:
+with open('config_library/unified/few_shot_example/config.yaml', 'r') as f:
     config = yaml.safe_load(f)
 
 # Initialize service

lib/idp_common_pkg/idp_common/rule_validation/README.md

@@ -565,7 +565,7 @@ from idp_common.rule_validation import RuleValidationService
 from idp_common import s3
 
 # Load configuration
-config_path = "../../config_library/pattern-2/rule-validation/config.yaml"
+config_path = "../../config_library/unified/rule-validation/config.yaml"
 with open(config_path, 'r') as f:
     config = yaml.safe_load(f)