01name: Chassis
02title: Chassis
03ports:
04 - name: rOperatingState
05 direction: require
06 interface: IVehicleOperatingState
07members:
08 - name: BrakeSubsystem
09 composition: BrakeSubsystem
10 - name: BrakeController
11 type: BrakeController
12 - name: RearBrakeSensor
13 type: BrakeTemperatureSensor
14delegations:
15 - name: DelegateOperatingState
16 port: rOperatingState
17 member: BrakeSubsystem
18 member_port: rOperatingState
Architecture as Code for AUTOSAR Classic
Make architecture
reviewable like code.
Import existing AUTOSAR ARXML or declare your architecture as YAML in Git. Bring in requirements, trace them to the design, and assess changes across the hierarchy, cores and partitions. Review assistant proposals before they land, then generate checked ARXML, diagrams and traceability documentation.
- YAMLdeclared hierarchy
- ARXMLimport and export
- Local-firstno service to run
01 / One source of truth
One model.
Every artefact.
Components, their hierarchy, the diagrams and the ARXML stop being documents that agree by discipline. They are derived from one model, with validation controlling the ARXML handoff.
AUTOSAR
ARXML
UML / SysML
Diagrams
Sphinx-Needs
Traceability
Architecture
Change report
Architecture with a shape
One explicit root contains named component and composition instances, with boundary ports delegated through the hierarchy.
Checked as a whole
References, interface compatibility, task and partition mappings, resource budgets, safety levels and AUTOSAR identifiers are validated across fifteen layers.
Downstream stays put
The existing downstream toolchain remains on the ARXML path. SWCraft moves the reviewable source of truth upstream.
02 / Deterministic gate
Invalid architecture stops here.
Model errors stop generation before it begins. Warnings stay visible, and project policy can make them blocking too. The final ARXML check states whether it used a licensed XSD or structural checks; a rejected file remains on disk and must not be handed downstream.
$ swcraft check-model --project swcraft.yaml
checking architecture model...
FINDING SWC 'BrakeController' port 'rBrakeRequest'
references interface 'IBrakeRequest' which is not declared
REFUSED model unchanged · nothing generated
Structure
Root composition, member placement, delegation compatibility and hierarchy cycles.
Execution and trace
Task mappings, runnable access points and sequences; requirement references, derivation cycles and links needing confirmation.
Resources
CPU thresholds, memory budgets and core-to-memory accessibility.
Below the VFB
Cores, the partitions on them and their trust class, memory reach, and every task placed in a partition.
Safety levels
Component against requirement, partition, core and memory, with decomposed levels such as B(D) compared by their own rule.
AUTOSAR
Generated identifier legality and optional validation against a licensed 4.2.2 or 4.3.0 XSD.
03 / Constrained assistance
The LLM proposes.
SWCraft determines.
A human decides.
The assistant proposes one complete change through SWCraft's MCP tools. SWCraft checks it on a private copy and opens a review tab in VS Code: the same Approve or Reject decision for Copilot, Codex and Claude. A proposal that would weaken a check needs a second, separate approval.
-
01
Plain-language request
Describe the outcome, not the files.
-
02
One atomic proposal
Every related element arrives together.
-
03
Shadow validation
The real model stays untouched.
-
04
Exact semantic diff
Review what will land, not a summary.
-
05
Review tab
Approve all of it or apply nothing.
Pending Change Sets keeps unanswered reviews within reach. The SWCraft Architect profile has no file editing or terminal tools; other clients use model guards with documented limits. These are guardrails, not a sandbox. Panel review assumes the assistant is confined to the project folder.
04 / Migration proven on real exports
Import first.
Remodel nothing.
An ARXML export from the current toolchain imports into a readable Git model. The report names every value the import does not carry, and what comes back out is compared with what went in.
Software components
Every one with its ports, runnables and events.
Interfaces
240 of them stubs for platform software the export references but does not contain.
Connectors
Assembly and delegation connectors, followed through the compositions.
Compositions
The hierarchy kept as declared, root to leaf.
Zero unexplained differences. Output against input on two real exports: every difference is one of a short, published list grounded in the AUTOSAR text, or a line in the import report.
Every component round-trips. Each component exports on its own and imports back, and SWCraft's own exports import whole.
05 / Incremental adoption
Start small.
Keep control.
Introduce Architecture as Code around a bounded slice. Keep the existing engineering flow in place and evaluate the model, checks and generated handoff on their own merits.
Bounded slice
Choose a contained subsystem or component group instead of committing to a broad migration.
Separate Git model
Build the reviewable source alongside the current process, with no production repository change required.
Checked handoff
Only a validated ARXML artefact crosses the boundary into the downstream toolchain.
Decide from the result
Review the Change Report: introduced findings, requirement links, resource use, ARXML changes and diagrams before and after.
No big-bang replacement. SWCraft is introduced upstream of the existing toolchain. Its value can be reviewed on a controlled scope before any wider adoption decision.
06 / The architecture workbench
Model, trace and assess the change.
Guided authoring
Completion and schema diagnostics, Go to Definition, references, outline and diagram links keep the YAML model navigable in VS Code.
EDITORRequirements and trace links
Import requirements through a defined JSON interchange profile. Track versions, review proposed architecture links and confirm them again when requirements change.
IMPORT · TRACE LINKS · SPHINX-NEEDSChange Report
See changed elements, introduced findings, trace links, resource use and ARXML changes, with composition diagrams before and after. Computed from the model.
MARKDOWN · JSON · DIAGRAMSImpact analysis
Open Impact on the element under the cursor. Dependents are grouped by layer, with the path that reaches each one and a jump to its definition.
VS CODE VIEW · CLI · READ ONLYResources and fit
Inspect each core and memory with its consumers. Ask whether a proposed load fits both the configured threshold and the physical capacity.
RESOURCES VIEW · CPU · MEMORYAllocation experiments
Explore where components could move between partitions to reduce exchanged data. Compare checked candidates and their assumptions before choosing a change.
REPORT · JSON · MODEL UNCHANGEDControlled assistance
Ask about signals, requirements, impact or budgets through the model API. Review a staged change in VS Code; only an affirmative decision commits it.
MCP · REVIEW TAB · HUMAN DECISIONARXML import and exchange
Import a whole export or one component with an explicit loss report. Export the model or one component with its required interfaces and types.
ARXML 4.2.2 · 4.3.0Guide that ships
Version-matched documentation and generated reference, served locally. A finding's rule in Problems opens the guide at that check.
OFFLINE07 / Developing SWCraft with Carchetype
Reproduce the shape.
Test the behaviour.
Architecture tools need tests that reflect how models are actually structured. Carchetype generates reproducible synthetic models with declared properties, helping us find, investigate and prevent defects in SWCraft itself.
Known data. Checkable answers.
A component with hundreds of ports, an interface used across the model, or deeply nested compositions can expose problems a small, evenly connected example misses. Carchetype creates models with specified structural characteristics for functional tests of SWCraft.
Scenarios exercise SWCraft's actual commands and model tools. Expected answers come from the generated data independently of the function under test. Reproducible cases become regression checks for future changes.
Your architecture stays with you.
When a project cannot leave your organisation, a model passport offers a way to investigate a problem together. It records counts, distributions and lengths without element names, requirement text or source values. You can inspect it before sharing.
For supported passports, Carchetype generates a synthetic model with the stated characteristics. We can use that model to investigate structure-dependent problems and develop repeatable tests while your source architecture stays on your machine.
- 01Model passport
- 02Carchetype specimen
- 03Reproducible scenario
- 04Regression test
The passport describes structure. A problem that depends on a particular name, text or a relationship the passport does not record may need an additional synthetic example. This approach improves SWCraft's own development and testing.
08 / Project status · Current release: 0.20.0
Working prototype.
The architecture loop is implemented. SWCraft covers ARXML and requirements import, authoring, traceability, deterministic checks, change assessment and reviewed AI-assisted edits. Evaluate it on a bounded architecture slice alongside the existing AUTOSAR toolchain.
Reviewable source
A Git-native YAML model in fifteen layers: components, interfaces, connectors, compositions, seven data-description layers, tasks, sequences, requirements, and hardware with cores, partitions and memories.
Deterministic gate
Structure, budgets, safety levels, partitions and trace links, with errors and warnings in Problems. ARXML validation states its mode; Build can write a computed report of outputs, findings, resources and ARXML changes.
Generated evidence
ARXML 4.2.2 and 4.3.0, local SVG and HTML diagrams, Sphinx-Needs traceability documentation, Change Reports, impact and model queries. Allocation and trace-link experiments support the next design decision.
Integrated workspace
Release archives for Linux and Windows carry the CLI, VS Code extension, MCP integration, assistant, guide and runtimes for offline installation. The release gate runs on both platforms.
09 / Product demonstration
See the workflow.
Synthetic showcase model · 6 minutes · captions · no audio
- 01
ModelYAML, the editor and the gate
- 02
ViewsDiagrams, partitions and the guide
- 03
ChangeRefusal, exact delta, human decision
- 04
QuestionsDiff, impact, query and resources
A bounded first step
Bring one architecture slice.
Leave with evidence.
Start from existing architecture or an empty project. Keep the model in its own Git repository; the ARXML it emits is the only thing the downstream toolchain needs to see.
Access is granted per e-mail address by the author. Approved addresses download the current release for Linux and Windows after a one-time code by e-mail. Privacy notice.
Request accessSay what you want to try; confirm your e-mail.
Install and import or modelOne archive per machine; a representative, bounded slice.
Validate and assessTrace requirements, inspect changes and build checked outputs.
Review the evidenceDecide what fits your engineering process.
SWCraft is developed with a tool-qualification path in mind; it is not a qualified tool. Licensed AUTOSAR XSD schemas are not distributed with it.