Update CONTRACTS.md

CONTRACTS.md

@@ -1,16 +1,16 @@
-<h1 align="center"> AISA Cross-Layer Contracts</h1>
+<h1 align="center">AISA Cross-Layer Contracts</h1>
 
-AISA relies on explicit cross-layer contracts to ensure predictable, governable, and reproducible agentic system behavior.
-These contracts define how constraints and signals propagate across layers.
+AISA defines a set of explicit cross-layer contracts that govern how constraints, signals, and guarantees propagate across system layers. These contracts ensure that agentic systems remain predictable, governable, and reproducible as they scale in complexity and autonomy.
 
 ---
+
 <div align="center">
 
 <table>
   <thead>
     <tr>
       <th>Contract</th>
-      <th>Purpose</th>
+      <th>Primary Purpose</th>
       <th>Key Artifacts</th>
     </tr>
   </thead>
@@ -23,17 +23,17 @@ These contracts define how constraints and signals propagate across layers.
     <tr>
       <td><strong>Telemetry</strong></td>
       <td>Enable auditability and traceability</td>
-      <td>Run IDs, traces, tool logs, policy markers, budget signals</td>
+      <td>Run identifiers, execution traces, tool logs, policy markers, budget signals</td>
     </tr>
     <tr>
       <td><strong>Versioning</strong></td>
       <td>Ensure reproducibility and controlled change</td>
-      <td>Models, prompts, tools, workflows, memory and evaluation artifacts</td>
+      <td>Models, prompts, tools, workflows, memory artifacts, evaluation suites</td>
     </tr>
     <tr>
       <td><strong>Budget</strong></td>
-      <td>Control cost, latency, and risk</td>
-      <td>Token limits, time limits, tool-call limits, cost ceilings</td>
+      <td>Control cost, latency, and operational risk</td>
+      <td>Token limits, time limits, tool-call limits, monetary cost ceilings</td>
     </tr>
   </tbody>
 </table>
@@ -44,10 +44,10 @@ These contracts define how constraints and signals propagate across layers.
 
 ## Contract Descriptions
 
-**Policy** :Defines what actions are allowed, restricted, or require approval, and how safety and escalation rules are enforced at runtime.
+**Policy** — Defines which actions are permitted, restricted, or require explicit approval, and how safety, escalation, and compliance rules are enforced during runtime execution.
 
-**Telemetry**  :Specifies the minimum signals required to trace, audit, and reproduce agent behavior across executions.
+**Telemetry** — Specifies the minimum set of signals required to trace, audit, and reproduce agent behavior across executions, enabling accountability and post-hoc analysis.
 
-**Versioning**  :Ensures that agent behavior changes are attributable to explicit,versioned artifacts rather than implicit system drift.
+**Versioning** — Ensures that changes in agent behavior are attributable to explicit, versioned artifacts rather than implicit system drift or undocumented configuration changes.
 
-**Budget**  :Bounds resource usage to prevent runaway behavior and enable cost- and risk-aware operation.
+**Budget** — Bounds resource usage across tokens, time, actions, and cost to prevent runaway behavior and enable cost- and risk-aware system operation.