Peter Kaloroumakis

Recommend distinguishing between remediation actions since they could be quite varied. In D3FEND we define [Evict](https://d3fend.mitre.org/tactic/d3f:Evict/), [Restore](https://d3fend.mitre.org/tactic/d3f:Restore/), and [Isolate](https://d3fend.mitre.org/tactic/d3f:Isolate/). You could argue even Hardening could be a [remediation](https://d3fend.mitre.org/tactic/d3f:Harden/).

Adding in some of the conversation from OCSF slack for posterity: I think that having Category names being "X Remediation" is not specific enough. For example, our (current) full taxonomy...

> It appears that the "named layouts" feature is gone? https://kit.svelte.dev/docs/layouts#named-layouts - I now get a 404 I thought that was one of the slickest features pre "+layout" svelte-kit.

you have to create a .pipconfig file with the following: ``` [pip-save] use_compatible = false # example setting ```

Thank you for the report, we will get that updated on the next release.

needs a few minor tweaks - [ ] rename tactics to `Credential Access - ATLAS`, add a prefLabel for `Credential Access` > currently: Credential Access (ATLAS Tactic) - [ ]...

* [ ] we're missing "Credential Access - ATLAS - Technique" classes to group their techniques. Like we do here: 

Can you revert the actual ontology changes in this pull so **its just the generative code**. Also, were there any other additions necessary? I think you added the convenience classes...

Yes, this should go under platforms. lets do this next go-round.

This would hang right under External Threat Model Thing. It would not be considered an Attack Thing.