S Silkwit Briefs 2026-05-13 — AM

Context

Mid-week position check. Three parallel tracks are active: outbound regulatory scoping for AV technology, silkwit infrastructure expansion (briefs.silkwit.com now going live), and vault knowledge compilation. Munich assignment is approximately 8 weeks away — the clock on German regulatory registration, passport renewal, and family logistics is running.

Priority matrix

01 — Immediate Finalize outbound scope document; continue EU regulatory structure deep-dive
02 — This week Ship briefs.silkwit.com; connect vault daily-review to brief rendering pipeline
03 — Ongoing Maintain standards.silkwit.com content loop; monitor WP.29 GRVA updates
04 — Background Munich logistics: visa, passport (renewal window), notarization, child care enrollment

Track A — AI / AV / Robotics

Autonomous driving outbound scope

Primary research question: what regulatory dimensions govern AV technology export from EU to third countries, and which actors hold authority at each step?

  • EU export control framework: dual-use regulations, EU 2021/821 (recast)
  • UNECE WP.29: type approval for vehicles — non-EU manufacturers face R155/R156 compliance
  • Germany's Federal Motor Transport Authority (KBA): L4 AV approval pathway under EU 2022/1426
  • Key actors identified: European Commission (DG GROW), UNECE WP.29/GRVA, national type approval authorities
  • Open question: how does China's GB/T standards interact with EU AV certification for cross-border deployment?
Next action: Draft the actor-map section; cross-reference with OICA public positions

Track B — Standards & Regulation

EU regulatory structure: three-layer map

The EU regulatory stack for automated driving operates across three distinct horizontal layers that must be understood separately before mapping their interactions.

Horizontal AI

EU AI Act — risk classification, prohibited AI, high-risk system requirements

Vehicle Approval

EU 2022/1426 — L4 ADS approval procedure; UNECE WP.29 integration

Cybersecurity

R155 (CSMS), R156 (SUMS) — mandatory for type approval from 2024

These three layers interact in practice: an L4 ADS must satisfy the EU AI Act's high-risk requirements and obtain type approval under EU 2022/1426 and demonstrate compliance with R155 CSMS. They are not alternatives — they stack.

Track C — Engineering & Infrastructure

Silkwit network status

silkwit.com Live — static HTML + CSS, Cloudflare Pages Live
standards.silkwit.com Live — static HTML, Cloudflare Pages Live
briefs.silkwit.com Deploying today — first static prototype Deploy
files.silkwit.com Live — Cloudflareimgbed Worker, R2 backend Live
labs.silkwit.com Not started Planned
Vault-to-brief pipeline: Next milestone. Requires daily-review render script + optional KV state for tracking last-sync date.

Open questions

  1. Does EU 2021/821 dual-use regulation actually apply to AV software (as opposed to hardware sensors)? Is there a definitive ruling or only guidance?
  2. For the brief rendering loop: push model (vault triggers build on daily-review save) or pull model (Cloudflare Pages polls vault on request)? Which has lower friction for your workflow?
  3. Should briefs.silkwit.com eventually be authenticated, or remain public as a portfolio signal?