Skip to main content
GPARS home page
Search...
⌘K
Github
Overview
Introduction
Why general-purpose?
Scope
Conformance language
Terminology
Architecture
Architecture
Environment-Modifying Operations
Agent manifest
Agent manifest
Security
Security policy
Enforcement model
Security considerations
Operations
Processing model
Compliance levels
Extension model
Context
Rationale
Non-goals (v0.1)
References
GPARS home page
Search...
⌘K
Ask AI
Search...
Navigation
Overview
Conformance language
Specification
Examples
Specification
Examples
Overview
Conformance language
How to interpret requirement levels in this specification.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, and “MAY” in this document are to be interpreted as described in
RFC 2119
.
Previous
Terminology
Definitions of key terms used in the GPARS specification.
Next
⌘I
Assistant
Responses are generated using AI and may contain mistakes.