How brahmastra-labs/logicaffeine works
Logicaffeine is a natural-language programming and logic system: LOGOS English is parsed into formal representations, then either translated into executable code or interpreted, or rendered as logic and used for proof. Its CLI, browser Studio, and language server expose that engine through different workflows. The README also documents multiple execution backends, verification, concurrency, and distributed data. Arrows reflect documented workflows and sampled ownership; unsampled subsystem internals are represented only where the tree and README support them.
Main entry points: src/compile.rs Imperative compiler · app.rs Web Studio · src/compile.rs Logic compiler · lib.rs largo CLI
Components 22
User interfaces
- largo CLI
apps/logicaffeine_cli/src/lib.rs - Web Studio
apps/logicaffeine_web/src/ui/app.rs - Language server
crates/logicaffeine_lsp/src/server.rs - Browser progress
apps/logicaffeine_web/src/storage.rs
Language engine
- English parser
crates/logicaffeine_language/src/parser/mod.rs - Logic compiler
crates/logicaffeine_language/src/compile.rs - Logic semantics
crates/logicaffeine_language/src/semantics/mod.rs - Program analysis
crates/logicaffeine_compile/src/analysis/mod.rs
Execution
- Imperative compiler
crates/logicaffeine_compile/src/compile.rs - Rust codegen
crates/logicaffeine_compile/src/codegen/program.rs - Interpreter
crates/logicaffeine_compile/src/interpreter.rs - Bytecode VM
crates/logicaffeine_compile/src/vm/machine.rs - Native JIT
crates/logicaffeine_jit/src/lib.rs - WASM backend
crates/logicaffeine_compile/src/vm/wasm/mod.rs
Reasoning and verification
- Proof engine
crates/logicaffeine_proof/src/engine.rs - Proof kernel
crates/logicaffeine_kernel/src/lib.rs - Hardware verification
crates/logicaffeine_compile/src/codegen_sva/hw_pipeline.rs
Concurrency and data
- Concurrency runtime
crates/logicaffeine_compile/src/concurrency/mod.rs - CRDT data types
crates/logicaffeine_data/src/crdt/mod.rs
Other components
- LOGOS author
- Z3 verifier
- libp2p mesh
Connections 27
- LOGOS author → largo CLI: runs commands
- LOGOS author → Web Studio: writes English
- LOGOS author → Language server: edits programs
- largo CLI → Logic compiler: compiles logic
- largo CLI → Imperative compiler: builds programs
- largo CLI → Interpreter: runs programs
- Web Studio → Logic compiler: logic mode
- Web Studio → Imperative compiler: imperative mode
- Web Studio → Proof engine: requests proofs
- Web Studio → Browser progress: persists progress
- Language server → English parser: parses documents
- Language server → Program analysis: checks programs
- English parser → Logic compiler: produces formal logic
- English parser → Program analysis: supplies program AST
- Logic compiler → Logic semantics: uses semantics
- Imperative compiler → Program analysis: analyzes programs
- Imperative compiler → Rust codegen: emits Rust
- Imperative compiler → Bytecode VM: compiles bytecode
- Bytecode VM → Interpreter: executes fallback
- Bytecode VM → Native JIT: tiers up native code
- Imperative compiler → WASM backend: emits WASM
- Logic compiler → Proof engine: supports proof input
- Proof engine → Proof kernel: checks proof terms
- Hardware verification → Z3 verifier: checks equivalence
- Imperative compiler → Hardware verification: verifies hardware specs
- Concurrency runtime → CRDT data types: uses replicated types
- Concurrency runtime → libp2p mesh: connects peers