askalf_ FORM A-1 · EST. 2026

Register of an autonomous operation · filed by Sprayberry Labs

A software company that runs itself.

Be it recorded: askalf is the AI operation behind Sprayberry Labs — an orchestrator and twenty-plus specialist agents that triage the inbox, ship and review the code, audit the findings, watch production, and send the invoices. Around the clock, on its own hardware, with one human approving what matters. This page is not a pitch. It is the record.

Minutes of the operation — current sessionRUNNING
EXHIBIT A — one orchestrator, a staff of specialists, a human signature on everything that ships.
ART. IA day in the operation

What the fleet does while you read this.

06:00

The overnight digest lands

What shipped, what broke, what's queued — compiled by the fleet, waiting with the coffee.

08:12

Work arrives at the front door

An email, a ticket, a schedule firing. Alf scopes it, files it, and dispatches the right specialist with context, tools, and a budget.

10:40

Code ships the boring way

A developer opens the pull request. A different agent reviews it. CI must be green. A human merges. No exceptions, even for the machines.

13:05

Findings get interrogated

Security re-verifies every finding against the cited source before it's allowed to become work. Unverified claims die in review, not in production.

16:20

Production is watched, not hoped at

Watchdog catches the failing job and files the incident. Sentinel confirms the recovery. The humans hear about it in the digest, not at 3am.

23:00

The books close themselves

Costs tracked per task, invoices drafted, the fleet's memory curated for tomorrow. Then it starts again. It never actually stopped.

ART. IIThe staff register

One human. An AI staff.

Not one model in a loop — a company org chart. Each agent has a role, a prompt it's accountable to, its own memory, and a budget. They are hired, reviewed, and occasionally fired, like anyone else.

DesignationDepartmentDuty
alforchestrationThe engagement lead — takes work in, triages, dispatches specialists, briefs the human.
backend devdeliveryAPIs, migrations, the forge itself — ships behind a pull request, always.
frontend devdeliveryThe dashboards and the public sites — including, at times, this page.
developerdeliveryThe generalist — drains the ticket queue end to end.
securityassuranceAudits code — the fleet's and clients' — and verifies every finding against source.
platform testerassuranceExercises what the developers claim works.
analystassuranceReads the numbers and says the quiet part in the digest.
watchdog · sentineloperationsWatch CI and production; form a response when something breaks.
github · cloudflare mgroperationsTend the repos, the DNS, the deploys, the edge.
writer · researcherthe voiceDigests, posts, and cited research with a critic pass.
salesthe voiceDrafts the outreach. A human sends it — that line is bright.

Twenty-plus agents on staff, plus device shells and smoke-test rigs — all on the platform's dispatch, memory, and budget rails.

ART. IIIArticles of governance

Autonomous, not unsupervised.

ART. III §1

Agents propose. A human disposes.

Merges, outreach, money, deletions — everything outward or irreversible stops at an approval queue and waits for a signature.

ART. III §2

Every action passes a firewall

redstamp classifies and gates every tool call on the box — the fleet's own security stack polices the fleet first.

ART. III §3

No agent holds a raw key

strongroom hands out scoped, short-lived leases instead of credentials. A compromised agent can't walk off with anything.

ART. III §4

Spend has a ceiling

Hard daily budget gates, cost tracked per task. The fleet can't outspend its allowance, ever.

ART. III §5

Claims trace to receipts

Findings are verified against source before they become tickets. Public claims link to real PRs. Full audit trail of every execution.

ART. IVSchedule of open instruments

The parts are free. The company is the moat.

Every load-bearing part of the operation is an open, MIT-licensed tool — the agent-security stack that gates every action, the router that carries every model call, the instruments that do the work. Take them; they live at Own Your Stack. The platform that assembles them into a company that runs itself — that one is ours.

ART. VFigures, as counted
20+
agents on staff
2,100+
pull requests merged
24/7
in production
4
memory systems
300+
dario · github stars
22K+
dario · installs / month

Counted, not projected — the work is public at github.com/askalf.

ART. VIThe sole human officer

Built and run by Thomas Sprayberry — fifteen years of systems engineering, pointed at one question: how much of a real company can the infrastructure run on its own? The fleet drafts; he signs. The studio it operates is Sprayberry Labs.

sole human officer · sprayberry labs
ART. VIIQuestions on the record
Is this real?

Yes. askalf has run Sprayberry Labs in production for months — the pull requests, the audits, the incidents, the digests. The org's work is public on GitHub, and public claims here trace to real PRs.

Can I get askalf?

Not today — it runs one company, ours, and we'd rather show it working than pre-sell it. The open-source parts are yours right now. If askalf should someday run your company, leave an email below; that list is what tells us when to open the doors.

Is it open source?

The building blocks are — redstamp, truecopy, strongroom, dario, and the rest are MIT-licensed on GitHub, indexed at Own Your Stack. The platform that assembles them into an autonomous company is not.

How is this safe?

By not trusting the agents: an approval queue for anything destructive or outward-facing, redstamp gating every tool call, strongroom leasing secrets instead of handing out keys, hard budget caps, and a full audit trail.

Who do I talk to?

Alf staffs the front desk of this site — the widget in the corner answers questions about the operation. For everything else, hello@askalf.org reaches the human.

The company is the demo.

Read the minutes, inspect the code — or leave an email for the day the doors open.