From 377d0c13f8d2b536ba3c72d966837e3b411238af Mon Sep 17 00:00:00 2001
From: Poshith <poshithreddyr@gmail.com>
Date: Sat, 8 Aug 2026 22:19:00 +0530
Subject: [PATCH] Revise README with code and manifest.yaml example

Updated Python code snippet and added a YAML example for manifest configuration.
---
 README.md | 27 +++++++++++++++++++++++++--
 1 file changed, 25 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 4c33c0659..c8f82976e 100644
--- a/README.md
+++ b/README.md
@@ -127,7 +127,7 @@ Or use the full `AgentControl` API for programmatic control:
 ```python
 from agent_control_specification import AgentControl
 
-runtime = AgentControl.from_path(str("manifest.yaml"))
+runtime = AgentControl.from_path("manifest.yaml")
 result = runtime.evaluate(
     "input",
     {
@@ -139,6 +139,30 @@ print(result.verdict)
 runtime.close()
 ```
 
+```yaml
+# manifest.yaml (minimal, illustrative shape — matches the schema used in
+# examples/acs-email-tool/manifest.yaml). Running this requires a matching
+# policy adapter; see the linked example below for the full working version.
+agent_control_specification_version: "0.3.0-alpha-agt"
+metadata:
+  name: example-agent
+  version: "0.1.0"
+extends: []
+policies:
+  example_policy:
+    type: custom
+    adapter: example_policy
+intervention_points:
+  input:
+    policy_target: $.input.body
+    policy_target_kind: input_body
+    policy:
+      id: example_policy
+tools:
+  web_search:
+    clearance: internal
+```
+
 [Run the complete ACS email-tool example](examples/acs-email-tool).
 
 </details>
@@ -226,7 +250,6 @@ Agent ──► Policy Engine ──► Identity ──► Audit Log
                                                         ▼
                                                  Decision Record
 ```
-
 Every layer is optional. Start with `govern()` and add layers as your risk profile grows. Most teams run policy enforcement + audit logging and never need the full stack.
 
 ---