Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This is a signpost, not a knowledge pack. It carries no source content:
no reproduced clauses, no synthesised summaries of normative text. ISO 26262,
ASPICE, SAE J3016, and UNECE R155/R156 are Excluded under this repo's
docs/SOURCE-VETTING.md (paywalled or no redistribution grant), so none of them
can be reconstituted into a pack. What this skill does: tell you which automotive
standard you want, who owns it, whether it can be packaged, and where to get the
authentic copy.
You need to identify, cite, or locate an automotive standard (e.g. "the
functional-safety standard?" → ISO 26262; "the cybersecurity regulation?" → UNECE
R155). This routes you to the authoritative source. The one genuinely open path in
this catalogue is the nhtsa-vehicle pack (US Government guidance, not an
equivalent of any excluded row).
Prerequisites: none. Plain Markdown.
Find your standard below. The Status column tells you whether it is redistributable:
Where a licence permits citation, the owner's official catalogue page is given in the Status cell.
| Designation | Edition to cite | Owner | Status | Open path |
|---|---|---|---|---|
| ISO 26262 | 2018 series; catalogue anchor ISO 26262-1:2018 | ISO | 🔴 Excluded. https://www.iso.org/standard/68383.html | mil-std-882 for system-safety process (not an equivalent); nhtsa-vehicle for US vehicle safety content |
| ASPICE (Automotive SPICE PAM) | 4.0 | VDA QMC | 🔴 Excluded. https://vda-qmc.de/en/software-processes/automotive-spice/ | none in this catalogue |
| SAE J3016 | 202104 | SAE | 🔴 Excluded. https://www.sae.org/standards/content/j3016_202104/ | nhtsa-vehicle ADS chapter for the US vision document, which is not the J3016 level definitions |
| UNECE R155 | UN Regulation No. 155, cyber security and CSMS | UNECE | 🔴 Excluded. https://unece.org/transport/documents/2021/03/standards/un-regulation-no-155-cyber-security-and-cyber-security | nhtsa-vehicle cyber chapter (US guidance, not R155) |
| UNECE R156 | UN Regulation No. 156, software update and SUMS | UNECE | 🔴 Excluded. Hub https://unece.org/transport/vehicle-regulations · addenda index https://unece.org/transport/vehicle-regulations-wp29/standards/addenda-1958-agreement-regulations-141-160 · exact document slug unconfirmed as of 2026-09-27 | none; no open SUMS pack exists in this catalogue |
| NHTSA vehicle set | Cyber 2022 final, ADS 2.0, FMVSS selections | NHTSA | 🟢 Open. No URL (the content pack carries no source URL, and neither does this row) | pack nhtsa-vehicle |
Signpost content is original JG Systems Consulting Ltd. work, MIT licensed. Trademarks and standard designations are named for identification only.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Knowledge base from CISA Cross-Sector Cybersecurity Performance Goals 2.0. Use for prioritized IT/OT baseline cyber goals aligned to NIST CSF 2.0 (including GOVERN), critical-infrastructure hygiene, MSP/supply-chain expectations, and board-friendly outcome language. Covers CPG 2.0 goals only; does not replace full CSF programs, sector-specific goals (SSGs), or CSET tooling detail.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from DAFMAN 63-119 (15 April 2021), Mission-Oriented Test Readiness Certification. Use for continuous MOTRC replacing single-point OTRR thinking: framework/applicability, Certification Official vs PM roles, review cycle and exit criteria, certification memo/decertify gates, DT&E/contractor evidence, ITT integration and cyber resiliency, and the 31-template matrix. DAF T&E readiness process only—does not replace DoDI 5000.89, AFI 99-103, or multi-service lead policies.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus their focus areas, the document-to-model and design-build-test→model-analyze-build shifts, model formalisms/provenance, governance and access control of the authoritative source of truth, and the coordinate→plan→pilot→sustain rollout. A vision-and-policy strategy, deliberately non-prescriptive. Does NOT provide a how-to method, tool tutorials, MBSE/SysML mechanics, or implementation-plan content; thin on metrics, acquisition-policy detail, and step-by-step procedure. Excludes the CAC-gated Digital Engineering Body of Knowledge (DEBoK).
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the OUSD(R&E) guidebook Implementing a MOSA in DoD Programs (Feb 2025). Use for the Modular Open Systems Approach as a DoD acquisition + design discipline: the statutory/regulatory basis (10 U.S.C. 4401–4403, FY2017/FY2021 NDAA, DFARS), the five OUSD(R&E) pillars, the plan→modularize→identify→define→standardize interface lifecycle, technical levers (WBS/MIL-STD-881F taxonomy, standards profiling, API-first software, COTS/cybersecurity), MOSA assessment metrics and tools (PART/OAAT/KOSS/SEAM/MAUT), technology-change and DMSMS management, roadmaps, MOSA across the six AAF pathways, and contracting/IP/data-rights mechanics. SCOPE LIMITS: this is U.S. DoD weapon-system acquisition policy, not a general open-architecture or interface-standards reference — it names standards (FACE, OMS, DISR) without reproducing them, is light on detailed engineering of any specific standard, and does not cover the underlying SE processes (use dau-se-guidebook / nasa-npr-7123) or general systems-engineering theory (use sebok).
日本語の概要は準備中です。原文の説明を表示しています。