# FINAL SUMMARY - Direction: matrix-to-notes - Scope: Expense approval tool, early planning stage - Cells populated: 4/36 - Cells not established / empty: 32 - Rule conflicts flagged: none - Unclassified material: none # ZACHMAN MATRIX STATE | | WHAT | HOW | WHERE | WHO | WHEN | WHY | |---|---|---|---|---|---|---| | **SCOPE** | Expenses, approvals | NOT ESTABLISHED | NOT ESTABLISHED | Employees, Managers | NOT ESTABLISHED | NOT ESTABLISHED | | **BUSINESS** | NOT ESTABLISHED | Submit → Approve | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | | **SYSTEM** | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | | **TECHNOLOGY** | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | | **COMPONENTS** | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | | **INSTANCES** | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | NOT ESTABLISHED | # CELL DETAIL ``` SCOPE × WHAT Content: Expenses, Approvals (as business-level things) Source basis: "Employees submit expenses, managers approve them" Rule note: Placed at Row 1 (Scope) rather than Row 2 (Business) since the material states only that these things exist, with no entity relationship or business rule detail yet — Rule 3 requires the Row 1 model to be a plain list, not a related model. ``` ``` SCOPE × WHO Content: Employees, Managers Source basis: "Employees submit expenses, managers approve them" Rule note: None — direct fit. ``` ``` BUSINESS × HOW Content: Submit-then-approve workflow Source basis: "Employees submit expenses, managers approve them" Rule note: Placed at Row 2 (Business) rather than Row 1, since a two-step submit→approve sequence is itself a minimal process description, which is Row 2's concern (Rule 3) — even though the material is otherwise very sparse. ``` # OBSIDIAN NOTES ```markdown # Scope — What — Expenses and Approvals The core things this system concerns: expense submissions and manager approvals. No further detail (categories, thresholds, currencies) has been established yet. Links: [[Scope — Who — Employees and Managers]] [[Business — How — Submit-Approve Workflow]] ``` ```markdown # Scope — Who — Employees and Managers Two roles are named at this stage: Employees (who submit) and Managers (who approve). No org-chart or role-hierarchy detail is available yet. Links: [[Scope — What — Expenses and Approvals]] ``` ```markdown # Business — How — Submit-Approve Workflow The only process detail established: an employee submits an expense, a manager approves it. Sequence, timing, and exception handling are not yet defined. Links: [[Scope — What — Expenses and Approvals]] [[Scope — Who — Employees and Managers]] ``` # CLASSIFICATION TABLE N/A — this run is matrix-to-notes direction. # RULE CONFLICTS No rule conflicts in this run. # GAP DISCLOSURE 32 of 36 cells are NOT ESTABLISHED, including the entire WHERE, WHEN, and WHY columns, and every cell below Row 2. This reflects the actual state of the input — the material describes only who does what, with no location, timing, motivation, or technical detail supplied yet. This is expected for an early-planning-stage project and is not a shortfall of this analysis; it's an accurate map of what's actually been decided so far. # INPUT INTEGRITY NOTES NONE.