Engineering tools, made to last.

Most teams have far more capability than they have catalog. A consultancy with five years of past projects has dozens of patterns, components, and clean implementations buried inside engagements no one revisits. Folio surfaces them. It gives every software component the same kind of structured datasheet that every chip ships with — and adds fields that name the thing hardware doesn't have to deal with: the current form of the capability, where it lives in the codebase, what extraction would cost.

The result: when a customer asks if you've done X, the answer stops being "yes, sort of, somewhere" and starts being "yes; here's the datasheet; here's our extraction estimate."

$ cargo forge release
building targets:
  ✓ x86_64-unknown-linux-gnu
  ✓ aarch64-unknown-linux-gnu
  ✓ x86_64-pc-windows-gnu
  ✓ x86_64-unknown-freebsd
  ✓ aarch64-apple-darwin

5 binaries produced in 42.1s
artifacts: ./target/forge/

Born out of the pain of shipping Anvil to four platforms from a single FreeBSD workstation. Cargo-forge wraps cargo and zig as a universal cross-linker, producing release binaries for FreeBSD, Linux, Windows, macOS, and ARM64 from one machine without virtualization, container infrastructure, or elevated privileges.

The tool exists because the alternative — standing up a CI matrix or maintaining a builder VM per target — costs more than the project itself for a small shop. Cargo-forge collapses that cost to a single command.

A C++ orchestration platform for distributed field node monitoring and control. Handles node registration, heartbeat tracking, event processing, maintenance windows, staleness detection, and automated command dispatch — with a time-travel debugging architecture that lets operators replay and reconstruct any past system state.

Built on Wavelet Solutions' real-world SCADA experience. Currently in development; production target is critical infrastructure where auditability is not optional.

This entry will be expanded as Conductor approaches release.