#AUTOSAR
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.
Read Post
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.
Read Post
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.
Read Post
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.
Read Post
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.
Read Post
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.
Read Post
My MCP Server Had 39 Tools. I Had Designed It for the Wrong Caller.
SWCraft grew to 39 MCP tools by exposing model operations one tool at a time. Separating the software API from the agent interface reduced the surface to 13 without removing capability.
Read Post
An LLM Wrote the Code. ISO 26262 Doesn't Care — and That's the Point.
ISO 26262 tool qualification never asks who wrote the code, because it never trusted the tool in the first place. If the confidence argument does not depend on the AI being right, AI-assisted development and qualification stop being in conflict.
Read Post
Nothing Changed in the API. Everything Changed for the Agent.
An MCP tool schema explains how to call a function, but not when that function should become a candidate. A task-scoped semantic contract can keep a growing tool catalog behaviorally compatible.
Read Post
An Agent Can Pass Validation and Still Make an Unsafe Change
The agent was authorized to modify one component. It helpfully modified two. The model still validated. Why MCP capability is not task authority, and how a task-scoped mutation boundary closes the gap.
Read Post
Everyone Is Building an AI AUTOSAR Toolchain. But How Should We Evaluate One?
Generating plausible AUTOSAR artifacts is an interesting capability. It is not yet evidence of a production-ready engineering system. We need a way to measure the difference.
Read Post