1.1--- a/pitch.org	Tue Apr 30 22:16:13 2024 -0400
     1.2+++ b/pitch.org	Sun Jun 02 20:06:36 2024 -0400
     1.3@@ -1,8 +1,5 @@
     1.4-{{{header(pitch,
     1.5-Richard Westhaver,
     1.6-ellis@rwest.io,
     1.7-The Big Picture)}}}
     1.8-
     1.9+#+title: the big picture
    1.10+#+author: Richard Westhaver <ellis@rwest.io>
    1.11 * Get Off of My Cloud
    1.12   - industry has moved away from client-side, distributed compute in
    1.13     favor of centralized server-side compute resources behind API

     2.1--- a/roadmap.org	Tue Apr 30 22:16:13 2024 -0400
     2.2+++ b/roadmap.org	Sun Jun 02 20:06:36 2024 -0400
     2.3@@ -1,11 +1,59 @@
     2.4-{{{header(roadmap,
     2.5-Richard Westhaver,
     2.6-ellis@rwest.io,
     2.7-The Compiler Company Roadmap)}}}
     2.8+#+title: roadmap
     2.9+#+author: Richard Westhaver <ellis@rwest.io>
    2.10+#+description: The Compiler Company Roadmap
    2.11+
    2.12 * TODO 2024
    2.13 SCHEDULED: <2024-01-01 Mon>--[2024-12-31 Tue]
    2.14 - State "TODO"       from              [2023-11-05 Sun 21:47]
    2.15-* Q1
    2.16-* Q2
    2.17-* Q3
    2.18-* Q4
    2.19+** WIP migrate VC off of EC2                                  :opsec:vc:code:
    2.20+:LOGBOOK:
    2.21+- State "WIP"        from              [2024-05-06 Mon 16:43]
    2.22+:END:
    2.23+We no longer need to maintain an instance of our forge in AWS now that
    2.24+we have enough compute in-house.
    2.25+
    2.26+vc.compiler.company will be migrate to rurik on a dedicated pod
    2.27+(requires ubuntu).
    2.28+** WIP Wireguard VPN                                              :net:opsec:
    2.29+:LOGBOOK:
    2.30+- State "TODO"       from              [2024-05-06 Mon 16:48]
    2.31+- State "WIP"        from "TODO"       [2024-05-06 Mon 16:48]
    2.32+:END:
    2.33+Wireguard is a fast, secure, and easy to configure VPN library. All
    2.34+our primary devices have been configured and tested with two available
    2.35+endpoints. Our goal is to migrate all existing devices, then make
    2.36+appropriate accomodations for Podman containers, and finally KVM.
    2.37+** TBD IO                                                              :lisp:
    2.38+:LOGBOOK:
    2.39+- State "TBD"        from              [2024-05-06 Mon 16:50]
    2.40+:END:
    2.41+io_uring is the Linux library we have chosen to spend some time
    2.42+getting comfortable with and for which we've written incomplete Common
    2.43+Lisp bindings - URING. This library will soon be developed in parallel
    2.44+to the higher-level IO library - similar to the development of ROCKSDB
    2.45+and RDB.
    2.46+
    2.47+Over the next few months our IO ecosystem will slowly expand. As a
    2.48+short-term goal, we will implement simple binary streams backed by
    2.49+io_uring.
    2.50+** WIP skel
    2.51+:LOGBOOK:
    2.52+- State "WIP"        from "TBD"        [2024-05-06 Mon 17:06]
    2.53+:END:
    2.54+The pieces are there, just needs glue.
    2.55+
    2.56+A usable SKEL system is a top priority for this year. To get there we
    2.57+need to give love to many of the underlying core libraries too - most
    2.58+of all =cli=.
    2.59+
    2.60+The two top priorities are VC commands and implementing a functional
    2.61+replacement for makefiles as used in the infra project.
    2.62+** TODO infra
    2.63+:LOGBOOK:
    2.64+- State "TODO"       from              [2024-05-06 Mon 17:06]
    2.65+:END:
    2.66+It is time to move away from makefiles and start integrating our own
    2.67+programs into the system bootstrap process. This iteration of the
    2.68+infra project will have a few POSIX shell scripts for checking the
    2.69+host and grabbing a pre-compiled lisp as well as a compressed
    2.70+=infra.core= image.