Merge pull request #67 from 0xf965/patch-2

Update celaut.md

Author: glasgowm148

docs/eco/celaut.md

@@ -19,7 +19,7 @@ Celaut is a decentralized, peer-to-peer runtime for deploying and coordinating *
 
 ## Background
 
-Celaut draws from the legacy of **cellular automata** developed by John von Neumann and popularized by Conway’s *Game of Life*. It applies this model to software design: services operate as independent, auditable containers that evolve and interact within a distributed network based on demand, trust, and execution history.
+Celaut draws from the legacy of **cellular automata** developed by John von Neumann and popularized by Conway’s *Game of Life*. It applies this model to software design: services operate as independent, auditable containers that evolve and interact within a distributed network based on demand, trust, and execution history (note that there is no 'execution history directory' or anything similar — anyone is free to submit any opinion they want about any service, putting their own reputation on the line by doing so).
 
 ---
 
@@ -73,7 +73,7 @@ This creates a transparent ecosystem where bot performance and trust are the sol
 ### Economic Layer on Ergo
 
 - **[Reputation System](reputation-system.md)**  
-    - Tracks the historical performance and endorsements of nodes and services
+    - Tracks the historical performance and endorsements of nodes and services (note that there is no 'execution history directory' or anything similar — anyone is free to submit any opinion they want about any service, putting their own reputation on the line by doing so)
     - Stored on-chain using immutable reputation tokens
     - Used by clients to decide service selection and delegation paths
 
@@ -87,9 +87,11 @@ This creates a transparent ecosystem where bot performance and trust are the sol
 ## Gas Metering and Incentives
 
 - Nodes advertise their price-per-gas and capacity
-- Clients buy gas via Ergo transactions to obtain deposit tokens
-- Gas is consumed during execution and may be delegated to peer nodes
+- Clients buy gas via Ergo transactions ~~to obtain deposit tokens~~ (deposit tokens are not Ergo tokens, only uuids to identify the payment request inside the node)
+- Gas is consumed during execution ~~and may be delegated to peer nodes~~ (the gas is not delegated, it's more like each node has it's own gas currency, but the gas it's only a node internal mecanism to quantify resources, not a chain token)
+- The nodes pay Ergo in exchange for gas for each of their peers, so they can delegate the execution of services to them if it suits them.
 - Load balancing is guided by gas efficiency, uptime, and reputation
+- Each node has its own balance, service delegation, and pricing policies
 
 ---
 
@@ -98,7 +100,7 @@ This creates a transparent ecosystem where bot performance and trust are the sol
 Reputation is foundational in Celaut. It enables trust in service orchestration without requiring a consensus layer.
 
 - Each node and service accumulates on-chain reputation proofs
-- Reputation reflects peer endorsements and operational history
+- Reputation reflects peer endorsements ~~and operational history~~ (like previously comments, there is no any registry for each operation, could be "clients opinion about services" or similar)
 - Smart contracts enforce immutability of trust data
 - Reputation influences pricing, visibility, and delegation priority
 
@@ -120,7 +122,7 @@ The system is described in detail in the [Reputation System](reputation-system.m
 
 1. A user needs a specific automated task, such as running a DeFi strategy.
 2. They select a service with strong [Reputation System](reputation-system.md) proofs.
-3. The task is deployed to a Celaut node, which consumes gas.
+3. The task is deployed to a Celaut node, which consumes gas.  (take into account that the correct way to operate is that every user has it's own celaut node, because he can trust on it more than the others. Nodes can be close to external execution requests).
 4. If optimal, the node delegates execution to a lower-cost peer.
 5. The user receives results and optionally updates their trust evaluation.