github-featured/tractorjuice--arckit-gemini
2
0
Fork 0
Code Issues Pull Requests Deployments Models Agent Notes Packages Projects Releases Wiki Activity

chore: sync with arc-kit v6.1.7

Browse Source
This commit is contained in:
tractorjuice
2026-07-03 20:15:30 +00:00
committed by GitHub
parent 896ca398be
commit 4d415f7d1f
7 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
VERSION
+1 -1
View File
@@ -1 +1 @@
6.1.6
6.1.7
commands/arckit/uk-nhs-dcb0129.toml
+1 -1
View File
@@ -47,7 +47,7 @@ NHS DCB0129 (\"Clinical Risk Management: its Application in the Manufacture of H
- **Risk level**: `unacceptable` | `high` | `medium` | `low`
- **Status**: `open` | `mitigated` | `accepted` | `closed`
> Note: the DCB0129 scale inverts the usual ArcKit / Orange Book convention where 5 = highest. We follow DCB0129 because that is what CSOs sign off against. Templates carry the legend prominently.
> Note: ArcKit numbers the DCB0129 labels 1 (worst) to 5 (least) to store them; DCB0129 itself puts no numbers on the severity/likelihood axes (word-labelled), and its only numbers are the Risk Class cells (1-5, 5 = unacceptable/highest, the conventional direction). ArcKit keeps the DCB0129 label order because that is what CSOs sign off against; templates carry the legend prominently.
## Process
docs/guides/uk-nhs-dcb0129.md
+1 -1
View File
@@ -27,7 +27,7 @@ The 3 files together implement the four DCB0129 deliverables — Clinical Risk M
- **Risk level**: `unacceptable` | `high` | `medium` | `low`
- **Status**: `open` | `mitigated` | `accepted` | `closed`
> ⚠️ DCB0129 inverts the usual Orange Book convention where 5 = highest. Templates carry the legend prominently.
> ⚠️ **Numbering note (ArcKit encoding, not DCB0129).** ArcKit numbers the DCB0129 labels 1 (worst) to 5 (least) purely to store them. DCB0129 itself puts no numbers on the severity/likelihood axes - they are word-labelled; the only numbers in the standard are the Risk Class cells (1-5, where 5 = unacceptable/highest, the conventional direction). So these ordinals run opposite to both the usual risk-register convention and DCB0129's own risk classes. The templates carry this legend prominently.
## When to use
gemini-extension.json
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "arckit",
"version": "6.1.6",
"version": "6.1.7",
"description": "The Enterprise Architecture Governance Harness - 68 commands across strategy, architecture, delivery, and assurance — including UK Government compliance",
"contextFileName": "GEMINI.md",
"mcpServers": {
templates/uk-nhs-dcb0129-case-template.md
+1 -1
View File
@@ -39,7 +39,7 @@
**Risk levels**: `unacceptable` · `high` · `medium` · `low`
**Hazard status**: `open` · `mitigated` · `accepted` · `closed`
> ⚠️ DCB0129 inverts the usual Orange Book convention where 5 = highest. Read carefully when cross-referencing project risk registers.
> ⚠️ **Numbering note (ArcKit encoding, not DCB0129).** ArcKit numbers the DCB0129 labels 1 (worst) to 5 (least) purely to store them. DCB0129 itself puts no numbers on the severity/likelihood axes - they are word-labelled. The only numbers in the standard are the Risk Class cells (1-5, where 5 = unacceptable/highest, the conventional direction), so these ordinals run opposite to both the usual risk-register convention and DCB0129's own risk classes. Take care when cross-referencing project risk registers.
---
templates/uk-nhs-dcb0129-hazard-template.md
+1 -1
View File
@@ -157,7 +157,7 @@ controls:
- **Risk level**: `unacceptable` | `high` | `medium` | `low`
- **Status**: `open` | `mitigated` | `accepted` | `closed`
> ⚠️ DCB0129 inverts the usual Orange Book convention where 5 = highest. The numbers above carry the opposite meaning from the project risk register.
> ⚠️ **Numbering note (ArcKit encoding, not DCB0129).** ArcKit numbers the DCB0129 labels 1 (worst) to 5 (least) purely to store them. DCB0129 itself puts no numbers on the severity/likelihood axes - they are word-labelled. The only numbers in the standard are the Risk Class cells (1-5, where 5 = unacceptable/highest, the conventional direction), so the ordinals above run opposite to both the usual risk-register convention and DCB0129's own risk classes. Take care when cross-referencing the project risk register.
---
templates/uk-nhs-dcb0160-deployment-hazard-template.md
+1 -1
View File
@@ -232,7 +232,7 @@ controls:
- **Risk level**: `unacceptable` | `high` | `medium` | `low`
- **Status**: `open` | `mitigated` | `accepted` | `closed`
> ⚠️ DCB0129/0160 inverts the usual Orange Book convention. The numbers above carry the opposite meaning from the project risk register.
> ⚠️ **Numbering note (ArcKit encoding, not DCB0129/0160).** ArcKit numbers the DCB0129/0160 labels 1 (worst) to 5 (least) purely to store them. The standard itself puts no numbers on the severity/likelihood axes - they are word-labelled. The only numbers in DCB0129/0160 are the Risk Class cells (1-5, where 5 = unacceptable/highest, the conventional direction), so the ordinals above run opposite to both the usual risk-register convention and the standard's own risk classes. Take care when cross-referencing the project risk register.
---