plan

[puleeno]

Basilisk Implementation Plan

Phase 1: Project Foundation

1. Initialize Rust project with cargo init
2. Set up Cargo.toml with dependencies:
   • pyo3 (Python bridge)
   • tokio + reqwest (async downloads)
   • rusqlite (SQLite)
   • blake3 (hashing)
   • zstd (compression)
   • ed25519-dalek (signatures)
   • anyhow, thiserror (error handling)
   • clap (CLI)
   • tempfile, pathdiff, num_cpus

Phase 2: Core Engine Modules

src/
├── main.rs           # CLI entry point (clap)
├── lib.rs            # PyO3 module export
├── engine/
│   ├── context.rs    # BuildContext, CommandBuilder, DependencyInfo
│   ├── sandbox.rs    # macOS Seatbelt sandbox wrapper
│   └── rpath.rs      # Mach-O RPATH relocation
├── state/
│   ├── database.rs   # SQLite operations
│   └── schema.rs     # Tables: packages, major_links, dependencies
├── resolver/
│   └── sat.rs        # SAT solver (pubgrub algorithm)
├── storage/
│   ├── bottle.rs     # .tar.zst extraction & metadata
│   └── links.rs      # Major symlink management
├── downloader/
│   └── fetch.rs      # Async bottle downloader
└── crypto/
    └── verify.rs     # Ed25519 signature verification

Phase 3: CLI Commands

• bsk install <pkg@major> - Install with auto-resolve
• bsk list --links - Show major symlink mappings
• bsk gc - Garbage collect orphaned packages
• bsk doctor - Verify RPATH integrity
• bsk uninstall <pkg> - Remove package
• bsk search <query> - Search available packages

Phase 4: Recipe System (PyO3 Bridge)

• Python basilisk_engine module with BuildContext, CommandBuilder
• Recipe base class for basilisk-mpm/recipes
• Sandboxed recipe execution

Phase 5: Bottle Infrastructure

• GitHub Actions CI/CD for building bottles
• Ed25519 signing pipeline
• METADATA.json schema validation