Update Architecture.md to remove layer-specific references

- Remove 'three-layer architecture' from title and overview
- Change 'The Three Layers' section to 'Core Architecture'
- Remove 'The **Attribute layer**' bold formatting
- Remove DebugServer unified interface statement
- Simplify architecture description while maintaining technical accuracy

Author: Kyle-Ye

Sources/OpenAttributeGraph/OpenAttributeGraph.docc/Architecture.md

@@ -1,16 +1,16 @@
 # Architecture
 
-Understanding OpenAttributeGraph's three-layer architecture: Attributes, Graph, and Runtime.
+Understanding OpenAttributeGraph's architecture: Attributes, Graph, and Runtime.
 
 ## Overview
 
-OpenAttributeGraph is built around a three-layer architecture that provides a complete reactive programming system. Each layer serves a specific purpose in the overall framework, working together to deliver high-performance reactive updates.
+OpenAttributeGraph is built around an architecture that provides a complete reactive programming system. Each layer serves a specific purpose in the overall framework, working together to deliver high-performance reactive updates.
 
-## The Three Layers
+## Core Architecture
 
 ### Attribute Layer
 
-The **Attribute layer** forms the foundation of the reactive system, providing the building blocks for trackable, reactive values.
+The Attribute layer forms the foundation of the reactive system, providing the building blocks for trackable, reactive values.
 
 #### Core Concepts
 
@@ -153,6 +153,4 @@ Each layer provides debugging capabilities:
 
 - Attribute layer: Inspect individual attribute values and states
 - Graph layer: Visualize dependency relationships and update cycles  
-- Runtime layer: Examine type metadata and memory layout
-
-The ``DebugServer`` provides a unified interface for debugging across all layers.
+- Runtime layer: Examine type metadata and memory layout