About

Why I built ReasoningArc.

I am making the architecture and its limits visible so people can inspect, question, and challenge the work.

ReasoningArc did not start as a technology project. I experienced thirteen episodes over two days: eleven on June 12, 2025, followed by two lesser episodes on June 13. The episodes were originally diagnosed as a stroke. The Neurology Department at Augusta University is now investigating possible autonomic nervous system dysregulation as a deeper explanation, rather than treating the stroke label as the end of the inquiry. That evaluation is ongoing; I am not saying the original diagnosis has been overturned. The experience forced me to slow down and separate what I knew from what I assumed. I began to notice contradictions sooner, pay attention to why I believed something, and accept that uncertainty does not have to disappear before a decision can be made.

That is where ReasoningArc came from. I came to see reasoning as an arc: gather what is known, identify what is missing, test assumptions, follow competing explanations, and revise when the evidence requires it. The important part is not merely the answer. It is being able to see how you got there.

My work applies that lesson to machine reasoning and operational decisions: do not force the conclusion. Tend to the evidence. Follow the reasoning. Allow uncertainty to remain uncertainty.

What would have to be true for me to legitimately permit this system to act?

Creator

Thom Williamson

Creator, ReasoningArc · Aurum Trail Integrity Solutions, LLC

My background is in complex processes, technology delivery, accountability, and evidence-based decision systems.

Who this is for—and how to use it

Workflow designers

Use the architecture to identify the evidence, criteria, authority, stop conditions, and records a consequential workflow needs.

Reviewers and operators

Use the case record to challenge an evaluation, test whether authority is current, and see what uncertainty remains.

Researchers and critics

Try to break the candidate taxonomy, expose unsupported assumptions, and propose attacks that create new findings.

What ReasoningArc is—and is not

It is an evolving research architecture and working framework. The public site is intended to expose the model, its rationale, test history, and unresolved questions. It is not a certification, regulator-approved standard, finished software implementation, or proof of universal safety. The claim should never be stronger than its evidence.