ERP HRM · WORD DOCUMENT VIEW · V1.0c

عرض الـUser Stories بنفس ملف الـWord

طريقة عرض إضافية لا تستبدل التحليل الحالي: اختر الإدارة ثم الـEpic، وستظهر كل القصص تحته بنفس ترتيب الصفوف وألوان المصدر.

العودة للتحليل الفني

171 Story معتمدة في V1.0c2 إضافة نظام خارج الملف1 · 3 · 5 Epics مذكورة في سجل تحديث V1.0c

الإدارةEpic / Module

EPIC DOCUMENT · كل القصص في صفحة واحدة

Reliable Integration Gateway

0 من المصدر المعتمد

User StoryDescriptionAcceptance CriteriaField ValidationJourneyScenarios

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Transactional Outbox from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-060Canonical SRS Graph

As a Integration Operator, I want to manage Transactional Outbox from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Transactional Outbox from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـTransactional Outbox، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Transactional Outbox ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Inbound Inbox & Idempotency from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-061Canonical SRS Graph

As a Integration Operator, I want to manage Inbound Inbox & Idempotency from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Inbound Inbox & Idempotency from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـInbound Inbox & Idempotency، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Inbound Inbox & Idempotency ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Versioned Event Envelope from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-062Canonical SRS Graph

As a Integration Operator, I want to manage Versioned Event Envelope from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Versioned Event Envelope from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـVersioned Event Envelope، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Versioned Event Envelope ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Connector Configuration & Secret Rotation from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-063Canonical SRS Graph

As a Integration Operator, I want to manage Connector Configuration & Secret Rotation from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Connector Configuration & Secret Rotation from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـConnector Configuration & Secret Rotation، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Connector Configuration & Secret Rotation ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Retry, DLQ & Controlled Replay from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-064Canonical SRS Graph

As a Integration Operator, I want to manage Retry, DLQ & Controlled Replay from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Retry, DLQ & Controlled Replay from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـRetry, DLQ & Controlled Replay، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Retry, DLQ & Controlled Replay ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Sync Jobs & Checkpoints from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-065Canonical SRS Graph

As a Integration Operator, I want to manage Sync Jobs & Checkpoints from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Sync Jobs & Checkpoints from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـSync Jobs & Checkpoints، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Sync Jobs & Checkpoints ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Reconciliation & Drift Detection from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-066Canonical SRS Graph

As a Integration Operator, I want to manage Reconciliation & Drift Detection from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Reconciliation & Drift Detection from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـReconciliation & Drift Detection، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Reconciliation & Drift Detection ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

SAME DOCUMENT LAYOUT

As a Integration Operator, I want to manage Conflict Resolution Queue from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

Reliable Integration Gateway

CORE-067Canonical SRS Graph

As a Integration Operator, I want to manage Conflict Resolution Queue from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

User Story

As a Integration Operator, I want to manage Conflict Resolution Queue from the Core workspace so that the ERP operation is secure, traceable and integration-ready.

بصفتي Integration Operator، أريد أن أدخل إلى مساحة Reliable Integration Gateway وأقوم بـConflict Resolution Queue، لكي أنفّذ العمل بأمان وأحصل على نتيجة قابلة للتتبع والربط مع موديولات ERP.

Description

Acceptance Criteria

Given مستخدم مصرح وبيانات صحيحة، When ينفذ العملية، Then تظهر النتيجة داخل نفس الـالشركة / مساحة العمل.
لا يقبل الـAPI أي Write دون Validation وصلاحية وCorrelation ID.
التغيير ينتج Audit وHistory/Event حسب العقد ولا يتكرر عند Retry.
Permission وDuplicate وStale Version وProvider Failure لها Errors قابلة للاختبار.

Field Validation

Record ID	UUID / String	No	Unique and immutable after creation
Company	Reference	Yes	Required and must match the user scope
Branch	Reference	No	Must be active and permitted for the user
Status	Enum	No	Allowed enum only; transitions require permission
Created By	User Reference	No	Server-generated; client value is rejected
Created At	UTC DateTime	No	Stored in UTC and displayed in user timezone
Correlation ID	String	No	Unique per run and propagated across steps
Source System	Enum / Reference	Yes	Active integration with supported contract version
External ID	String	Yes	Unique per source system and never reused for another record
Schema Version	Semantic Version	Yes	Unsupported versions are quarantined without writes
Idempotency Key	String	Yes	Unique per operation; replay returns the same result

Dropdown / Select Options (DDL)

—

User Journey

ينفذ Integration Operator سيناريو Conflict Resolution Queue ببيانات معتمدة، ويثبت الـEvidence أن الصلاحيات والنتيجة والـAudit/Event صحيحة.

Scenarios

Happy Path + Required Fields
Unauthorized / Cross-company workspace / Masked Fields
Boundary + Duplicate + Concurrent Update
Retry / Idempotency / Audit-Event Integrity
Positive / Happy path ببيانات صحيحة
Negative validation للحقول المطلوبة
Boundary للقيم والتواريخ والأحجام
Permission وRole وRow security
Business rules وInvalid state transition
API contract وError schema

Alternative Path

—

Edge Cases

—

QPENTASCOPE

جاري تجهيز مساحة العمل

بنحمّل الواجهة والبيانات المطلوبة فقط.

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result

Record ID

UUID / String

Unique and immutable after creation

Company

Reference

Yes

Required and must match the user scope

Branch

Reference

Must be active and permitted for the user

Status

Enum

Allowed enum only; transitions require permission

Created By

User Reference

Server-generated; client value is rejected

Created At

UTC DateTime

Stored in UTC and displayed in user timezone

Correlation ID

String

Unique per run and propagated across steps

Source System

Enum / Reference

Yes

Active integration with supported contract version

External ID

String

Yes

Unique per source system and never reused for another record

Schema Version

Semantic Version

Yes

Unsupported versions are quarantined without writes

Idempotency Key

String

Yes

Unique per operation; replay returns the same result