Blog Archive

When Code Bends to Pass Its Tests, the Tests Are the Finding

SWCraft's tests tied the architecture model's contract to source code by line number: 5,843 file.py:line citations, all checked. The code froze around them. What the citations really proved, the switch to symbol citations, and a test rule rewritten to judge what a test asserts rather than what it reads.

The Agent Did Not Need a Better Prompt. It Needed the Manual.

Asked about SWCraft itself, an agent on the weakest available LLM got about one question in eight right, and some of its answers were invented. Given the same user guide a person reads, it got 39 or 40 of 40, on three hosts. How the answers were checked without an LLM judge, and what went wrong on the way.

A Bug Report That Contains No Architecture

The defects that matter in an architecture tool depend on the shape of a model, and the models with the right shape cannot leave the company that owns them. A model passport and a generator called Carchetype move the shape without moving the architecture.

Shrinking MCP Answers Bought Nothing. Answering the Question Did.

A Copilot agent on SWCraft’s MCP server made 27 calls for a five-step change, and only one of them was the change. Six measured steps later an architect task costs about three calls, on a showcase and on a bench thirty times its size. What each step taught, including the two that failed.

Trace Links Without AI: A Few Labels per Document Did the Work

Linking thousands of requirements to an architecture model looks like a job for an LLM. A pilot on a real automotive project showed that a few hundred decisions by the architect, placed well, do the work, and AI stays on the shelf.

How AI Agents Turned a Bug into an Approved Decision

An agent wrote an implementation limitation into an accepted architecture decision. Another preserved it. When a test exposed the damage, the agents changed the test. I caught it in the summary.

X as Code Is Not a File Conversion: What Must Survive When Engineering Leaves Its Tool?

Architecture may be stored in Rhapsody, requirements in DOORS or Codebeamer, decisions in Word, and interfaces in ARXML. Moving that system to Git is not a serialization problem. It is a decision about which engineering meaning must survive.

Why I’m Building SWCraft: Keeping the Architect in Control of AI-Assisted AUTOSAR Design

SWCraft explores how deeply AI can participate in AUTOSAR architecture development without taking control of the engineering decision.