VoidLens
// always on watch · autonomous AI workforce
Run AI like a company.
Not a chatbot.
AI can already do a great deal of your work. The hard part is knowing what it did while you were not looking, and being sure it never does the one thing you would never have agreed to.
VoidLens is the desk you run it from. Every action is written down before it happens, along with what it cost. Nothing new is allowed to act on its own until it has spent forty-eight hours proving it can be trusted, and anything that matters waits for your yes. We run our own company on it: 35 agents organised into eleven divisions the way a real business is, with more than 2,300,000+ actions on the record.
across 11 divisions
lifetime, cumulative
spec-before-code
+ VOIDLENS™ USPTO ITU
deny-by-policy · immutable
none at L3 today — L2→L3 needs a clean 48h shadow
An AI workforce that runs itself, with you in the supervisor seat.
The era of AI that only gives advice is ending. The 2026 frontier is AI that senses, decides, and acts. The same year brought the first wave of agents deleting production systems and leaking data on borrowed credentials. VoidLens is the kernel for building an autonomous AI company the other way: the safety rails of a real engineering org, built in from message one.
Divisions, not bots
Eleven divisions, each led by a named director: kernel, governance, revenue, sales, marketing, legal, operations, product, hiring, a quant lab and an investment office. Every agent carries a playbook, a capability allowlist, and a daily budget cap, and 34 of the 35 carry a worker.md. On larger hosts, each division is designed to carry its own standalone local brain — the planned Adaptive Second Brain enterprise configuration (pilots ship with one shared local model today).
Forty-eight-hour ladder
No agent jumps straight to autonomy. Every capability earns its way from L0 read-only → L1 propose → L2 act-with-review → L3 act, through a clean 48-hour shadow window and a six-gate promotion check.
Audit-before-effect, by design
Every non-trivial action on the instrumented paths is one row in state/audit.jsonl — cost, duration, outcome, reason, playbook version. You can read what the company did, why, and what it cost. To the cent.
You don't prompt it. You supervise it.
You cannot make an AI safe by asking it nicely to behave, so VoidLens does not try. Every action on the instrumented paths is logged before it happens, checked against a list of things it may never do, which is refused at the gate and logged on every attempt, and it earns its independence through a forty-eight-hour trial run. You watch all of it from one screen, the cockpit, and approve anything that needs your call.
The Five Rails
Five engineering rails carry the whole safety posture: capability gating, a structured audit trail, the 48-hour ladder, eval-driven deploys, and audit-before-effect on the instrumented paths. Payments, hard-deletes and unapproved sends sit on a list that cannot be edited. They are refused at the capability gate on the instrumented paths, and logged on every attempt (the fully enforced plane is Phase 1 on the roadmap below). See the rails →
The cockpit
One control room. Watch the workforce act in real time, read the receipt for every governed action, and clear the approval queue. The dashboard, the audit reader and the boardroom sit in one lens. Open the cockpit →
Incorporated & filed
VoidLens, Inc. is a Delaware C-Corp (incorporated July 2026, EIN issued). Four provisional patent applications on the core inventions — the fourth, on execution-locus-bound provenance, filed 2026-07-03 — plus the VoidLens™ word mark were filed in the founder's name and assigned to the company on 2026-07-09, as the consideration for his founder shares. The company owns them; recording that assignment at the USPTO is still outstanding. The architecture you see is ours. The IP →
Fourteen weeks. The slope, not the snapshot.
VoidLens ships at compounding speed, and the receipts are dated rather than adjectival. From an empty directory to an incorporated company with four patent filings, a governed 35-agent workforce, and 2.3M+ audit rows, in one quarter. Pilot partners inherit that slope: every weekly increment lands in your instance too.
Apr 21
Genesis. The 54-hour founding build: Guardian gate, audit log, kill-switch, autonomy ladder, agent #1.
Apr 27
One kernel, many instances. The kernel split that lets new VoidLens instances stamp out from a single source of truth.
Jun 03–04
IP on file. Three provisional patent applications + the VOIDLENS™ trademark filed with the USPTO.
Jun 24
The adversary goes hands-free. A different-model reviewer attempts to falsify every load-bearing claim before it ships.
Jul 03
The crown jewel. Provisional #4 filed, covering execution-locus-bound, post-quantum-signed provenance manifests.
Jul 07
First external seat. A full VoidLens instance commissioned on a second human's machine, end-to-end, in a day (operator-reported).
Jul 08
VoidLens, Inc. Incorporated as a Delaware C-Corp, with the EIN issued two days later. Banking live for the first revenue lane.
Jul 14
voidlens.io launches. The public seat opens, and with it the first pilot offer.
Jul 22
The Helix goes live. Execution moved to a mode where the policy hooks actually fire, OS-attested, closing the gap between a rule that is written down and a rule that runs.
Jul 23
Autonomy earned, and a console to watch it. The first promotions ever minted through the full gate — two agents L0→L1, four 48-hour shadow windows opened (all four closed 07-25 with no further promotion) — the engineering gate drained 74/74, and the master operator console wired to live system data.
Jul 24
A second set of eyes. The Cognition Map became a mandatory session-start read, and a second outside adversary (Gemini) stood up in non-binding shadow beside the binding one.
Jul 25
Room first, then the outside. The internal review board must now exhaust a piece of work before an outside adversary confirms it.
Seeking our first pilot partners. Paid pilots only.
These are not free trials. They are pilots with skin in the game on both sides. First-cohort pilots run $1–3K/mo with a 90-day money-back, bring-your-own-keys, and your data staying in your systems. VoidLens also runs revenue lanes on the same kernel — an Etsy print-on-demand stream, the Sticks & Stones lodging stream (Stones Throw Holdings LLC), and Avera Logistics, LLC — the latter two founder-affiliated entities, not VoidLens, Inc. Those are live streams; VoidLens, Inc. itself is pre-revenue — said plainly.
Web-deployable, fast
A prior external seat stood up end-to-end in a day (operator-reported); your timeline varies with integration, security review and key setup. The design target is days, not a procurement quarter. The same kernel that runs our own company, stamped for yours.
Production velocity, inherited
The platform advances at compounding speed. The rail above is dated receipts rather than marketing. Pilot partners receive every increment as it lands, on a weekly cadence.
Governed from message one
33 registered red lines, the 48-hour ladder, audit-every-action on the instrumented paths. Your compliance team reads the receipts before your agents earn autonomy.
Eleven divisions. Organized like a company.
Thirty-five governed agents across eleven divisions, each led by a named director lens, because a workforce needs an org chart rather than a prompt library.
Where it is, and where it's going.
We name our own phase. Nothing on this site is called "enforced" until the enforced policy plane ships and can be checked by a third party. That rule is written into our canon, not just this paragraph.
Phase 0 · Today
Instrumented governance live on our own company: capability gating, git-gated canon, audit-every-gated-action, the 48h ladder. The first paying pilots will run here.
Phase 1 · Enforced core
The policy enforcement point, the decision plane and the API façade. This is the claim-gate where "governed" becomes "enforced" and third-party-checkable.
Phase 2 · Signed approvals
The supervisor seat as a signed-approval surface, making every human "yes" a verifiable artifact.
Phase 3+ · Attestation & scale
Multi-user, hardware-anchored approvals, provenance attestation, SOC 2 / ISO 42001 on the compliance wall.
Built by an operator. For operators.
Jeff Hicks
FOUNDER · VOIDLENS
Logistics operator first. Nine years in the Army across two combat tours, running convoy operations and logistics management at scale, then a decade in civilian logistics: dispatch, fleet, freight, the daily mechanics of moving real things through real systems on real deadlines. VoidLens is the AI workforce I built for that operator. Eleven divisions. A forty-eight-hour ladder before any new capability ships. Audit-before-effect, by design, logged to the cent. The five rails are not marketing copy. They are how my own company runs every day, and the audit log is the receipt.
Twenty-minute walkthrough. Live system.
Tell the founder who you are and what you'd want to hand off to the workforce first. We'll book a slot and walk through the live audit log, the org chart, and the proposal queue.