@virid/core 0.0.1 → 0.1.1

package/LICENSE

@@ -0,0 +1,190 @@
+   Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Ailrid
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -1,259 +1,273 @@
-# 🛰️ @virid/core
+# @virid/core
 
+`@virid/core` is the logical heart of the entire Virid ecosystem. It provides a deterministic message distribution and scheduling mechanism designed to decouple business logic from complex UI frameworks and runtime environments.
 
+## 🌟 Core Design Philosophy
 
-> **A Lightweight, Message-Driven Logic Engine inspired by Rust's ECS Architecture and Nestjs.**
+- **Absolute Environment Independence**: This package does not depend on any browser, Node.js specific APIs, or third-party libraries (relying only on `reflect-metadata` for decorator functionality). This ensures the core can run seamlessly in Electron main processes, Worker threads, Web rendering layers, or even pure server environments.
+- **Deterministic Scheduling**: It introduces a "Tick" mechanism similar to game engines, utilizing a double-buffered message pool to ensure the predictability of logic execution order.
 
-[中文说明](README.zh.md)
+## 🛠️ Core Functional Overview
 
-## ✨ Features
+### 1. Message-Driven & Dispatcher Mechanism
 
+In Virid, all state changes must be triggered by sending a `Message` command.
 
+- **Automatic Scheduling**: By defining specific types of `Message` and corresponding `System` handlers, the engine automatically invokes the registered logic in the next microtask cycle (Tick).
+- **Message Types**:
+  - **`SingleMessage`**: Messages of the same type within the same Tick are automatically merged, suitable for state synchronization.
+  - **`EventMessage`**: Sequentially appended, ensuring the integrity of action sequences.
+  - **`ErrorMessage`**: Sequentially appended; errors are treated as a message type with a default handling System.
+  - **`WarnMessage`**: Sequentially appended; warnings are a message type with a default handling System.
+  - **`InfoMessage`**: Sequentially appended; information is a message type with a default handling System.
 
-### 🧩 What is CCS Architecture?
+### 2. Dependency Injection System (DI)
 
-`virid` is built on the **CCS (Component-Controller-System)** architecture. Based on the traditional ECS (Entity-Component-System) pattern, it introduces a "Controller" layer specifically for Web/UI environments to bridge logic and views seamlessly.
+Virid implements a lightweight, decorator-based DI system, allowing Systems to access data entities with minimal effort.
 
-#### 1. 💾 Component (Data) — "The Container of Truth"
+- **Data Entities (Component)**: Classes marked with the `@Component()` decorator are defined as data containers.
+- **Automatic Injection**: Once registered via `app.bindComponent()`, the Dispatcher automatically injects the corresponding instances based on the parameter types of the System function.
 
-- **Definition**: Pure data structures containing zero business logic.
-- **Responsibility**: Stores state (e.g., `PlaylistComponent` storing song lists and playback status). In `virid`, Components are managed as **Singletons** within the IoC container.
+TypeScript
 
-#### 2. 🎮 Controller (The Bridge) — "The Anchor of Views"
-
-- **Definition**: A proxy layer between the UI framework (Vue) and the core logic (Core).
-- **Responsibility**:
-  - **Projection**: Safely maps data from `Components` to Vue using `@Project`.
-  - **Command**: Captures UI events (like clicks) and transforms them into `Messages` to be dispatched to the engine.
-  - **Context Awareness**: Perceives UI hierarchy and metadata (like list indices) via `@Env`.
+```ts
+class IncrementMessage extends SingleMessage {
+  constructor(public amount: number) {
+    super();
+  }
+}
 
-#### 3. ⚙️ System (Logic) — "The Arbiter of Causality"
+@Component()
+class CounterComponent { public count = 0; }
 
-- **Definition**: A collection of stateless static methods and the **only** legitimate place for state transitions.
-- **Responsibility**: Listens for `Messages` and modifies `Component` data accordingly. Systems are **deterministic**, ensuring that the same input always yields the same state transition.
+class CounterSystem {
+  @System()
+  static onIncrement(
+    @Message(IncrementMessage) msg: IncrementMessage,
+    count: CounterComponent
+  ) {
+    count.count += msg.amount; // CounterComponent instance is automatically injected
+  }
+}
+```
 
-### 🛠️ Decoupling of Logic Sovereignty
+### 3. Lifecycle Hooks
 
-### 1. Total UI Demotion: Framework-Agnostic Core
+The Dispatcher provides comprehensive lifecycle monitoring:
 
-- **Transfer of Sovereignty**: The UI framework is stripped of its authority over state management and business scheduling, relegated to a pure **"State Projection Layer."** All business causality and state machine transitions are executed within the closed loop of `virid Core`.
-- **Physical Isolation**: The Core layer has zero dependencies on `DOM/BOM` APIs. Your core logic runs seamlessly in **Node.js servers, Web Workers, or even Command Line Interface (CLI) tools**.
-- **Seamless Migration**: Logical assets are no longer tethered to a specific UI library. Switch the adapter layer, and you are ready for **Vue, React, or beyond**.
+- **Execution Hooks**: Supports `onBeforeExecute` and `onAfterExecute` for global auditing or filtering before and after logic execution.
+- **Cycle Hooks**: `onBeforeTick` and `onAfterTick` monitor the start and end of each logic frame.
 
-### 2. Production-Grade Testability
+### 4. Industrial-Grade Robustness
 
-- **Farewell to Mocking Hell**: Say goodbye to JSDOM and complex browser simulations. Since the core logic is pure JS/TS, you can boot the Core directly in Node.js and complete unit tests for complex business flows via a **"Send Message -> Assert State"** pattern.
-- **Logic Playback**: As all side effects are triggered by messages, business logic becomes a **pure pipeline**, enabling offline refactoring and automated regression of production logic paths.
+- **Deadlock Defense**: The Dispatcher includes an `internalDepth` counter. If a logic chain triggers more than 100 levels of recursion, the system automatically fuses and throws an error to prevent the environment from hanging.
+- **Execution Priority**: Supports defining the order of multiple Systems handling the same message via `@System({ priority: number })`.
 
-### 3. Powerful Inversion of Control (IoC)
+------
 
-- **Deep IoC Architecture**: Built on **InversifyJS** for robust Dependency Injection. `Systems`, `Components`, and `Controllers` are auto-assembled via the container.
-- **Dynamic Lifecycle**: Supports on-demand loading and auto-injection of logic modules. Whether it’s a global singleton `System` or a `Controller` that dies with a component, the container manages the entire lifecycle.
+## 🛠️ @virid/core API Reference
 
----
+### 1. Engine Initialization
 
-## 🏎️ Game-Grade Scheduling Engine
+#### `createVirid()`
 
-- **Deterministic Tick Mechanism**: Introduces a Bevy-inspired message loop where all logical changes advance within discrete "Ticks."
-- **Double-Buffered Message Pool**: Physically isolates "processing" and "incoming" messages, effectively eliminating infinite loops and logical jitter.
-- **Physically Isolated Message Strategies**:
-  - **SingleMessage (Signal)**: Automatically merges identical signals, triggering a single batch process within the same Tick.
-  - **EventMessage (Event)**: Guarantees strict sequential execution, ensuring the atomicity of logical chains.
+- **Function**: Initializes the logical kernel and creates the globally unique `Dispatcher` and container.
 
----
+------
 
-## 🛡️ State Security & Access Control
+### 2. Instructions & Messages
 
-- **Read-Only Data Shield**: Controllers receive read-only proxies by default, strictly prohibiting illegal tampering with `Component` states outside of a `System`.
-- **Atomic Modification Protocol**: Data changes are forced through specific `AtomicModifyMessage` protocols, ensuring every state transition is traceable and auditable.
+#### `SingleMessage`
 
----
+- **Feature**: State synchronization message.
+- **Logic**: Multiple messages of the same type in one Tick are merged; the System typically receives only the latest one.
+- **Example**:
 
-## 🧬 Declarative Meta-Programming
+```ts
+import { SingleMessage } from "@virid/core";
+class MyMessage extends SingleMessage {}
+//Send messages anywhere
+MyMessage.send(); // Parameters correspond to the constructor
+```
 
-- **Decorator-Driven**: Use `@System`, `@Message`, `@Inherit`, and `@Project` to declaratively describe complex dependency networks and reactive logic flows.
-- **Automated Data Routing**: Dispatching a message immediately triggers the response; parameters are injected automatically, eliminating the need to write tedious boilerplate for listeners and dispatchers.
+#### `EventMessage`
 
-## 📖 Quick Start
+- **Feature**: Action command message.
+- **Logic**: Sequential, no merging. Every `EventMessage` triggers a System execution strictly.
+- **Example**: Same as `EventMessage`
 
-⚠️ Important: You MUST import reflect-metadata at the very first line of your entry file (e.g., main.ts), otherwise decorators will not function correctly.
+------
 
-Build a strictly protected state machine in a pure JS environment in just three steps.
+### 3. Data & Logic Definitions (Decorators)
 
-### 1. Define Components & Messages
+#### `@Component()`
 
-**Components** are pure data structures; **Messages** are the sole driving contracts.
+- **Function**: Marks a class as a **Data Entity**.
+- **Usage**: Used with `bindComponent` to enable dependency injection in Systems.
+- **Example**:
 
 ```ts
-import {
-  createvirid,
-  Component,
-  System,
-  Message,
-  SingleMessage,
-  AtomicModifyMessage,
-} from "@virid/core";
-
-// Initialize the core engine
-const app = createVirid();
-
-// Define Data Entity (Component)
 @Component()
 class CounterComponent {
   public count = 0;
 }
-// Register component
-app.bindComponent(CounterComponent);
-
-// Define operation instructions (Message)
-class IncrementMessage extends SingleMessage {
-  constructor(public amount: number) {
-    super();
-  }
-}
 ```
 
-### 2. Implement Systems
+#### `@System(params?)`
 
-**Systems** are stateless static methods. They retrieve components via Dependency Injection (DI) to handle business logic. You don't need to manually instantiate or invoke them—virid will automatically discover and execute them through static analysis.
+- **Function**: Registers a static method as a logic handler with automatic dependency assembly.
+- **Parameters**:
+  - `priority`: Higher values execute earlier in a Tick.
+  - `messageClass`: The message type that triggers this System (cannot coexist with `@Message`).
+- **Note**: Returning a Message (or array) from a System implements automatic logic chaining.
+- **Examples**:
 
 ```ts
-//Define System
+import {
+  System,
+  Message,
+} from "@virid/core";
+
 class CounterSystem {
-  @System()
+  // Priority can be set for the system
+  @System({ priority: 0})
   static onIncrement(
     @Message(IncrementMessage) message: IncrementMessage,
     count: CounterComponent,
   ) {
-    console.log("---------------------System----------------------");
-    console.log("message :>> ", message);
     count.count += message.amount;
   }
+  //You don't need to use @ Message if you already used messageClass
+  @System({messageClass:IncrementMessage})
+  static onIncrement(
+    count: CounterComponent,
+  ) {
+    count.count += 1;
+  }
+   @System()
+   static onProcess(msg: SomeMessage) {
+      // Directly return the message to achieve logical chain triggering, without the need to 		//manually call the Message Writer
+      // You can also return a message array to trigger continuously
+      return new NextStepMessage(); 
+   }
 }
+//Send messages directly through. send
+IncrementMessage.send(5);
 ```
 
-### 3. Headless Execution
+#### `@Message(Class, single?)`
 
-No browser required. Drive your business logic directly in **Node.js** or any testing framework.
-
-```ts
-// Business logic automatically completes scheduling in the next microtask
-queueMicrotask(() => {
-  IncrementMessage.send(1);
-  IncrementMessage.send(5);
-  queueMicrotask(() => {
-    AtomicModifyMessage.send(
-      CounterComponent,
-      (comp) => {
-        console.log("----------------AtomicModifyMessage------------------");
-        console.log("CounterComponent :>> ", comp);
-      },
-      "Check CounterComponent",
-    );
-  });
-});
-```
+- **Function**: Parameter decorator defining the message type for the System.
+- **Batch Mode**: Set `single: false` to receive an array of all messages of that type in the current Tick (ideal for high-performance batch processing).
+- **Example**: Same as `System`
 
-## 🛠️ Advanced Engineering Practices
+#### @Observer(callback)
 
-### ⚓ Lifecycle Interception (Middleware & AOP Hooks)
+- **Function** : Attribute level change monitoring, used to handle side effects that are not instruction driven
+- **Logic**  : When the attribute marked in 'Component' changes, the engine will automatically trigger the specified callback function.
+- **Example** :
 
-virid provides deep access to the message pipeline, allowing you to easily extend the system with features like **Undo/Redo, State Synchronization, or Automated Logging**.
-
-- **Middleware**: Pre-process messages before they enter the `EventHub`.
-
-  TypeScript
-
-  ```
-  app.useMiddleware((message, next) => {
-    console.log(`[Log]: Intercepted message ${message.constructor.name}`);
-    next(); // Continue the pipeline
-  });
-  ```
-
-- **AOP Hooks**: Perform aspect-oriented processing before or after specific message execution.
-  - `onBeforeExecute`: Triggered before System logic runs (e.g., for permission checks).
-  - `onAfterExecute`: Triggered after logic execution (e.g., for data persistence).
-
-  TypeScript
+```ts
+@Component()
+class PlayerComponent {
+  //Automatically send a synchronization message or execute a callback when progress changes
+  @Observer((old, val) => new SyncLyricMessage(val))
+  public progress = 0;
+}
+```
 
-  ```
-  app.onBeforeExecute(IncrementMessage, (message, context) => {
-    console.log("---------------- onBeforeExecute ------------------");
-    console.log("Message Details:", message);
-    console.log("Target System:", context.targetClass.name);
-    console.log("Method Context:", context.methodName);
-  });
-  ```
+#### `@Safe()`
 
----
+- **Function**: Method access marking. In Virid, The UI layer is restricted from directly modifying logic data. `@Safe()` explicitly authorizes the view layer to call specific "read-only" or "safe-calculation" methods.
+- **Example** :
 
-### ⚡ Atomic Modification: The "Snapshot" Privilege
+```ts
+@Component()
+class PlayerComponent {
+  // 如果不加Safe，virid将会禁止在任何vue的controller中调用该方法
+  @Safe()
+  public someMethod(){}
+}
+```
 
-To balance **strict constraints** with **development efficiency**, virid allows direct state mutations via `AtomicModifyMessage` without the need to write a full `System`.
+------
 
-- **Semantic Mutations**: Every atomic modification requires a mandatory `label`, transforming "arbitrary" assignments into auditable, meaningful actions.
-- **Consistency Guarantee**: Atomic modifications still follow the **Tick Scheduling** mechanism, ensuring that data changes are synchronized with System logic.
+### 4. Dispatcher & Hooks
 
----
+- **Double-Buffered Flip**: Each execution locks current messages; new messages generated during execution enter the next cycle.
+- **Hooks Example**:
 
-### 🚨 Everything is a Message: Robust Error Monitoring
+```ts
+const app = createVirid();
+app.onBeforeExecute(MyMessage, (msg, context) => {
+  // Global performance tracking or permission validation
+});
+app.onAfterTick((context) => {
+  console.log("----------------onAfterTick------------------");
+});
+```
 
-virid treats exceptions as first-class citizens of the system:
+------
 
-- **Automatic Encapsulation**: Any synchronous or asynchronous exception within a `System` or `Hook` is automatically captured by the `Dispatcher` and encapsulated into an `ErrorMessage`.
-- **Defensive Programming**: You can define a dedicated `ErrorSystem` to handle these messages globally (e.g., reporting to Sentry or triggering UI alerts). This ensures the core engine remains resilient and never crashes due to a single component failure.
+### 4. Dispatcher & Hooks
 
----
+#### **Dispatcher**
 
----
+The core scheduling engine of Virid operates on the following logic:
 
-## 🚀 Conclusion: Why virid?
+- **Double-Buffered Flip**: The scheduler runs based on logical **Ticks**. A Tick starts at the beginning of a microtask and continues until no new messages are generated internally. During each execution, the scheduler locks the current pending messages; any new messages generated during this process are automatically moved to the next cycle.
+- **Recursion Melt-down (Deadlock Defense)**: If the recursive execution depth (`internalDepth`) exceeds 100, the engine immediately halts and throws an error. This protects the main thread from being frozen by logical "black holes" or infinite loops.
 
-virid is not just another state management library; it is an endeavor to introduce **Deterministic Industrial Standards** to Web development.
+#### **Life-Cycle Hooks**
 
-As your project scales from dozens to thousands of components, and your business logic evolves from simple CRUD into intricate cross-component choreographies, the virid architecture ensures that your codebase remains:
+- **onBeforeTick / onAfterTick**: Monitor the "pulse" of logical frames.
+- **onBeforeExecute / onAfterExecute**: Audit the entire execution process for specific message types.
+- **Example:**
 
-- **Traceable**: Every logical transition has a clear trail via messages.
-- **Predictable**: Every state modification follows strict, predefined protocols.
-- **Decoupled**: Every business flow can be tested and validated entirely independent of the UI.
+```ts
+const app = createVirid();
 
-### 🛰️ Data Flow Architecture
+app.onBeforeExecute(MyMessage, (msg, context) => {
+  // Implement global performance tracking or permission validation here
+  // This hook only triggers for MyMessage and its subclasses
+});
 
-```mermaid
-graph TD
-    %% 定义外部触发
-    User([External/Logic Call]) -->|Message.send| Writer[MessageWriter]
+app.onAfterTick((context) => {
+  console.log("----------------onAfterTick------------------");
+});
+```
 
-    %% 核心引擎内部
-    subgraph Engine [Virid Core Engine]
-        direction TB
-        Writer -->|Middleware Pipeline| Hub[EventHub: Staging]
+### 5. System Communication (IO)
 
-        subgraph Dispatcher [Deterministic Dispatcher]
-            Hub -->|Tick / Buffer Flip| Active[EventHub: Active Pool]
-            Active -->|Sort by Priority| TaskQueue[Task Queue]
+#### **MessageWriter**
 
-            subgraph Executor [Execution Context]
-                TaskQueue -->|Identify| Sys[System Static Method]
-                Container[(Inversify Container)] -.->|Inject Component| Sys
-                Sys -->|Execute| Logic{Business Logic}
-            end
-        end
+- **Function**: A global static utility for system-wide communication.
+- **API**:
+  - **`MessageWriter.write(MessageClass, ...args)`**: The underlying entry point for dispatching messages. It instantiates the message class with the provided arguments and sends it to the Dispatcher.
+  - **`MessageWriter.error(Error, context?)`**: Throws a system-level error, which automatically triggers an `ErrorMessage`.
+  - **`MessageWriter.warn(context)`**: Logs a warning, which automatically triggers a `WarnMessage`.
+  - **`MessageWriter.info(context)`**: Logs an informational message, which automatically triggers an `InfoMessage`.
 
-        Logic -->|Update| Data[(Raw Component Data)]
+------
 
-        %% 异常与反馈流
-        Logic -- "New Message" --> Writer
-        Logic -- "Error" --> ErrorHandler[Error Message System]
-    end
+### 🔬 Advanced: Atomic Operations
 
-    %% 状态输出
-    Data -->|Optional Projection| Output([External State Observation])
+#### **AtomicModifyMessage**
 
-    %% 样式
-    style Engine fill:#fff,stroke:#333,stroke-width:2px
-    style Dispatcher fill:#f5f5f5,stroke:#666,dashed
-    style Container fill:#e1f5fe,stroke:#01579b
+- **Function**: Provides a "plug-and-play" solution for temporary logic modifications.
+- **Scenario**: When you need to perform a one-time observation or tweak a `Component` without the overhead of defining a dedicated `System`, you can use this message to execute a closure logic in the next logical frame (Tick).
+- **Example**:
 
+```ts
+AtomicModifyMessage.send(
+  CounterComponent,
+  (comp) => {
+    // Perform one-time inspection or modification on the component instance
+    console.log("----------------AtomicModifyMessage------------------");
+    console.log("Current Component State:", comp);
+  },
+  "Check CounterComponent" // Optional: label for debugging/tracing
+);
 ```
+
+------