-
Notifications
You must be signed in to change notification settings - Fork 2
Specs M1 Context Scope
Claude edited this page Aug 28, 2026
·
1 revision
context.models.scope.Scope
Represents the scope covered by the GRC framework.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto-generated | Unique identifier |
name |
string | required, max 255 | Scope name |
description |
text | required | Detailed description of the scope |
version |
string | required | Version of the scope document |
workflow_state |
enum | required, default draft
|
Standardised perimeter lifecycle: draft → definition → validation → in_force → review (periodic, looping back to in_force), with archived as the from-any exit (and restore to draft). in_force and review count in reports and are linkable; only draft is deletable. Runs the standardised lifecycle engine (Scope.LIFECYCLE_NAME = "scope"), not the default workflow. |
boundaries |
text | optional | Scope boundaries and exclusions |
justification_exclusions |
text | optional | Justification of exclusions |
geographic_scope |
text | optional | Geographic scope |
organizational_scope |
text | optional | Organizational scope |
technical_scope |
text | optional | Technical scope |
applicable_standards |
relation | M2M → Referential | Applicable standards |
effective_date |
date | optional | Effective date |
review_date |
date | optional | Next review date |
created_by |
relation | FK → User | Creator |
created_at |
datetime | auto | Creation date |
updated_at |
datetime | auto | Last modification date |
Built from docs/ at v0.36.0. Edits made here are overwritten by the next release : open a pull request against the source instead.
- Administration
- Ask Cairn
- Assets and suppliers
- Compliance
- The dashboard
- Finding your way
- Getting started
- Incidents
- How records move
- Organisational context
- Reports and management review
- Risks
- Trust Center
- Architecture
- Configuration
- Contributing
- The documentation system
- Installation
- Internationalisation
- Operations
- Release process
- Security
- Testing
- Adding an assistant provider
- Adding a dashboard widget
- Adding a domain entity
- Declaring a lifecycle
- Adding an MCP tool
- Adding a REST endpoint
- Adding a report
- Interface conventions
- Dashboard widgets
- Lifecycles
- MCP tools
- MCP tool parameters : Assets
- MCP tool parameters : Compliance
- MCP tool parameters : Governance and context
- MCP tool parameters : General
- MCP tool parameters : Incidents
- MCP tool parameters : Reports and management review
- MCP tool parameters : Risks
- MCP tool parameters : System and administration
- MCP tool parameters : Trust Center
- Management commands
- Models
- Permissions
- REST endpoints
- Environment variables
- MCP server
- REST API
- Assistant module (Ask Cairn)
- Module 0: User Management and Access Control
- Module 1: Context and Organization
- Module 2: Asset Management
- Module 3: Compliance
- Module 4: Risk Management
- Module 4 bis - EBIOS Risk Manager
- Module 5 : Trust Center
- Module 6 : Security Incident Management
- Management review : ISO 27001:2022 compliance (clause 9.3)