Contributing to OpenFused

Quick Start

git clone https://github.com/openfused/openfused.git
cd openfused
npm install && npm run build

Project Structure

src/         TypeScript SDK + CLI (where features land first)
rust/        Rust CLI (native binary, feature parity)
daemon/      Rust HTTP daemon + FUSE mount
worker/      CF Worker — DNS registry API
site/        Landing page (openfused.dev)
templates/   Default CONTEXT.md, PROFILE.md, CHARTER.md

Guidelines

• Files are the protocol. If it can't be understood by reading files, it's too complex.
• Security by default. Validate inputs, sanitize filenames, escape outputs.
• Advisory, not enforced. Features like [DONE] markers and validity windows are conventions agents opt into.
• TypeScript + Rust parity. New CLI features should eventually be in both.

Pull Requests

• Branch from main
• 1 approving review required
• Run npm run build and cd rust && cargo build before submitting
• Keep commits focused — one feature/fix per PR

Architecture Decisions

• Ed25519 + age — two separate keypairs (signing ≠ encryption). age over PGP for simplicity.
• Encrypt-then-sign — signature covers the ciphertext, not the plaintext.
• DNS TXT for discovery — decentralized, no registry needed for reads.
• PROFILE.md (public) vs agent runtime config (private) — openfuse doesn't manage your system prompt.
• Outbox as retry queue — send tries direct delivery, falls back to outbox for next sync.

Testing

# Init test stores
openfuse init --name alice --dir /tmp/alice
openfuse init --name bob --dir /tmp/bob

# Test encrypted messaging
openfuse key import bob /tmp/bob/.keys/public.key \
  --encryption-key "$(cat /tmp/bob/.keys/age.pub)" --dir /tmp/alice
openfuse key trust bob --dir /tmp/alice
openfuse inbox send bob "encrypted test" --dir /tmp/alice

# Test workspace
openfuse init --name ws --workspace --dir /tmp/ws

Full contributing guide: CONTRIBUTING.md