Explicit authority
Every canonical transition requires an actor authorized for that exact operation.
Security
Security architecture.
wclmfenx separates authoritative state from provider execution, encrypts protected objects before replication, and grants scoped capabilities instead of root access.
Core security principles
Data minimization
Providers receive projections for the current task instead of unrestricted personal or organizational state.
Compartmentalization
Devices, applications, providers, and agents receive separate, revocable capabilities.
Encrypted state
Sensitive objects are encrypted before leaving approved local environments.
Provider revocation
Future context disclosure stops without deleting project or agent state controlled by the user.
Independent verification
Portable bundles support offline integrity, authority, lineage, and replay verification.
Security documentation
| Area | Design | Documentation |
|---|---|---|
| Canonical encoding | Deterministic signed representation | Encoding and signing |
| Object protection | Encryption and wrapped keys for each object | Encrypted object fabric |
| Capabilities | Scoped, attenuable, revocable grants | Capability model |
| Verification | Offline replay relative to a checkpoint | Verification scope |
Synchronization without relay access to your work
Encryption before transfer
Project snapshots are encrypted and authenticated in the browser. Recovery material and plaintext never enter relay storage.
Independent device keys
Each browser creates a nonextractable signing key. Requests bind the method, path, body, time, and unique request identity.
Immediate relay denial
Revoked device keys cannot read or append ciphertext. Recovery authority remains separate from everyday device access.