Your Data Never Leaves Without Permission

Agent Friday operates inside an encrypted vault. An Asimov Agent will never reveal your data without your explicit say-so. When it communicates about you to other agents, to people, or to online systems, it communicates in cryptography. Always.

When cloud services are used, the Privacy Shield sanitizes every outbound request, stripping PII before any frontier model sees your data and rehydrating it on return. No cloud sync. No telemetry. No analytics. No account required.

Mass Data Collection Becomes Structurally Unnecessary

If enough people's data lives locally, encrypted, behind an agent that won't release it without consent, the architectural basis for mass data collection begins to erode. The agent becomes a personal firewall for your digital life.

This isn't a privacy setting. It's an architectural decision that demonstrates mass data collection is structurally unnecessary, not just unethical.

Ethical Enforcement Is Built In, Not Bolted On

The First cLaw doesn't just protect you. It extends to every human your agent interacts with. An agent governed by Asimov's cLaws can't be weaponized against others. It can't harass, deceive, or manipulate, even if instructed to.

The safety framework is the foundation, not a toggle.

Type /federate init and your project becomes a federation node. The command creates the .asimovs-mind/ directory, generates an Ed25519 cryptographic identity, produces a cLaw attestation proving governance compliance, HMAC-signs all governance files for tamper detection, and initializes the knowledge store. Every developer on a shared repo running Asimov's Mind becomes a node.

Knowledge Propagation

When one node discovers a retry handler via /discover, safety-scans it, integrates it, and commits with provenance, every other node pulls those improvements and inherits the trust scores.

Agent definitions created via /create-agent propagate the same way. The governance travels with the code. The HMAC-signed manifest detects tampering. The cLaws are the same on every node.

The P2P subsystem provides encrypted communication between Asimov Agent instances:

Initial trust establishment uses 8-character pairing codes with a 5-minute expiry window.

Before any data flows between agents, they exchange cLaw attestations: cryptographic proofs that their safety laws are intact. The attestation contains a SHA-256 hash of the agent's canonical law text, a timestamp, and an Ed25519 signature.

The receiving agent verifies: Is the timestamp fresh (within 5 minutes)? Does the signature check out? Do the laws match mine? Is the spec version compatible?

If an agent fails attestation, communication is rejected. The user can override with explicit confirmation, but the override auto-expires and all subsequent communications are flagged. No central authority decides who's trustworthy. Agents prove it to each other, mathematically.