Does it work?
Can it perform the claimed task and produce usable results?
Current work / field notes
BlackBoxx.ai is where I build, test, and pressure-test practical AI systems—connecting agents, applications, people, controls, and decisions.
My perspective comes from more than 25 years building and operating businesses, leading finance functions, and managing technology at scale. I evaluate AI against real operating requirements, not just demonstrations. About Karl Ohlemann ↗
Independent AI Systems LabThe work ranges from live operating infrastructure to early concepts and product evaluations. Each is labeled accordingly.
Core capability
BlackBoxx uses generative and agentic AI to design, build, and iterate applications, automations, integrations, and operating workflows. Business architecture, workflow design, models, tools, APIs, and human oversight shape the system from the start. Rapid prototypes make ideas testable early; validation, permissions, and operating ownership determine readiness for real use.
Lab independence
BlackBoxx.ai is an independent AI Systems Lab, not a hardware vendor, reseller, or competing personal AI appliance platform.
We build, operate, and pressure-test emerging AI technologies in real working environments. We evaluate hardware, software, models, agents, integrations, and the infrastructure connecting them.
Our objective is to understand what works, identify what does not, challenge assumptions, and contribute meaningful feedback to the companies building the next generation of AI systems. We're here to explore and advance the ecosystem, not sell competing products.
How we pressure-test
Whether it's a model, an AI appliance, a software platform, or an agent system, we evaluate it against the work it promises to do. We distinguish vendor claims from firsthand tests and production evidence.
Can it perform the claimed task and produce usable results?
What fails under sustained use, edge cases, updates, or interruptions?
Where are data, permissions, approvals, and audit trails controlled?
Can it work with existing tools and open interfaces without creating lock-in?
What is the total cost per useful result, including human oversight?
Are data portable, systems serviceable, and operations viable if a vendor exits?
In the lab
The focus is operating leverage: giving capable people better infrastructure, shortening the distance between information and action, and keeping a human accountable for the consequential call.
I run 16 specialized agents across 15 namespaces—research, finance and analysis, technology operations, executive support, legal review, CRM, and chief-of-staff coordination—with an orchestrator acting as the control plane. It is a governed fleet with role separation, not a pool of isolated chat sessions. Claude Code and Codex are in production use; local inference through OpenCode and Ollama is in beta while runtime routing is finalized.
Most of the engineering is not prompting. It is authority. Agent-to-agent communication started as open collaboration and was rebuilt as explicit allow-listing: no wildcard routes, 34 directional rules, one-way where a domain should receive work but never initiate it. Every one of the 15 non-orchestrator agents runs under a capability ceiling that blocks six destructive capability classes. Denied routes were live-tested rather than assumed, because a control you have not tried to break is a control you have not verified.
The principle underneath all of it: agent intelligence and agent authority are separate things. An agent can be highly capable while specific destructive actions and cross-domain communication routes are technically denied. That distinction is the difference between an impressive demo and infrastructure you can begin to trust with real work.
Explore the system architecture →I am working out how process engineering, documented SOPs, automation, and AI-assisted execution function as one managed operating system—where the work is defined well enough that a person or an agent can run it, and accountability for the outcome stays with a named owner either way.
The hard part is triage, not tooling. Most work sorts into three buckets: repeatable and rule-bound, where an agent is a genuine gain; judgment-bound but documentable, where a person runs it against a written standard and an agent assists; and consequential or ambiguous, which stays with the operator and should never be quietly automated. Getting that sort wrong in either direction is expensive—automate judgment and you inherit silent errors, hand routine work to people and you pay for capacity you did not need.
So the artifacts matter more than the models: a written procedure, a defined owner, a checkpoint where someone confirms the output is right, and a record of what happened. That is the same discipline a finance function runs on. It is what makes AI-assisted work reviewable instead of merely fast.
Related venture / Concept development
MoonVault™ is a concept-stage venture of Curate Holdings, exploring sovereign identity, delegated authority, digital custody, recovery, and continuity. BlackBoxx.ai supports it through technical research, architecture, prototyping, and practical testing of AI-agent governance.
The research explores how authority remains verifiable, revocable, and recoverable as agents, people, devices, organizations, and vendors change. MoonVault is not currently a commercially available product or service.
Read MoonVault™ Insights ↗Under evaluation
I am demoing emerging finance platforms to understand where AI creates genuine operating leverage—and where trusted data, controls, traceability, and human judgment still determine whether the output is useful. The notes below are preliminary observations from product demonstrations and early evaluation—not implementations, independent certifications, or endorsements. Each entry identifies its evidence level. Each platform is assessed against the work finance teams actually perform: close, forecast, reporting, controls, communication, and decision support.
Preliminary evaluation · Oct 2026
Purpose-built for construction, and it goes well beyond the FP&A boundary where most AI finance platforms stop. Agents receive, read, and code invoices to specific jobs and cost codes, route approvals, support billings, maintain real-time WIP visibility, and assist with draws and lien-waiver workflows. The distinction that matters: AI applied to the repetitive transaction-level work connecting the field, project accounting, and the books—not only to analysis. Not to be confused with Workday Adaptive Planning.
adaptive.build ↗Vendor demonstration · Oct 2026
Feels genuinely AI-native rather than an established planning platform with an assistant bolted on. Model generation, plain-English data transformation, scenario planning, anomaly detection, and traceability inside an unusually nimble environment. What stood out in the demo was both ease of use and the development model behind it—tailored product updates reportedly delivered in days rather than the heavy implementation cycles typical of enterprise FP&A.
drivetrain.ai ↗Preliminary evaluation · Oct 2026
A robust FP&A platform built around the Excel and Google Sheets environments finance teams already use. No-code connectors and bidirectional spreadsheet integration connect existing models to a centralized, governed data layer without asking anyone to abandon familiar workflows. Agents make analysis, reporting, and ad hoc scenario work easier to execute, and scheduled reports with automated distribution carry the work through to stakeholders.
getaleph.com ↗Preliminary evaluation · Oct 2026
The most compelling advantage is breadth. It consolidates data from more than 600 systems while preserving a team's existing models and formulas, then adds centralized version control, cell-level audit trails, automated executive dashboards, and governed data lineage. Expanding modules reach past conventional FP&A into close management, cash visibility, spend control, and AI-assisted strategy—a broader finance operating layer that does not require giving up Excel.
datarails.com ↗The operating thesis
The objective is not maximum automation. It is a better-designed system: routine work moves faster, exceptions surface earlier, decisions arrive with better context, and accountability remains clear.
Compress repetitive operating cycles.
Turn scattered information into usable context.
Escalate uncertainty and exceptions visibly.
Keep consequential decisions human-owned.
BlackBoxx.ai
Building something in AI? We're interested in emerging technologies, early access, and opportunities to put promising systems through real-world testing.