-
Notifications
You must be signed in to change notification settings - Fork 2
Specs M1 Context Stakeholder
Claude edited this page Aug 28, 2026
·
1 revision
context.models.stakeholder.Stakeholder
Represents any person or organization that can affect, be affected by, or perceive itself to be affected by a decision or activity.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto-generated | Unique identifier |
scope_id |
relation | FK → Scope, required | Linked scope |
name |
string | required, max 255 | Stakeholder name |
type |
enum | required |
internal, external
|
category |
enum | required | See list below |
description |
text | optional | Description |
contact_name |
string | optional | Primary contact name |
contact_email |
string | optional, email format | Contact email |
contact_phone |
string | optional | Contact phone |
influence_level |
enum | required |
low, medium, high
|
interest_level |
enum | required |
low, medium, high
|
expectations |
relation | O2M → StakeholderExpectation | Expectations and requirements |
related_issues |
relation | M2M → Issue | Associated issues |
status |
enum | required |
active, inactive
|
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 |
Stakeholder categories (category values):
executive_management, employees, customers, suppliers, partners, regulators, shareholders, insurers, public, competitors, unions, auditors, other
Note: Categories must be configurable by the administrator.
Sub-entity: expectation of a stakeholder.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto-generated | Unique identifier |
stakeholder_id |
relation | FK → Stakeholder, required | Parent stakeholder |
description |
text | required | Description of the expectation or requirement |
type |
enum | required |
requirement, expectation, need
|
priority |
enum | required |
low, medium, high, critical
|
is_applicable |
boolean | required, default true | Applicable to the scope |
linked_requirements |
relation | M2M → Requirement | Linked compliance requirements (Compliance module) |
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)