# HG changeset patch
# User ellis <ellis@rwest.io>
# Date 1698888758 14400
# Node ID 087da4ed0df6882a7f0c7acfb9f990b9c329e4f7
# Parent  b154f8be21c8c89c2c04ecf6b4230842b15115b1
ulang

diff -r b154f8be21c8 -r 087da4ed0df6 business.org
--- a/business.org	Sun Jul 02 00:36:31 2023 -0400
+++ b/business.org	Wed Nov 01 21:32:38 2023 -0400
@@ -2,12 +2,13 @@
 #+AUTHOR: ellis
 
 * Abstract
-In short, this document describes =otom8= the business. We are
-designed to be small, fast, and agile. We infiltrate a market, apply
-our methodology, and develop solutions that are simply years ahead of
-the competition. We treat the market like we're the only supplier,
-because we can. This is in part due to our internal research &
-development pursuits, but also our approach to business. We build
-businesses and revenue streams the exact same way we build software --
-with a bottom up approach. This is our secret weapon, and what gives
-us the ability to adapt to any environment where our interests lie.
+In short, this document describes the business aspects of The Compiler
+Company LLC. We are designed to be small, fast, and agile. We
+infiltrate a market, apply our methodology, and develop solutions that
+are simply years ahead of the competition. We treat the market like
+we're the only supplier, because we can. This is in part due to our
+internal research & development pursuits, but also our approach to
+business. We build businesses and revenue streams the exact same way
+we build software -- with a bottom up approach. This is our secret
+weapon, and what gives us the ability to adapt to any environment
+where our interests lie.
diff -r b154f8be21c8 -r 087da4ed0df6 style.org
--- a/style.org	Sun Jul 02 00:36:31 2023 -0400
+++ b/style.org	Wed Nov 01 21:32:38 2023 -0400
@@ -1,3 +1,23 @@
 #+TITLE: style
 
-* U-Lang
+As an organization we maintain a styleguide[fn:1] which lists all of
+the style guidelines we use for our code. If you are contributing to
+one of our projects, you should review and understand the relevant
+sections below.
+
+You should also review the [[file:ulang.org][ulang]] document, which may shine some light
+on code comments and developer docs.
+
+[fn:1] https://google.github.io/styleguide/ 
+
+* Common Lisp
+
+* Rust
+
+* Emacs Lisp
+
+* Org-mode
+
+* Shell
+
+* Python
diff -r b154f8be21c8 -r 087da4ed0df6 ulang.org
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ulang.org	Wed Nov 01 21:32:38 2023 -0400
@@ -0,0 +1,53 @@
+#+TITLE: ulang
+
+This document defines a *U-Language* as described by the late great
+Haskell Curry:
+
+#+begin_quote
+Every investigation, including the present one, has to be communicated
+from one person to another by means of language. It is expedient to
+begin our study by calling attention to this obvious fact, by giving a
+name to the language being used, and by being explicit about a few of
+its features. We shall call the language being used the
+U-Language. [...] There would be no point in calling attention to it,
+if it were not for the fact that language is more intimately related
+to our job than of most others.
+#+end_quote
+
+There is a natural reader/writer relationship that exists in countless
+places, but is rarely examined because it is rarely necessary. However
+there is a wide array of significantly complex code and prose projects
+out there which would benefit greatly from such an investigation.
+
+I would also like to humbly clarify on our interpretation of a *job*
+as Curry puts it. We all have the same job really - to be curious, and
+to solve problems. It is the *problems* I would like to shine a light
+on, if just for a moment, because it's important. Just as Curry thinks
+of languages, we can think of problems. There exists the *problem of
+problems* which is the subject of our investigations. This *U-Problem*
+is what we are solving for at all times. In this light, we can view
+the *U-Language* as a means of bringing both the /reader/ and /writer/
+as close as possible to the *U-Problem*.
+
+For convenience, our *U-Problem* is undecidable, but we model and
+solve for it using /computers/, or more abstractly machines. Thus, our
+*U-Language* helps bring the /reader/ and /writer/ closer to
+our /machines/ as well as expedite communications.
+
+- /Why do we need a U-Language?/ ::
+  To bring both the /reader/ and /writer/ closer to our *U-Problem*.
+- /What is our U-Problem?/ :: 
+  Undecidable, but we use /computers/ as a model of the
+  *U-Problem*.
+- /How do we solve our U-Problem?/ ::
+  With /computers/, by developing accurate models and finding optimal
+  solutions.
+
+* Key Words
+* Abbrevs
+* Conditionals
+* Operators
+* Expressions
+* Links
+* Timestamps
+* Macros