Glossary and Terminology Updates

[ottosulin]

Creating this issue here for discussion.

For any topic of a focus area we should aim for generic terminology so that it's more future-proof. This is important because the technology is evolving fast, and new paradigms and patterns will emerge probably every year, but for AISVS users it will be more challenging if we have to change the topic wording constantly.

Some examples:

• "Autonomous loop bounding" -> "Enforce resource boundaries"
• "Protocol‑level misuse protection" -> "Data validation"
• "Tool plugin sandboxing" -> "Component sandboxing"
• "Agent task planning & re‑entrancy control" -> "Agent workflow control"

[jmanico]

Otto - I would love your help maintaining the Glossary here https://github.com/OWASP/AISVS/blob/main/1.0/en/0x90-Appendix-A_Glossary.md throughout the process. Please help us keep our terminology robust!

[jmanico]

Creating this issue here for discussion.

For any topic of a focus area we should aim for generic terminology so that it's more future-proof. This is important because the technology is evolving fast, and new paradigms and patterns will emerge probably every year, but for AISVS users it will be more challenging if we have to change the topic wording constantly.

Some examples:

• "Autonomous loop bounding" -> "Enforce resource boundaries"
• "Protocol‑level misuse protection" -> "Data validation"
• "Tool plugin sandboxing" -> "Component sandboxing"
• "Agent task planning & re‑entrancy control" -> "Agent workflow control"

I agree, if we have any mistakes in the current Categories file please give us a PR!

[ottosulin]

@jmanico I think we should revisit this discussion on how much we want "generalize" the wording of topics once we feel like the categories are finalized.

I would prefer to keep this issue open for now so that other reviewers would not create duplicate issues about this.

[jmanico]

You got it! Good idea. :)

[jmanico]

I propose removing the amorphous term provenance here: #87