Technology
How we build.
Every SolisHQ product is built on the same methodology, the same kernel, and the same uncompromising engineering standards. This page is the evidence.
Four layers. Zero ambiguity.
Limen separates concerns at the architecture level. Each layer has a defined boundary, a defined API, and defined invariants.
L1 — Kernel
SQLite-backed audit trail, role-based access control, invariant enforcement engine, and cryptographic provenance. The foundation everything else trusts.
L2 — Substrate
Transport layer, worker management, session lifecycle, and event bus. Handles the mechanics so the layers above can focus on intelligence.
L3 — Orchestration
16 system calls. Reasoning pipelines. Agent coordination. The API surface that products consume — stable, versioned, tested.
L4 — Application
Domain-specific products built on the orchestration layer. Juris, Accipio, SOLIS — each a proof that the kernel works.
Builder. Breaker. Certifier.
Three roles. Structural separation. No single role can ship alone.
BUILDER
Constructs from the specification. Every line of code traces to a spec requirement. No patches. No assumptions. No external patterns copied without derivation.
Writes code, tests, documentation
BREAKER
Attacks every assumption the Builder made. Adversarial testing against 9 mandatory defect categories. Finds the failures the Builder didn't imagine.
9 defect categories · adversarial analysis
CERTIFIER
Reviews the evidence. Verifies invariants hold. Gates the release. No code ships without Certifier sign-off. Independent of both Builder and Breaker.
Evidence review · release gate
7 Engineering Controls
Every change traces to a spec section
Failing test before fix
Impact declared before change
All tests run, not just related
Class 1–4 for every change
Architectural changes require approval
Every decision in writing
Inviolable engineering constraints
What 'first principles' means concretely.
Every dependency is an assumption you inherit. We chose to inherit almost none.
| Metric | Limen | LangChain |
|---|---|---|
| Production dependencies | 1 | 72+ |
| Supply chain surface | Minimal | Extensive |
| Audit trail | Built-in | Plugin |
| Cryptographic provenance | Ed25519 | None |
| Invariant enforcement | 99 | 0 |
| Structural role separation | B/B/C | None |
LangChain is a capable framework. The comparison isn't about quality — it's about architectural philosophy. Limen is designed for environments where every dependency is a liability and every decision must be auditable.
Cryptographic provenance.
Every module in the SolisHQ portfolio is cryptographically signed. You can verify what ran, when, and whether it was tampered with.
Our provenance system uses a 3-layer architecture: identity binding (organization + project + version), content registry (SHA-3-256 hash of every tracked file), and attestation (Ed25519 signature binding identity to registry).
997 modules across the portfolio are signed. Pre-commit hooks verify provenance on every commit. CI verifies on every build. The chain is unbreakable.
Provenance fingerprint (abbreviated)
org: "solishq"
project: "limen"
version: "3.3.0"
pubkey: "ed25519:Gk8x..."
files: 573
hash: "sha3-256:a7f2c..."
algorithm: "SHA3-256"
signature: "ed25519:Mx9p..."
signed_at: "2026-03-21T..."
status: VERIFIED