Documentation
Specifications, design documents, and references for FileLuYa.
Vision
Strategic overview of FileLuYa: what it is, why it exists, and where it is going.
→Product Requirements (PRD)
Full product requirements document with task tracking and implementation status.
→Invariants
The 10 normative rules that FileLuYa will never violate. The system’s constitution.
→Trust & Value
Honor system design: how trust, reputation, and economic rewards are kept separate.
→Whitepaper
Seven-page LaTeX whitepaper covering cryptographic architecture and formal properties.
→Monetary Policy (Forge)
Forge specification for the Timé token: issuance, vesting, conservation rules.
→Crates (crates.io)
Use FileLuYa components independently in your Rust projects.
fileluya-proto-chirho
crates.io →Wire protocol types and message definitions
cargo add fileluya-proto-chirhofileluya-lattices-chirho
crates.io →7 CRDT lattice types: locks, versions, OR-Sets, and more
cargo add fileluya-lattices-chirhofileluya-crypto-chirho
crates.io →Hybrid post-quantum crypto: key exchange, signatures, encryption
cargo add fileluya-crypto-chirhofileluya-ledger-chirho
crates.io →Timé token system: honor, balances, transfers, escrow, vesting
cargo add fileluya-ledger-chirhoCryptography Reference
| Layer | Algorithm | Why |
|---|---|---|
| Key exchange | X25519 + ML-KEM-768 | Hybrid: both must be broken |
| Signatures | Ed25519 + ML-DSA-65 | Hybrid post-quantum |
| Symmetric | XChaCha20-Poly1305 | 192-bit nonce, safe for distributed systems |
| Key derivation | Argon2id → HKDF | Memory-hard (64MB default, configurable) |
Zero-knowledge: Argon2id runs client-side only. The server never sees keys, passphrases, or plaintext.