Gornskew Enterprises lays down Basilisk — a hull class of working starship, grown entirely from plans and flown in whatever galaxy you keep: one of your own, however small, or a rented berth in someone else's. Bring the plans, get the ship.
Gornskew Enterprises builds Basilisk — an open-source, AI-enabled engineering workstation defined entirely in code, and running wherever you point it: a laptop, a workstation under the desk, or a rented box in someone else's building. Bring the code, get the machine.
One incantation musters the whole crew: a Captain at the console, Engineers in the machine spaces, a Pilot at the helm and a Medic on watch, every post answering over HTTP, SLIME/Swank and subspace. What a ship carries is written down before it flies, so the yard can lay down the same one tomorrow, or a hundred of them.
One command brings up the whole set: an Emacs console, the Lisp engines, a reverse proxy and a watchdog, wired onto one network and reachable over HTTP, SLIME/Swank and MCP. What each machine should carry is written down rather than done by hand, so you can build the same one again tomorrow, or a hundred of them.
The engines those Engineers run are Genworks-built, and live at genworks.com. For the ideas underneath them — caching, dependency tracking, demand-driven evaluation, declarative form — see Concepts.
The knowledge-based engineering engines in those Lisp containers are Genworks', and they live at genworks.com. For the ideas underneath them — caching, dependency tracking, demand-driven evaluation, declarative form — see Concepts.
One fleet, given away. Two drones that stand a watch in it, built and sold by Gornskew Enterprises.
One stack, given away. Two binaries that ride in it, sold by Gornskew Enterprises.
The ship itself: a Captain, Engineers, a Pilot and a Medic, mustered as one crew and answering over HTTP, SLIME/Swank and subspace. The plans are the ship — what a hull carries is a file, and the ship is what that file builds.
The stack itself: an Emacs console, Common Lisp engines, a reverse proxy and a watchdog, wired onto one network and reachable over HTTP, SLIME/Swank and MCP. Infrastructure as code — what a machine should carry is a file, and the machine is what that file builds.
What Basilisk is →A single-eyed drone for the helm: give it the Captain's standing orders as symbolic expressions, and every consignment your ship takes on or sends out passes under that eye. One hull, perpetual engagement, no compiler aboard.
A small, serious reverse proxy for people who would rather configure services with symbolic expressions than wrestle YAML. Ships as a binary on an Allegro CL runtime — one host, perpetual license, no build tools required.
About Cyclops →A Comm drone for the bridge viewscreen: everything the ship watches gets a tile, and the bad news is the loudest thing on the board. Ships wearing our colours, and will wear any livery cut to the published contract.
The full-screen board that watches every property a fleet comprehends, and the one thing that reads Cyclops' vitals feed. Ships as a binary with base skins, plus a skins marketplace.
About Eyes Only →A ship you do not have to berth: one of ours, flying in our own galaxy, with the engines already aboard and the subspace channel open to you.
A Basilisk you do not have to house: hosted and metered, delivered over MCP, with the knowledge-based engineering engines already installed.
Gornskew offers this as a Genworks value-added reseller, so higher tiers can carry commercial NURBS solids, non-manifold booleans, and other licensed engine capability. Coming soon; to be shaped by demand.
Learn enough GDL to build real KBE systems, whether you are entering from the open-source path or preparing for commercial work.