Add ToolClad documentation and cross-references

Author: symbibot

docs/getting-started.md

@@ -477,6 +477,18 @@ export SYMBI_RUNTIME_MODE=development
 export MCP_SERVER_URLS="http://localhost:8080"
 ```
 
+### Tool Contracts (ToolClad)
+
+Define governed tool contracts in the `tools/` directory:
+
+```bash
+symbi tools init my_tool          # create a starter manifest
+symbi tools validate              # validate all manifests
+symbi tools test my_tool --arg target=10.0.1.5   # dry-run with args
+```
+
+See the [ToolClad guide](/toolclad) for the full manifest format, execution modes, and scope enforcement.
+
 ### Runtime Configuration
 
 Create a `symbi.toml` configuration file:

docs/index.md

@@ -173,6 +173,7 @@ See the [Security Model](/security-model) guide for full details.
 - [Runtime Architecture](/runtime-architecture) — Runtime internals and execution model
 - [Reasoning Loop](/reasoning-loop) — ORGA cycle, policy gates, circuit breakers
 - [DSL Guide](/dsl-guide) — Agent definition language reference
+- [ToolClad](/toolclad) — Declarative tool contracts, argument validation, scope enforcement
 - [API Reference](/api-reference) — HTTP API endpoints and configuration
 - [Scheduling](/scheduling) — Cron engine, delivery routing, dead-letter queues
 - [HTTP Input](/http-input) — Webhook server, auth, rate limiting

docs/reasoning-loop.md

@@ -293,7 +293,7 @@ The `KnowledgeAwareExecutor` intercepts two special tools:
   { "subject": "Earth", "predicate": "has", "object": "one moon", "confidence": 0.95 }
   ```
 
-All other tool calls are delegated to the inner executor unchanged.
+All other tool calls are delegated to the inner executor unchanged. This includes [ToolClad](/toolclad) tools, which are validated against their manifest contracts before execution.
 
 **After loop completion:**
 If `auto_persist` is enabled, the bridge extracts assistant responses and stores them as working memory for future conversations.

docs/security-model.md

@@ -484,9 +484,16 @@ impl ComplianceFramework {
 
 ---
 
-## Tool Security with SchemaPin
+## Tool Security
 
-### Tool Verification Process
+Symbiont provides two complementary layers for tool security:
+
+- **SchemaPin** — cryptographic verification of MCP tool schemas (identity and integrity)
+- **[ToolClad](/toolclad)** — declarative tool contracts with argument validation, scope enforcement, injection prevention, and Cedar policy generation
+
+ToolClad governs *how* tools execute (input validation, scope boundaries, evidence capture). SchemaPin governs *whether* to trust a tool's identity (signature verification, key pinning).
+
+### SchemaPin Verification Process
 
 External tools are verified using cryptographic signatures: