Chapter 6: Business Domain Patterns

Having established the complete educational domain implementation in Chapter 5, we now examine how the same patterns manifest in other verticals. This comparative analysis demonstrates that while domain content differs, underlying structural patterns recur with remarkable consistency.

This chapter analyzes four business domains: 1. Legal Services - Complex relationships, high precision requirements 2. Real Estate - Visual-heavy, marketing-focused, transaction-driven 3. Retail & E-commerce - High volume, hierarchical categories 4. Human Resources - Personnel management, compliance-heavy

For each domain, we provide: - Domain context and characteristics - Core entity model (lighter than Chapter 5, but comprehensive) - Key document types mapped to patterns - Pattern distribution analysis - Domain-specific considerations

Goal: Show that the framework transcends education and applies universally to document-intensive domains.

6.1 Legal Services Domain

6.1.1 Domain Context

Legal practices (law firms, corporate legal departments, solo practitioners) are among the most document-intensive domains. Documents are the product - legal services manifest as written work product.

Characteristics: - High precision requirements: Errors can have serious legal/financial consequences - Complex relationships: Cases involve multiple parties, attorneys, documents, deadlines - Performative documents: Contracts, pleadings, motions create legal reality - Strict formatting: Court rules mandate specific formats - Time-based billing: Documents often tied to time entries - Confidentiality: Attorney-client privilege, work product doctrine - Regulatory compliance: State bar rules, court rules, ethics requirements

Document Intensity: Very High - Large firms: 50,000+ documents per year - Solo practitioners: 500-2,000 documents per year - Every client matter generates dozens of documents

Pain Points: - Inconsistent document formatting across attorneys - Time-consuming document assembly - Risk of missing required provisions - Difficulty tracking document versions - Calculating billable time for document preparation

6.1.2 Core Entity Model

Primary Entities:

Matter/Case
case_id, case_number, title
practice_area (litigation, corporate, estate, real_estate, family)
status (open, pending, closed)
open_date, close_date
jurisdiction, court
case_value, fee_arrangement
Party
party_id, name, type (client, opposing_party, witness, expert)
role_in_matter (plaintiff, defendant, third_party)
contact_information
relationship_to_client
Attorney
attorney_id, bar_number, name
practice_areas, hourly_rate
status (partner, associate, paralegal, contract)
Document (Meta-entity tracking documents themselves)
document_id, title, type
matter_id (which case)
author_id (which attorney)
created_date, version
filing_status (draft, filed, served)
confidentiality_level
Time Entry
entry_id, attorney_id, matter_id
date, hours, hourly_rate
description, task_code
billable, billed, paid
Deadline
deadline_id, matter_id
due_date, description
responsible_attorney_id
priority, status

Key Relationships: - Matter → Party (M:N - multiple parties per case) - Matter → Attorney (M:N - multiple attorneys per case) - Matter → Document (1:N - case has many documents) - Matter → Time Entry (1:N - billing) - Attorney → Time Entry (1:N - who worked) - Document → Time Entry (1:N - time spent on document)

6.1.3 Key Document Types

1. Engagement Letter (Atomic Pattern) - Purpose: Contract between attorney and client defining scope, fees, responsibilities - Frequency: Once per new client/matter - Data: Client, Attorney, Matter, Fee terms - Communicative Function: Performative (creates attorney-client relationship) - Precision: High (legally binding contract)

2. Legal Invoice (Master-Detail Pattern) - Purpose: Bill client for services rendered - Frequency: Monthly per matter - Data: - Master: Matter, Client, Attorney firm info, Billing period - Detail: Time entries with attorney, date, description, hours, rate, amount - Calculations: - Subtotal by attorney - Subtotal by task type - Total fees - Expenses - Grand total - Communicative Function: Performative (creates payment obligation) + Declarative (reports work done) - Compliance: State bar rules often mandate specific invoice content

3. Pleading/Motion (Atomic with standardized format) - Purpose: File documents with court - Frequency: Variable, 5-50 per case depending on practice area - Data: Matter, Parties, Court, Attorney, Legal arguments - Structure: - Caption (Court, case number, parties, document title) - Body (legal arguments, facts, procedural history) - Prayer for relief - Signature block with bar number - Certificate of service - Communicative Function: Performative (asks court to take action) + Directive (tells court what to do) - Compliance: Must follow court formatting rules exactly (font, margins, line spacing, page limits)

4. Contract (Hierarchical Pattern) - Purpose: Create binding agreement between parties - Frequency: Variable, core document in transactional practice - Structure: - Preamble (parties, effective date, recitals) - Article I: Definitions - Article II: [Substantive provisions] - Article III: Representations and Warranties - Article IV: Covenants - Article V: Conditions - Article VI: Term and Termination - Article VII: Indemnification - Article VIII: Miscellaneous - Signature blocks - Exhibits and Schedules - Data: Parties, Terms, Dates, Amounts, Conditions - Communicative Function: Performative (creates legal obligations) - Precision: Extremely high (ambiguity creates disputes)

5. Document Production List (Directory Pattern) - Purpose: List documents produced in discovery - Frequency: Per discovery request in litigation - Data: Documents with metadata (bates numbers, date, author, subject, privilege claims) - Structure: Table format | Bates No. | Date | Author | Recipient | Subject | Description | Privilege | - Communicative Function: Declarative (what was produced) - Compliance: Federal Rules of Civil Procedure requirements

6. Time and Billing Report (Matrix Pattern) - Purpose: Internal tracking of attorney time by matter/client - Frequency: Weekly/Monthly - Structure: Attorneys (rows) × Matters (columns) = Hours - Data: Time entries aggregated - Communicative Function: Declarative (internal reporting)

7. Exhibit List (Directory Pattern) - Purpose: List exhibits to be used at trial - Frequency: Per trial - Data: Exhibit number, description, date, offered_by, admitted status - Structure: Numbered list or table - Communicative Function: Declarative + Directive (court procedures)

8. Demand Letter (Atomic Pattern) - Purpose: Formal demand for payment or action before litigation - Frequency: Variable - Data: Parties, Claims, Damages, Deadline for response - Structure: Letter format with facts, law, demand - Communicative Function: Commissive (threatens legal action if demand not met)

6.1.4 Pattern Distribution

Legal Services Pattern Distribution:
- Master-Detail: 35% (Invoices, time reports, document lists)
- Atomic: 30% (Pleadings, letters, contracts as single instances)
- Hierarchical: 20% (Contracts with articles/sections, briefs with arguments)
- Directory: 10% (Document indices, exhibit lists, witness lists)
- Matrix: 5% (Time tracking, case comparisons)
- Narrative: 0% (Not used in legal)

6.1.5 Domain-Specific Considerations

Precision is Paramount: - Template language must be legally accurate - Cannot use "approximate" or "similar" calculations - Every clause in contracts matters - Version control critical (which draft was sent?)

Confidentiality: - Attorney-client privilege protections - Work product doctrine - Secure document generation and storage - Access controls (who can see what)

Court Compliance: - Strict formatting rules (font: Courier 12pt, margins: 1", line spacing: double) - Page limits (briefs limited to 15/25/50 pages) - Filing deadlines (miss by 1 minute = case dismissed) - Electronic filing requirements (PDF/A format, specific naming)

Time Tracking Integration: - Document creation time should be captured - Billable vs. non-billable distinction - Time entries linked to documents - Client billing transparency

Approval Workflows: - Senior attorney review before filing - Client review for certain documents - Conflicts checks before new matters - Multiple signature requirements

Unique Patterns: - Redline Comparison: Show changes between versions (track changes) - Cross-references: Contracts reference exhibits, briefs cite cases - Boilerplate with Variations: Standard clauses with customization points

6.2 Real Estate Domain

6.2.1 Domain Context

Real estate professionals (agents, brokers, property managers) create visually-rich, marketing-focused documents to sell or lease properties.

Characteristics: - Visual-heavy: Photos essential, appearance matters - Marketing focus: Documents persuade and inform buyers/sellers - Transaction-driven: Documents support sales process - Time-sensitive: Market conditions change rapidly - Geographic: Location is primary attribute - Data integration: MLS (Multiple Listing Service) data - Regulatory: Disclosure requirements vary by state/locality

Document Intensity: High - Active agent: 200-500 documents per year - High-volume team: 2,000+ documents per year

Pain Points: - Creating professional-looking marketing materials - Keeping property data current - Comparing properties (comps) - Generating required disclosures - Personalizing for each client

6.2.2 Core Entity Model

Primary Entities:

Property
property_id, mls_number
address (street, city, state, zip)
type (single_family, condo, multi_family, commercial)
beds, baths, sqft, lot_size, year_built
list_price, status (active, pending, sold, withdrawn)
list_date, sold_date, sold_price
features (pool, garage, fireplace, etc.)
photos[] (multiple images)
Agent
agent_id, license_number, name
brokerage, contact_info, photo
specialties, certifications
production_stats
Client
client_id, name, contact
type (buyer, seller, both)
preferences (price_range, locations, must_haves)
pre_qualified_amount
Listing
listing_id, property_id, agent_id
listing_type (exclusive_right, exclusive_agency, open)
start_date, end_date
commission_rate
marketing_notes
Showing
showing_id, property_id, client_id, agent_id
date_time, duration
feedback, interest_level
Transaction
transaction_id, property_id
buyer_agent_id, seller_agent_id
buyer_id, seller_id
offer_date, offer_price
contract_date, close_date
contingencies, status
Comparable Sale (Comp)
comp_id, property_id (the sold property)
reference_property_id (what it's being compared to)
sale_date, sale_price
adjustments (age, condition, features)
adjusted_price

Key Relationships: - Property → Listing (1:N over time) - Listing → Agent (N:1 - agent lists many properties) - Property → Showing (1:N - many showings per property) - Property → Transaction (1:1 per sale) - Property → Comparable (1:N - compared to many similar properties)

6.2.3 Key Document Types

1. Property Listing Flyer (Atomic Pattern - Visually Rich) - Purpose: Marketing material to attract buyers - Frequency: Per active listing - Data: Property (all attributes), Photos, Agent contact - Layout: - Hero photo (full width top) - Property address and price (prominent) - Key stats (beds, baths, sqft) with icons - Photo gallery (6-12 additional photos) - Features list (bullet points) - Property description (narrative) - Location map - Agent photo and contact info - Design: Professional, eye-catching, branded - Communicative Function: Declarative + Expressive (sells the property)

2. Comparative Market Analysis (CMA) (Master-Detail Pattern) - Purpose: Help seller price property by showing comparable sales - Frequency: Per listing consultation - Data: - Master: Subject property - Detail: 3-10 comparable sales with adjustments - Structure: - Subject property summary - Comparable properties table: | Address | Beds/Baths | SqFt | Sale Date | Sale Price | Adjustments | Adj. Price | - Analysis and pricing recommendation - Calculations: - Price per square foot - Adjustments for differences (condition, features, location) - Suggested listing price range - Communicative Function: Declarative (market data) + Commissive (recommends price)

3. Purchase Agreement (Hierarchical Pattern - Legal Document) - Purpose: Contract between buyer and seller - Frequency: Per offer - Structure: Similar to legal contracts but real-estate specific - Parties identification - Property description (legal and common) - Purchase price and payment terms - Earnest money deposit - Contingencies (inspection, financing, appraisal) - Closing date - Inclusions and exclusions - Disclosures - Signatures - Data: Property, Buyer, Seller, Agents, Terms - Communicative Function: Performative (creates binding contract) - Compliance: State-specific forms often required

4. Disclosure Documents (Atomic Pattern - Regulatory) - Purpose: Legally required disclosures about property condition - Frequency: Per sale - Types: - Seller's Property Disclosure - Lead-Based Paint Disclosure - Flood Zone Disclosure - HOA Disclosure - Data: Property, Known defects, Environmental hazards - Communicative Function: Declarative (inform buyer) + Protective (legal compliance)

5. Open House Sign-In Sheet (Directory Pattern) - Purpose: Capture visitor information for follow-up - Frequency: Per open house event - Data: Name, Phone, Email, Agent (if have one), Interest level - Structure: Simple form/table - Communicative Function: Declarative (who attended)

6. Agent Marketing Package (Narrative Flow Pattern) - Purpose: Agent presents themselves to potential clients - Frequency: Per agent (updated periodically) - Content: - Agent bio and photo - Market statistics - Recent sales (success stories) - Client testimonials - Service offerings - Contact information - Layout: Magazine-style, multi-page - Communicative Function: Expressive (builds trust) + Declarative (shows credentials)

7. Listing Presentation (Narrative Flow + Master-Detail) - Purpose: Agent pitches services to potential seller - Frequency: Per listing appointment - Content: - Agent credentials - Marketing plan - CMA (comparable sales) - Suggested pricing - Commission structure - Timeline - Communicative Function: Commissive (proposes services) + Declarative (shows market data)

8. Neighborhood Guide (Narrative Flow + Directory) - Purpose: Showcase neighborhood features to buyers - Frequency: Per neighborhood where agent is active - Content: - Neighborhood overview - Schools (with ratings) - Parks and recreation - Shopping and dining - Demographics - Property listings in area - Layout: Magazine-style with photos - Communicative Function: Declarative (informs) + Expressive (sells lifestyle)

6.2.4 Pattern Distribution

Real Estate Pattern Distribution:
- Atomic: 40% (Listing flyers, disclosures, individual contracts)
- Narrative Flow: 25% (Marketing materials, presentations, guides)
- Master-Detail: 20% (CMAs, transaction summaries, agent activity reports)
- Directory: 10% (Property lists, open house sheets, agent rosters)
- Matrix: 5% (Showing schedules, property comparisons)
- Hierarchical: 0% (Not typically needed)

6.2.5 Domain-Specific Considerations

Visual Quality Critical: - Professional photography essential - Layout and design matter (this is marketing) - Templates must handle varying numbers of photos - Print quality important (high-resolution images)

Data Freshness: - Property status changes daily (sold, under contract, price reduced) - Must pull current MLS data - Regenerate marketing materials when data changes

Geographic Focus: - Location is primary attribute - Maps essential - Neighborhood data important - School district boundaries matter

Mobile-First: - Buyers browse on phones - Responsive design for digital flyers - QR codes linking to virtual tours

Compliance Varies by Location: - Disclosure requirements by state - Fair housing laws (what can/can't be said) - MLS rules (how to display data) - Brokerage policies (branding requirements)

Integration Needs: - MLS data import - Photo management (high-resolution, metadata) - E-signature for contracts - CRM for client management

6.3 Retail & E-commerce Domain

6.3.1 Domain Context

Retailers (online and brick-and-mortar) create high-volume documents for products, promotions, transactions, and inventory.

Characteristics: - High volume: Thousands to millions of SKUs - Hierarchical: Deep category structures - Seasonal: Catalogs and promotions tied to seasons - Transaction-heavy: Invoices, receipts, orders daily - Price-sensitive: Pricing changes frequently - Visual: Product photos essential - Multi-channel: Web, print, in-store materials

Document Intensity: Very High - Small retailer: 5,000+ documents per year - Mid-size: 50,000+ documents per year - Enterprise: Millions of documents per year

Pain Points: - Keeping product information current - Creating catalogs with thousands of products - Consistent pricing across channels - Seasonal catalog production (tight deadlines) - Personalizing promotions

6.3.2 Core Entity Model

Primary Entities:

Product
product_id, sku, upc
name, description (short and long)
category_id, subcategory_id, brand_id
price_retail, price_wholesale, price_sale
cost, margin_percentage
dimensions, weight
colors[], sizes[]
images[] (multiple product photos)
in_stock, quantity_on_hand
discontinued, featured, new_arrival
Category
category_id, name, parent_category_id
description, sort_order
(Hierarchical: Clothing → Women's → Tops → Blouses)
Brand
brand_id, name, logo
description, website
Customer
customer_id, name, email
shipping_address, billing_address
loyalty_tier (regular, silver, gold)
purchase_history_value
preferences
Order
order_id, order_date
customer_id
status (pending, processing, shipped, delivered, cancelled)
subtotal, tax, shipping, discount, total
payment_method, payment_status
Order_Line_Item
line_item_id, order_id, product_id
quantity, unit_price, line_total
(Master-Detail relationship)
Promotion
promotion_id, name, code
discount_type (percentage, fixed_amount, bogo)
discount_value
start_date, end_date
applies_to (specific products, categories, all)
minimum_purchase

Key Relationships: - Product → Category (N:1 - product in one category) - Category → Category (1:N - hierarchical categories) - Product → Brand (N:1) - Order → Customer (N:1 - customer has many orders) - Order → Order_Line_Item (1:N - order has many items) - Order_Line_Item → Product (N:1)

6.3.3 Key Document Types

1. Product Catalog (Hierarchical + Directory Pattern) - Purpose: Comprehensive listing of products for sale - Frequency: Seasonal (Spring, Summer, Fall, Holiday) - Scale: 100-10,000+ products per catalog - Structure: - Hierarchical organization by category - Within each category: Directory of products - Data: Products with photos, descriptions, prices - Layout: - Table of contents (categories) - Category pages with products - Product grids (2-6 per page) - Each product: Photo, name, SKU, price, brief description - Communicative Function: Reference + Marketing - Challenge: High volume, must generate efficiently

2. Price List (Directory or Matrix Pattern) - Purpose: List current prices for all products - Frequency: Updated when prices change (monthly/quarterly) - Data: Products with SKU, name, price (retail, wholesale, sale) - Variations: - Simple: SKU, Name, Price (table) - Tiered: Showing volume discounts (matrix: quantity × price) - Customer-specific: Personalized pricing - Communicative Function: Declarative (current pricing)

3. Invoice/Receipt (Master-Detail Pattern) - Purpose: Bill customer for purchase - Frequency: Per transaction (could be thousands daily) - Data: - Master: Order, Customer, Date, Total - Detail: Line items (product, qty, price, line total) - Structure: Standard invoice format - Header: Company info, customer info, order #, date - Line items table - Subtotal, tax, shipping, discounts, total - Payment info, terms - Communicative Function: Performative (creates payment obligation) + Declarative (receipt of goods)

4. Product Specification Sheet (Atomic Pattern) - Purpose: Detailed information about single product - Frequency: Per product - Data: All product attributes plus technical specs - Layout: - Product photo(s) - Name and SKU - Description (detailed) - Specifications (dimensions, materials, features) - Care instructions - Related products - Use Cases: Customer inquiries, sales staff reference, B2B sales

5. Promotional Flyer (Narrative Flow Pattern) - Purpose: Advertise sale or promotion - Frequency: Weekly/monthly - Data: Featured products, sale prices, promotion details - Layout: Eye-catching design, large product photos, prominent pricing - Communicative Function: Expressive (creates urgency) + Declarative (what's on sale)

6. Inventory Report (Directory or Matrix Pattern) - Purpose: Track stock levels - Frequency: Daily/weekly - Data: Products with quantity on hand, reorder levels, value - Variations: - By location: Products × Warehouses/Stores - By category: Grouped by product category - Low stock alert: Filtering products below reorder point - Communicative Function: Declarative (internal reporting)

7. Purchase Order (to Supplier) (Master-Detail Pattern) - Purpose: Order products from supplier - Frequency: As needed - Data: - Master: Supplier, PO number, date, delivery location - Detail: Products ordered (SKU, description, qty, unit cost, line total) - Communicative Function: Commissive (commits to purchase) + Directive (supplier should ship)

8. Packing Slip (Master-Detail Pattern) - Purpose: Accompany shipment to customer - Frequency: Per shipment - Data: Order info, line items (no prices), shipping info - Communicative Function: Declarative (what's in the box)

6.3.4 Pattern Distribution

Retail/E-commerce Pattern Distribution:
- Master-Detail: 40% (Invoices, orders, purchase orders, packing slips)
- Directory: 30% (Product lists, inventory reports, price lists)
- Hierarchical: 15% (Catalogs with categories)
- Atomic: 10% (Individual product sheets, customer invoices)
- Narrative Flow: 5% (Promotional materials, flyers)
- Matrix: 0% (Occasionally for comparisons)

6.3.5 Domain-Specific Considerations

Volume and Performance: - Must generate hundreds or thousands of documents quickly - Catalog production: 5,000 products × 4 catalogs/year = 20,000 pages - Daily invoices: Could be thousands - Need efficient batch processing

Hierarchical Categories: - Products organized in nested categories - Catalog navigation reflects hierarchy - Filtering and faceted search - Breadcrumbs (Home > Clothing > Women's > Tops > Blouses)

Pricing Complexity: - Multiple price levels (retail, wholesale, member) - Sale prices with start/end dates - Volume discounts - Promotional codes - Dynamic pricing (time-based, inventory-based)

Multi-Channel Consistency: - Same product info for web, print, in-store - Synchronized inventory - Consistent branding - Mobile-friendly designs

Seasonal Production: - Tight deadlines for catalog publication - Must coordinate with marketing campaigns - Photography and content creation at scale

Integration Needs: - E-commerce platform (Shopify, WooCommerce) - Inventory management system - Accounting software (QuickBooks) - Shipping systems (FedEx, UPS APIs)

6.4 Human Resources Domain

6.4.1 Domain Context

HR departments manage personnel across the employee lifecycle: recruiting, onboarding, development, compensation, and offboarding.

Characteristics: - Personnel-centric: Everything revolves around employees - Hierarchical organizations: Departments, teams, reporting structures - Temporal: Employee data changes over time (promotions, transfers) - Confidential: Sensitive personal information, salaries, reviews - Compliance-heavy: Labor laws, EEO, benefits regulations - Recurring processes: Annual reviews, benefits enrollment - Lifecycle-driven: Hire → Onboard → Develop → Review → (Promote/Transfer/Depart)

Document Intensity: High - Small company (50 employees): 500-1,000 documents per year - Mid-size (500 employees): 5,000-10,000 documents per year - Enterprise (5,000+): 50,000+ documents per year

Pain Points: - Personalizing standard templates (offer letters, reviews) - Maintaining consistency across managers - Ensuring compliance (required content) - Tracking document versions - Coordinating multi-person processes (reviews, approvals)

6.4.2 Core Entity Model

Primary Entities:

Employee
employee_id, name, email
hire_date, start_date
job_title, department_id, location
manager_id (self-referential foreign key)
employment_type (full_time, part_time, contract)
status (active, on_leave, terminated)
salary, pay_grade
photo, bio
Department
department_id, name
parent_department_id (hierarchical)
head_of_department_id (FK to Employee)
Position/Job Title
position_id, title
job_description, responsibilities
required_skills, preferred_skills
pay_grade_min, pay_grade_max
department_id
Review/Performance Evaluation
review_id, employee_id, reviewer_id
review_period (start_date, end_date)
overall_rating
goal_achievement, competency_ratings
strengths, areas_for_improvement
development_plan
status (in_progress, completed, acknowledged)
Goal
goal_id, employee_id, review_id
description, measurement_criteria
due_date, completion_date
status (not_started, in_progress, completed)
Time Off Request
request_id, employee_id
type (vacation, sick, personal, other)
start_date, end_date, days
status (pending, approved, denied)
approver_id
Training/Certification
training_id, employee_id
course_name, provider
completion_date, expiration_date
certificate_number

Key Relationships: - Employee → Manager (N:1 self-referential - reporting structure) - Employee → Department (N:1) - Department → Department (1:N hierarchical) - Employee → Review (1:N - multiple reviews over time) - Review → Goal (1:N - multiple goals per review) - Employee → Training (1:N - employee takes many courses)

6.4.3 Key Document Types

1. Offer Letter (Atomic Pattern) - Purpose: Formal job offer to candidate - Frequency: Per hire - Data: Candidate, Position, Salary, Start date, Benefits summary - Structure: Letter format - Greeting - Job offer (title, department, reporting relationship) - Compensation (salary, bonus, equity if applicable) - Benefits summary - Start date and location - Contingencies (background check, references) - Acceptance deadline - Signature lines - Communicative Function: Commissive (company commits to employment) + Performative (creates employment relationship when signed) - Compliance: Must comply with employment laws, EEO considerations

2. Employee Directory (Directory Pattern with Hierarchy) - Purpose: List all employees with contact info - Frequency: Updated monthly or as-needed - Data: Employees with name, photo, title, department, contact info - Variations: - Flat alphabetical: Simple list - By department: Grouped hierarchically - Organizational chart: Visual hierarchy - Communicative Function: Declarative (who works here) - Privacy: Some employees may opt out of directory

3. Performance Review (Master-Detail Pattern) - Purpose: Document employee performance and set goals - Frequency: Annual or bi-annual per employee - Data: - Master: Employee, Reviewer, Period, Overall rating - Detail: Multiple competency ratings, goals, comments - Structure: - Employee information - Review period - Performance ratings (by competency area) - Goal achievement (last period's goals) - New goals for next period - Overall assessment - Development plan - Signatures (employee, manager, HR) - Communicative Function: Declarative (performance assessment) + Commissive (commits to development) - Sensitive: Confidential, protected information

4. Organizational Chart (Hierarchical Pattern - Visual) - Purpose: Show reporting structure - Frequency: Updated quarterly or with org changes - Data: Employees with manager relationships - Structure: Tree diagram - CEO at top - Nested reporting relationships - Boxes with name, photo, title - Communicative Function: Declarative (org structure) - Variations: By department, by location, entire company

5. New Hire Packet (Collection of Atomic documents) - Purpose: Onboarding materials for new employees - Frequency: Per new hire - Contents: - Welcome letter - Offer letter (copy) - Benefits enrollment forms - Tax withholding (W-4, state) - Direct deposit form - Employee handbook acknowledgment - IT policy acknowledgment - Equipment list - First week schedule - Communicative Function: Directive (here's what you need to do) + Declarative (here's our policies)

6. Benefits Enrollment Guide (Narrative Flow + Directory) - Purpose: Explain benefits options for annual enrollment - Frequency: Annual - Content: - Benefits overview - Plan options (health, dental, vision, 401k) - Comparison tables - Costs and coverage levels - How to enroll - Important dates - Layout: Multi-page booklet style - Communicative Function: Directive (choose your benefits) + Declarative (here are the options)

7. Salary/Compensation Report (Directory or Matrix Pattern) - Purpose: Internal HR analysis of compensation - Frequency: Annual or as-needed - Data: Employees with salary, grade, department - Variations: - By department: List with statistics - By pay grade: Matrix showing distribution - Equity analysis: Checking for disparities - Communicative Function: Declarative (internal reporting) - Highly Sensitive: Strict access controls

8. Time Off Calendar (Matrix Pattern) - Purpose: Show who's out when - Frequency: Updated continuously - Structure: Employees (rows) × Dates (columns) = Vacation/Sick/Other - Data: Time off requests (approved) - Communicative Function: Declarative (planning tool)

9. Termination Letter (Atomic Pattern) - Purpose: Document end of employment - Frequency: Per departure (voluntary or involuntary) - Data: Employee, Last day, Reason (if voluntary), Severance (if any), Benefits continuation (COBRA) - Structure: Letter format - Communicative Function: Performative (ends employment) + Declarative (terms of departure) - Legal: Must be carefully worded, reviewed by legal

10. Training Certificate (Atomic Pattern) - Purpose: Certify completion of required training - Frequency: Per completion - Data: Employee, Course, Date, Instructor/Provider - Structure: Certificate format with signatures - Communicative Function: Performative (certifies completion) - Compliance: Some industries require specific training certifications

6.4.4 Pattern Distribution

Human Resources Pattern Distribution:
- Atomic: 40% (Offer letters, review forms, certificates, termination letters)
- Directory: 25% (Employee directories, compensation reports)
- Master-Detail: 20% (Performance reviews with goals, new hire packets)
- Hierarchical: 10% (Organizational charts, department structures)
- Matrix: 5% (Time off calendars, training matrices)
- Narrative Flow: 5% (Benefits guides, employee handbooks)

6.4.5 Domain-Specific Considerations

Confidentiality is Critical: - Salary information highly sensitive - Performance reviews are private - Medical information (HIPAA if health-related) - Access controls: Employees see own info, managers see direct reports, HR sees all

Compliance Requirements: - Equal Employment Opportunity (EEO) laws - Americans with Disabilities Act (ADA) - Fair Labor Standards Act (FLSA) - Family and Medical Leave Act (FMLA) - State-specific employment laws - International: GDPR for EU employees

Approval Workflows: - Offer letters: Manager → HR → Legal → Executive - Performance reviews: Manager writes → Employee reviews → HR archives - Time off: Employee requests → Manager approves - Terminations: Manager initiates → HR reviews → Legal reviews → Executive approves

Temporal Data: - Employees promoted → job title changes - Salary adjustments over time - Department transfers - Manager changes - Historical data must be preserved (former employees, past reviews)

Multi-Language: - Global companies need translations - Local compliance varies by country

Integration Needs: - HRIS (Human Resource Information System) - Payroll systems - Time tracking - Benefits administration - Background check services

6.5 Cross-Domain Pattern Analysis

Now that we've examined four diverse domains, let's compare patterns:

6.5.1 Pattern Frequency Comparison

Pattern          | Education | Legal | Real Estate | Retail | HR     | Average
──────────────────────────────────────────────────────────────────────────────
Atomic           | 30%      | 30%   | 40%         | 10%    | 40%    | 30%
Directory        | 40%      | 10%   | 10%         | 30%    | 25%    | 23%
Master-Detail    | 20%      | 35%   | 20%         | 40%    | 20%    | 27%
Hierarchical     | 0%       | 20%   | 0%          | 15%    | 10%    | 9%
Matrix           | 15%      | 5%    | 5%          | 0%     | 5%     | 6%
Narrative Flow   | 5%       | 0%    | 25%         | 5%     | 5%     | 8%

Observations:

Universal Patterns: Atomic, Directory, and Master-Detail appear in EVERY domain (together account for 80% of documents)
Domain Variations:
Legal: High Master-Detail (invoices, document lists) and Hierarchical (contracts)
Real Estate: High Narrative Flow (marketing materials) and Atomic (property flyers)
Retail: High Master-Detail (orders, invoices) and Directory (catalogs)
HR: High Atomic (individual letters) and Directory (employee lists)
Education: High Directory (rosters, lists)
Rare Patterns:
Matrix: Only common in education and HR (scheduling, tracking)
Narrative Flow: Only common in real estate (marketing focus)
Hierarchical: Only legal and retail use significantly

6.5.2 Common Document Types Across Domains

Identity & Membership (All domains need this): - Education: Student rosters - Legal: Attorney/client directories - Real Estate: Agent directories - Retail: Customer lists - HR: Employee directories

Transaction Documents (Almost universal): - Education: (less transactional) - Legal: Invoices with time entries - Real Estate: Purchase agreements - Retail: Invoices, receipts, orders - HR: Offer letters (creates employment "transaction")

Status & Progress (All domains track something): - Education: Report cards, progress reports - Legal: Case status reports, matter updates - Real Estate: Transaction pipelines, showing reports - Retail: Inventory reports, sales reports - HR: Performance reviews, goal tracking

Certificates & Credentials (Formal recognition): - Education: Completion certificates - Legal: Bar admissions, certifications - Real Estate: License certificates - Retail: Gift certificates, warranties - HR: Training certificates, awards

6.5.3 What Makes Domains Different

Despite shared patterns, domains have distinct characteristics:

Legal: - Precision paramount: No approximations, every word matters - Strict formatting: Court rules, bar requirements - High consequence: Errors can be catastrophic - Complex relationships: Cases involve many interconnected entities

Real Estate: - Visual quality critical: Marketing-driven, photos essential - Geographic focus: Location is everything - Time-sensitive: Market changes rapidly - Regulatory variation: Different rules by state/locality

Retail: - High volume: Thousands to millions of documents - Performance critical: Must generate fast at scale - Hierarchical categories: Deep product taxonomies - Price sensitivity: Prices change frequently

HR: - Confidentiality paramount: Sensitive personal information - Compliance-heavy: Many regulations to follow - Approval workflows: Multiple reviewers required - Temporal complexity: Employee data changes over time

6.5.4 Transfer Learning Opportunities

Insights from one domain can inform others:

Education → HR: - Report cards ≈ Performance reviews (both assess progress) - Student directories ≈ Employee directories (both list members) - Class schedules ≈ Team schedules (both allocate people to activities)

Legal → Real Estate: - Contracts in both domains (similar hierarchical structure) - Disclosure requirements (legal compliance) - Document version control (important in both)

Retail → Education: - Product catalogs ≈ Course catalogs (both hierarchical reference documents) - Inventory tracking ≈ Enrollment tracking (both monitor capacity)

HR → All Domains: - Time tracking appears in many contexts - Directories appear in every domain - Performance assessment patterns transferable

6.6 Chapter Summary

This chapter demonstrated that document patterns transcend domain boundaries:

Universal Patterns: Atomic, Directory, and Master-Detail appear in every domain we examined (80% of documents)

Domain-Specific Variations: While patterns recur, emphasis differs: - Legal emphasizes Master-Detail and Hierarchical (complex relationships, structured agreements) - Real Estate emphasizes Narrative Flow and Atomic (marketing-driven, visual) - Retail emphasizes Master-Detail and Directory (transaction-heavy, catalog-driven) - HR emphasizes Atomic and Directory (individual documents, personnel listings)

Common Meta-Patterns Validated: - Identity & Membership (directories in all domains) - Transaction & Exchange (invoices, agreements, orders) - Status & Progress (reports, reviews, tracking) - Authorization & Validation (certificates, credentials)

Transfer Learning: Understanding one domain helps with others. The frameworks from Chapters 1-4 apply universally.

Chapter 6: Business Domain Patterns

6.1 Legal Services Domain

6.1.1 Domain Context

6.1.2 Core Entity Model

6.1.3 Key Document Types

6.1.4 Pattern Distribution

6.1.5 Domain-Specific Considerations

6.2 Real Estate Domain

6.2.1 Domain Context

6.2.2 Core Entity Model

6.2.3 Key Document Types

6.2.4 Pattern Distribution

6.2.5 Domain-Specific Considerations

6.3 Retail & E-commerce Domain

6.3.1 Domain Context

6.3.2 Core Entity Model

6.3.3 Key Document Types

6.3.4 Pattern Distribution

6.3.5 Domain-Specific Considerations

6.4 Human Resources Domain

6.4.1 Domain Context

6.4.2 Core Entity Model

6.4.3 Key Document Types

6.4.4 Pattern Distribution

6.4.5 Domain-Specific Considerations

6.5 Cross-Domain Pattern Analysis

6.5.1 Pattern Frequency Comparison

6.5.2 Common Document Types Across Domains

6.5.3 What Makes Domains Different

6.5.4 Transfer Learning Opportunities

6.6 Chapter Summary

Further Reading