government

commit 01d409d8a4b83bc1592daf61e55e68fa43d77f1e

tree

parent:
57ff1329428c2a48f4d12c02516f552806a79d7e

nmyk <nick@nmyk.io>

2026-11-15T10:22:04-05:00

readme edits

diff --git a/README.md b/README.md
index fddc8dc2ee6170398d67f4bda7ac13a2a6f8330b..22df6e75dc0feb3b5d3e93bc20139ff11c2af29d 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,29 @@
 # GOVERNMENT
 
+```
+   |                 |
+  / \               / \
+ /   \             /   \
+(_____)           (_____)
+ |   |  _   _   _  |   |
+ | O |_| |_| |_| |_| O |
+ |-  |             | - |
+ |   |  GOVERNMENT |   |
+ | - |          _  |   |
+ |   |   - _^_     |   |
+ |  _|    //|\\  - |   |
+ |   |   ///|\\\   |  -|
+ |-  |_  |||||||   |   |
+ |   |   |||||||   |-  |
+ |___|___|||||||___|___|
+         (      (
+          \      \
+           )      )
+           |      |
+           (      (
+            \      \
+```
+
 GOVERNMENT is a small Lisp whose programs are chains of X.509 certificates,
 stored in `.gov` files.
 
@@ -47,34 +71,15 @@    (define sq (lambda (n) (* n n)))
    (sq 12)
    ```
 
-2. Compile it:
+2. Compile it: `government compile square.gov.lisp -o square.gov`
 
-   ```sh
-   government compile square.gov.lisp -o square.gov
-   ```
+3. Run it: `government square.gov`. It prints `144`.
 
-3. Run it:
+4. Inspect the certificates with any X.509 tool, for example `openssl x509`.
 
-   ```sh
-   government square.gov
-   ```
-
-   It prints `144`.
-
-4. Inspect the certificates with any X.509 tool, for example `openssl x509
-   -text`.
-
-5. Show the program as a policy tree:
-
-   ```sh
-   government tree square.gov
-   ```
-
-6. Get the source back:
+5. Show the program as a policy tree: `government tree square.gov`
 
-   ```sh
-   government decompile square.gov
-   ```
+6. Get the source back: `government decompile square.gov`
 
 ## The language
 
@@ -135,7 +140,7 @@ each one that is not a `define`, one per line.
 
 ## The `.gov` file
 
-A `.gov` file holds PEM `CERTIFICATE` blocks: a trust anchor, then one
+A `.gov` file contains a series of PEM `CERTIFICATE` blocks: a trust anchor, then one
 certificate for each depth of the program. The compiler writes the anchor first,
 but the interpreter accepts the certificates in any order, because each
 signature links a certificate to its parent.
@@ -164,8 +169,8 @@ | 2         | Integer | The decimal text's code points | `-42`                          |
 | 3         | Float   | The decimal text's code points | `3.14`                         |
 | 4         | String  | The string's code points       | `"hi"`                         |
 
-Ids are unique within a program. A certificate's policies are an unordered set,
-so the ids are what record argument order.
+IDs are unique within a program. A certificate's policies are an unordered set,
+so the IDs are what determine argument order.
 
 ### Shared subexpressions
 
@@ -230,7 +235,7 @@ `--at` sets the time to check against. It defaults to now.
 
 ### Authorship
 
-1. Make an Ed25519 key:
+1. Make an [Ed25519 key](https://ed25519.cr.yp.to/):
 
    ```sh
    openssl genpkey -algorithm ed25519 -out ada.pem