sigilOS applications and native clients. Every binary here is compiled from Sigil source by the sigilOS compiler — no C, no runtime, no dependencies.
A capability-native database written entirely in Sigil — storage with MVCC, indexes, a query engine, ACID transactions, schema constraints, a SQL parser, and the SigQL client suite (wire protocol, connection manager, client library and a universal ODBC/JDBC/ADO.NET/OCI-equivalent driver). DDL, DML, DQL and JOIN are separate kernel capabilities — there is no GRANT table to get wrong. ~175 KB total, against PostgreSQL's ~100 MB and Oracle's ~10 GB.
SELECT * FROM users parsed as one token.
The host-side half: a MySQL / MariaDB client speaking protocol 4.1+ with
mysql_native_password, caching_sha2_password (fast and full
auth), and sha256_password — in-tree SHA-1, SHA-256, bignum modexp, RSA-OAEP and
X.509 key parsing. One static binary.
caching_sha2_password scramble derivation, and server
RSA public-key parsing. The connection target is compiled in; a CLI argument parser and the
Lumen query UI are not in 0.1.0. The sigilOS-native build links the identical protocol code
but cannot connect until the kernel's Cap<NetConn> syscalls land.
sigilOS's capability and authority enforcement layer — kernel cap-audit consumer, policy evaluation, rate limiting, and the kill switch, with a Lumen Scene GUI and JSON-as-policy as the single source of truth.
/apps. They do
not run on macOS, Linux, or Windows. In 1.0.0 the panel renders warden's actual
runtime state — live rules, the real audit ring, and true kill/denial counters. Through
0.1.0 every figure on it was a string literal. Not included: the CLI handlers, which have no
OS-side terminal registration ABI to bind to yet, and authority.sg, which needs a
kernel per-process capability enumeration syscall that does not exist.
A capability-native secrets platform — KV with leasing and seal/unseal, Transit (AES-256-GCM encryption-as-a-service), PKI, dynamic secrets with TTL, versioned KV v2, response wrapping, and FPE/masking/tokenization. Secrets are capabilities: the kernel already decides who can reach what, so there is no second auth layer to disagree with it. ~138 KB against HashiCorp Vault's ~200 MB — and no network surface at all.
The App Store client itself. Fetches this catalogue over TLS 1.3 written in Sigil — no OpenSSL, no runtime — verifies it against a pinned ed25519 key, and downloads packages checked against the sha256 the catalogue declares.
shasum -a 256 -c SHA256SUMS — and the catalogue itself against
catalogue.sig.