1.1--- a/business.org	Sun Jul 02 00:36:31 2023 -0400
     1.2+++ b/business.org	Wed Nov 01 21:32:38 2023 -0400
     1.3@@ -2,12 +2,13 @@
     1.4 #+AUTHOR: ellis
     1.5 
     1.6 * Abstract
     1.7-In short, this document describes =otom8= the business. We are
     1.8-designed to be small, fast, and agile. We infiltrate a market, apply
     1.9-our methodology, and develop solutions that are simply years ahead of
    1.10-the competition. We treat the market like we're the only supplier,
    1.11-because we can. This is in part due to our internal research &
    1.12-development pursuits, but also our approach to business. We build
    1.13-businesses and revenue streams the exact same way we build software --
    1.14-with a bottom up approach. This is our secret weapon, and what gives
    1.15-us the ability to adapt to any environment where our interests lie.
    1.16+In short, this document describes the business aspects of The Compiler
    1.17+Company LLC. We are designed to be small, fast, and agile. We
    1.18+infiltrate a market, apply our methodology, and develop solutions that
    1.19+are simply years ahead of the competition. We treat the market like
    1.20+we're the only supplier, because we can. This is in part due to our
    1.21+internal research & development pursuits, but also our approach to
    1.22+business. We build businesses and revenue streams the exact same way
    1.23+we build software -- with a bottom up approach. This is our secret
    1.24+weapon, and what gives us the ability to adapt to any environment
    1.25+where our interests lie.

     2.1--- a/style.org	Sun Jul 02 00:36:31 2023 -0400
     2.2+++ b/style.org	Wed Nov 01 21:32:38 2023 -0400
     2.3@@ -1,3 +1,23 @@
     2.4 #+TITLE: style
     2.5 
     2.6-* U-Lang
     2.7+As an organization we maintain a styleguide[fn:1] which lists all of
     2.8+the style guidelines we use for our code. If you are contributing to
     2.9+one of our projects, you should review and understand the relevant
    2.10+sections below.
    2.11+
    2.12+You should also review the [[file:ulang.org][ulang]] document, which may shine some light
    2.13+on code comments and developer docs.
    2.14+
    2.15+[fn:1] https://google.github.io/styleguide/ 
    2.16+
    2.17+* Common Lisp
    2.18+
    2.19+* Rust
    2.20+
    2.21+* Emacs Lisp
    2.22+
    2.23+* Org-mode
    2.24+
    2.25+* Shell
    2.26+
    2.27+* Python

     3.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2+++ b/ulang.org	Wed Nov 01 21:32:38 2023 -0400
     3.3@@ -0,0 +1,53 @@
     3.4+#+TITLE: ulang
     3.5+
     3.6+This document defines a *U-Language* as described by the late great
     3.7+Haskell Curry:
     3.8+
     3.9+#+begin_quote
    3.10+Every investigation, including the present one, has to be communicated
    3.11+from one person to another by means of language. It is expedient to
    3.12+begin our study by calling attention to this obvious fact, by giving a
    3.13+name to the language being used, and by being explicit about a few of
    3.14+its features. We shall call the language being used the
    3.15+U-Language. [...] There would be no point in calling attention to it,
    3.16+if it were not for the fact that language is more intimately related
    3.17+to our job than of most others.
    3.18+#+end_quote
    3.19+
    3.20+There is a natural reader/writer relationship that exists in countless
    3.21+places, but is rarely examined because it is rarely necessary. However
    3.22+there is a wide array of significantly complex code and prose projects
    3.23+out there which would benefit greatly from such an investigation.
    3.24+
    3.25+I would also like to humbly clarify on our interpretation of a *job*
    3.26+as Curry puts it. We all have the same job really - to be curious, and
    3.27+to solve problems. It is the *problems* I would like to shine a light
    3.28+on, if just for a moment, because it's important. Just as Curry thinks
    3.29+of languages, we can think of problems. There exists the *problem of
    3.30+problems* which is the subject of our investigations. This *U-Problem*
    3.31+is what we are solving for at all times. In this light, we can view
    3.32+the *U-Language* as a means of bringing both the /reader/ and /writer/
    3.33+as close as possible to the *U-Problem*.
    3.34+
    3.35+For convenience, our *U-Problem* is undecidable, but we model and
    3.36+solve for it using /computers/, or more abstractly machines. Thus, our
    3.37+*U-Language* helps bring the /reader/ and /writer/ closer to
    3.38+our /machines/ as well as expedite communications.
    3.39+
    3.40+- /Why do we need a U-Language?/ ::
    3.41+  To bring both the /reader/ and /writer/ closer to our *U-Problem*.
    3.42+- /What is our U-Problem?/ :: 
    3.43+  Undecidable, but we use /computers/ as a model of the
    3.44+  *U-Problem*.
    3.45+- /How do we solve our U-Problem?/ ::
    3.46+  With /computers/, by developing accurate models and finding optimal
    3.47+  solutions.
    3.48+
    3.49+* Key Words
    3.50+* Abbrevs
    3.51+* Conditionals
    3.52+* Operators
    3.53+* Expressions
    3.54+* Links
    3.55+* Timestamps
    3.56+* Macros