docs: update sparse kernel repo positioning

Author: AbrahamGreenman

README.md

@@ -25,6 +25,7 @@ It is built for personal and small-machine deployments where hundreds of agents
 - Brokers expensive resources by trust zone: browser contexts, sandbox allocations, filesystem access, tool invocation, and artifact reads/writes.
 - Keeps large outputs out of SQLite by placing screenshots, traces, downloads, exported transcripts, and other blobs in a content-addressed artifact store.
 - Enforces capability checks around sensitive operations and records allow, deny, grant, revoke, and broker events for auditability.
+- Defines an Agent Factory boundary for observing workflows, generating agent specs, compiling policy, and handing deployment plans to Sparse Kernel for safe execution.
 - Provides a Rust core, a local CLI/daemon, and a small TypeScript client surface for adapters.
 
 ## Why Sparse Execution
@@ -43,15 +44,23 @@ The goal is to make local multi-agent systems practical on ordinary machines, in
 
 - `crates/sparsekernel-core`: Rust ledger, artifact store, task leases, capabilities, audit records, and mock broker primitives.
 - `crates/sparsekernel-cli`: `sparsekernel` CLI and `sparsekerneld` local daemon.
-- `crates/sparsekernel-core/migrations/0001_initial.sql`: initial SQLite runtime schema.
+- `crates/sparsekernel-core/migrations/`: SQLite runtime schema migrations.
+- `packages/agent-factory`: TypeScript contracts for workflow observations, candidate workflows, agent specs, policy compilation, and deployment plans.
+- `packages/agent-factory-connectors`: connector adapter contracts for Gmail, CRM, calendar, accounting, and ticketing discovery surfaces.
 - `packages/browser-broker`: TypeScript CDP browser broker for materialized browser-context leases and artifactized screenshots/downloads.
 - `packages/openclaw-sparsekernel-adapter`: TypeScript adapter that wraps OpenClaw-shaped tools in Sparse Kernel session, capability, tool-call, and artifact lifecycle calls.
 - `packages/sparsekernel-client`: TypeScript client for the daemon HTTP surface.
-- `schemas/`: API and event schema definitions.
+- `schemas/`: API, event, capability, and Agent Factory schema definitions.
 - `docs/architecture/`: architecture notes for the ledger, brokers, artifact store, trust zones, security boundaries, and small-VM resource model.
 
 The Rust crates are workspace-internal for now (`publish = false`); run them from this repository until a crates.io release path exists.
 
+## Agent Factory Boundary
+
+Agent Factory decides what should exist. Sparse Kernel decides how it safely runs.
+
+The factory contracts model workflow observations, candidate workflows, generated agent specs, compiled policy, approvals, evaluations, and deployment history. The factory does not allocate browser contexts, open sandboxes, invoke connector tools, or grant capabilities directly; it emits deployment plans that the Sparse Kernel ledger and brokers can approve, audit, and materialize.
+
 ## Quick Start
 
 Runtime requirements: