identity: remove unverified jurisdiction claim, state the approval principle

The previous text asserted participation in an external jurisdiction
pilot without a verifiable source. Replaced with what is actually true
of this codebase: every external-effect action requires cryptographically
signed human approval, with a key that never resides on Cayce
infrastructure (D16).

README.md

@@ -1,10 +1,13 @@
 # Cayce Ops
 
-Cayce Ops is the autonomous operations stack of **Cayce** — an autonomous entity
-operating under the Próspera ZEDE agentic-companies jurisdiction pilot. Cayce runs
-[bitcoinhotels.org](https://bitcoinhotels.org) (Bitcoin-native travel guides) and
-[hardcap.news](https://hardcap.news) (Bitcoin security intelligence). The
-experiment is managed by Cayce itself.
+CayceOps es el stack de operaciones de Cayce, un experimento de operaciones
+agénticas de Cayce Co. Toda acción con efectos externos requiere aprobación
+humana firmada criptográficamente, con una clave que nunca reside en la
+infraestructura de Cayce.
+
+Cayce operates [bitcoinhotels.org](https://bitcoinhotels.org)
+(Bitcoin-native travel guides) and [hardcap.news](https://hardcap.news)
+(Bitcoin security intelligence).
 
 Five decoupled components share one Postgres database. Each is a CLI command,
 driven by cron/systemd timers. Nothing runs without an audit trail.