What a complex-systems lab should make possible

Open-Informatics is my founder-operated complex-systems lab, with healthcare as its first developed domain and a method intended to travel beyond it.

I use the word "lab" because the work is still experimental and because the output should be more than a product. A good lab leaves behind methods, tools, records, and questions that other people can inspect. It should help a student or researcher do work that inaccessible data, expensive software, or a brittle research process previously kept out of reach.

That is the standard I care about: source-traceable research that expands what a student or researcher can produce, with a record showing where the evidence came from, how it was used, and where its support ends.

Start with the person trying to learn

Complex institutions are often easiest to study for people who already have access. They may have commercial datasets, enterprise software, a research office, experienced analysts, or enough time to learn every public portal separately. Students and independent researchers usually have fewer of those advantages.

Public data does not automatically correct that imbalance; a downloadable file may use unfamiliar identifiers, an annual source may disagree with a current website, and a technically public disclosure may remain difficult to locate, parse, or compare, leaving the researcher to solve those access problems before reaching the question that drew them in.

Open-Informatics should absorb some of that repeated work. The lab serves students and researchers first by keeping the method visible and the starting cost low. Operators, builders, journalists, and institutions can use the same infrastructure, but the design test begins with the person who does not already have an enterprise stack behind them.

The method is narrower than the ambition

The recurring method is practical:

1. Put narrow domain expertise close to the question.
2. Make difficult systems callable through explicit interfaces.
3. Retain provenance and missingness in the result.
4. Guard actions that can change a consequential system.
5. Keep the work portable enough to inspect outside one vendor or model.
6. Leave judgment and authority with people.

Together, those choices create a practical discipline for agentic software, which can produce a coherent answer before the evidence is ready; the infrastructure has to slow down at the right boundary, before a guess becomes a fact, a retrieved record becomes advice, or a model change becomes an approved engineering decision.

In healthcare, Healthcare Data MCP provides source-visible retrieval, FAST Identity supplies a completed body of identity and fail-closed admission research, Healthcare Agents provides specialist workups, USHSO turns selected findings into maintained reference records, and AJHCS gives research a public distribution path while retaining its own scholarly authority. Development across that program includes repeated acceptance replays, adversarial identity cases, exhaustive policy tests, live-source checks, measured rebuild experiments, and a benchmark harness with separated evaluation evidence; this is a substantial first-party experimental record rather than an independent evaluation of the complete source-to-publication architecture, whose next phase is broader source coverage, maintained evidence, and public worked research.

The method should travel

Healthcare is not the only field where the record is scattered, the tools are specialized, and a fluent mistake can be costly.

Cameo MCP Bridge connects an AI assistant to CATIA Magic and Cameo Systems Modeler through a local bridge, exposing model queries and guarded write operations through explicit tools; writes use sessions that support undo and redo, the client checks compatibility before proceeding, and the documented interface keeps model work inspectable and controllable.

MBSE Agents approaches the same domain from the knowledge side, organizing systems-engineering guidance around standards, artifacts, tool mappings, and the questions a reviewer is likely to ask; applicable standards and accountable program authorities remain controlling, the same boundary I want in healthcare when expertise is made easier to use.

SEAL applies the method to software and plans by separating observed repository facts, user intent, inference, evidence, missing proof, and human approval into traceable project records; a clean validation result establishes that those records are structured and candid about known gaps, while correctness and launch safety remain separate decisions.

These projects are at different stages, yet together they show how the method transfers across domains: make a complex system legible to an agent while keeping final authority with the people and institutions responsible for it.

Keeping open work maintained

I want the core to remain open: code that makes the method reusable, research methods, schemas, evidence contracts, and access for students. People should be able to inspect how a result was assembled and build their own work on the same foundation.

Openness does not pay for continuous maintenance. Public APIs change. Source files move. Licenses, dependencies, hosting, security reviews, data refreshes, and support all take time. Pretending otherwise usually leads to one of two outcomes: an abandoned public tool or a closed product whose method can no longer be examined.

The sustainability boundary is therefore explicit. Hosting, implementation, custom research, support, and maintained enterprise delivery may be paid. A team can pay Open-Informatics to operate the infrastructure or adapt it to a real setting. That payment should fund the difficult parts of continuity without turning the underlying research method into a secret.

The balance will change as maintenance costs and public use become clearer. I will explain that boundary and revise it in public, so users can understand both the business model and the open method.

What the lab owes its users

The lab owes users an evidence trail, honest limits, and software that fails clearly enough to investigate. It owes contributors and research subjects accurate credit. It owes students access that is useful in practice, not a ceremonial free tier that withholds the method.

It also owes them restraint. Healthcare workups remain distinct from clinical decisions. Systems-engineering agents answer to designated reviewers. A repository map does not authorize a launch. Those limits need to stay visible as the tools become more capable.

Open-Informatics will be worthwhile if it lets more people study institutions and engineered systems with evidence they can trace, tools they can understand, and conclusions they can challenge. That is a modest description of a difficult goal. I prefer it to promising intelligence without showing the work.

Notes

The Healthcare Data MCP and Healthcare Agents repositories document the healthcare retrieval, workup, evidence-pack, and authority boundaries discussed here.

The Cameo MCP Bridge, MBSE Agents, and SEAL repositories document the systems-engineering and project-assurance examples. Their public documentation was reviewed July 21, 2026. Volatile repository and release counts are intentionally omitted.

The founding argument, student and researcher priority, and sustainability boundary are my own. They describe the direction of Open-Informatics, not a claim that every part of that vision is complete.