Tearing down the wall between quality and engineering.
Open-source DevOps scaffolding for automotive software — SDV, AI-defined vehicles, autonomous systems — that answers the question the whole industry is stuck on: how can agentic engineering and rigorous quality — ASPICE, ISO 26262 — work alongside each other?
Today they're treated as enemies. Agents move fast and can't show their work; quality shows its work and can't move. They were only ever enemies because evidence was manual. When compliance emerges from the pipeline as a continuous artifact — not after-the-fact documentation — engineers, AI agents, and assessors consume the same ground truth. The wall doesn't get climbed. It gets deleted.
One loop. One ground truth.
Engineers and agents commit against a single ground truth; the pipeline turns every merge into evidence; quality reads the same state engineering produces — and the context packs close the loop by feeding that state back to the agents.
A reference scaffolding for speed inside the standards.
- A reference repo layoutRequirements-as-code, architecture-as-code, tests, and safety artifacts living next to the code they justify.
- CI/CE pipeline templatesEmit compliance evidence on every merge: traceability (requirement → code → test), change impact, review records, capability-level coverage — assessment-ready at every commit.
- Thin open adaptersInto the tools teams already use — ALM, systems engineering, testing & simulation, embedded — so the scaffold breaks silos instead of adding one.
- Context packs for AI coding agentsMachine-readable project context — requirement slices, architecture views, the ASPICE practices and ISO 26262 clauses that apply to the work product being changed — so agents operate inside the regulated context instead of blind to it.
Neutrality is the point.
- Not a tool.No SaaS, no seat licenses, no lock-in.
- Not an ALM.It connects to yours instead of replacing it.
- Not a consultancy pitch.The manifesto, layout, and pipeline templates are MIT-licensed and public.
- Not exclusive to any vendor.Deliberately tool-agnostic and non-exclusive — the adapters are thin and open.
Early. The manifesto and layout come first, then one working pipeline template (traceability report on a toy SDV example), then adapters — in the open, iteratively. Watch the repo; contribute a silo you hate.
Delete the wall with us.
Curated in the open by The New Automotive — the marketplace for modern automotive software tooling.