The_Monad

ARCH.

The absolute fusion of Form and Will.
A self-installing, self-executing universe in a single file.

The Sacred
Separator.

An .arch scripture is divided into two hemispheres by the %% symphony directive. The top defines the physical manifestation (.scaffold), and the bottom defines the kinetic execution (.symphony).

1. Form Materializes First

2. Will Executes Inside It

self_hosted_db.arch

mixed

1# --- THE FORM (Scaffold) ---
2$$ db_password = "{{ secret(32) }}"
3
4docker-compose.yml :: """
5services:
6  db:
7    image: postgres:15
8    environment:
9      POSTGRES_PASSWORD: {{ db_password }}
10    ports:
11      - "5432:5432"
12"""
13
14# ==================================
15%% symphony
16# ==================================
17
18# --- THE WILL (Symphony) ---
19%% proclaim: "Form established. Igniting Database..."
20
21>> docker-compose up -d
22?? succeeds
23
24>> sleep 3
25>> docker exec db pg_isready
26?? succeeds
27
28%% proclaim: "Database is Resonant on port 5432."

Ω_NOVALYM

The Power of the Monad

Why separate setup from structure? The .arch file is the ultimate delivery vehicle for complex software environments.

Reproducible Environments

Share a single .arch file with a new developer. They run it, and their entire local machine is perfectly configured and running.

Executable Documentation

READMEs lie. Monads don't. The instructions for running the project are guaranteed to work because they are mathematically tied to the project's structure.

One-Click Demos