Repository navigation
Group the use cases and make the Use Cases section their home - #64
Merged
Merged
Conversation
ozzyathome
commented
Oct 4, 2026
ozzyathome
commented
Collaborator
- Group the use cases, add placeholders, and draft substation automation
- Draft a procurement profile and apply it to the Keycloak document
- Make the Use Cases section the home of use cases and worked examples
Draft decision 0023 groups use cases by their relation to the interface disclosure baseline: disclosure profiles select and tighten baseline facts, change-planning profiles add capability facts and share a change core. The subject is shown as a second axis; sector is not a grouping. The CI quality gate and change impact between versions move to "Applying a profile". - Use-case index and catalogue regrouped; entries 10 to 16 added as placeholders (managed service disclosure, service assurance, substation automation, PKI estate, code and firmware signing, stored data, shared-trust networks). Catalogue numbers are kept as identifiers. - A second emphasis table compares change-planning use cases across the core. - Maturity names the overlay as a fourth relation. - Q64 gets a proposed answer (Option C via a sibling core); Q66 to Q68 added. - drafts/ot-substation: the substation automation use case (entry 12), with a component profile on the change core and a system overlay (draft 0024). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DwbcVStMBfden6Ch4FMHrn
pkic.example.procurement v0.1 extends the interface disclosure baseline v0.8 draft. It narrows accepted lifecycle stages, removes withholdability from I9, and adds P5 (a storage interface for keys at rest, or a stated reason for none) and P6 (coverage all or all-external). Well-formed under C1 to C17 with --strict. It is applied unchanged to the Keycloak migration document, the first worked example in the disclosure group. A failing example removes the storage interface. Expected verdicts are checked by reading; the published validator cannot yet read services (K7) or inherit through provides (K9), as for the migration examples. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DwbcVStMBfden6Ch4FMHrn
ozzyathome
added a commit
that referenced
this pull request
Oct 4, 2026
* Add the PQC migration depth drafts and decision 0022 Working drafts for draft decision 0022: the interface enumeration v0.2, interface disclosure v0.8, pqc-migration v0.7 and pqc-migration-extended v0.1 rules files, the four Keycloak 26.7.3 example documents, the draft CycloneDX mapping and native-fields review, the CycloneDX 2.0 initial analysis, and the plan they were written from. Nothing here is published by the site. open-questions.md records where 0022 bears on two open items (K9 and K10). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DwbcVStMBfden6Ch4FMHrn * Group the use cases and make the Use Cases section their home (#64) * Group the use cases, add placeholders, and draft substation automation Draft decision 0023 groups use cases by their relation to the interface disclosure baseline: disclosure profiles select and tighten baseline facts, change-planning profiles add capability facts and share a change core. The subject is shown as a second axis; sector is not a grouping. The CI quality gate and change impact between versions move to "Applying a profile". - Use-case index and catalogue regrouped; entries 10 to 16 added as placeholders (managed service disclosure, service assurance, substation automation, PKI estate, code and firmware signing, stored data, shared-trust networks). Catalogue numbers are kept as identifiers. - A second emphasis table compares change-planning use cases across the core. - Maturity names the overlay as a fourth relation. - Q64 gets a proposed answer (Option C via a sibling core); Q66 to Q68 added. - drafts/ot-substation: the substation automation use case (entry 12), with a component profile on the change core and a system overlay (draft 0024). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DwbcVStMBfden6Ch4FMHrn * Draft a procurement profile and apply it to the Keycloak document pkic.example.procurement v0.1 extends the interface disclosure baseline v0.8 draft. It narrows accepted lifecycle stages, removes withholdability from I9, and adds P5 (a storage interface for keys at rest, or a stated reason for none) and P6 (coverage all or all-external). Well-formed under C1 to C17 with --strict. It is applied unchanged to the Keycloak migration document, the first worked example in the disclosure group. A failing example removes the storage interface. Expected verdicts are checked by reading; the published validator cannot yet read services (K7) or inherit through provides (K9), as for the migration examples. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DwbcVStMBfden6Ch4FMHrn --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.