public
/
docs
5
0
Fork 0
Code Issues 18 Pull Requests 1 Packages Projects Releases Wiki Activity

Define roles for system participants #12

New Issue
Closed
opened 2024-12-01 14:38:18 +00:00 by anton · 3 comments
anton commented 2024-12-01 14:38:18 +00:00
Owner
Copy Link

  • Operators

  • Approvers

  • Witnesses

https://git.distrust.co/public/docs/pulls/10/files#diff-18fdadf0b69aef556c629d0cf6c3d0f1319c76cb

* Operators * Approvers * Witnesses https://git.distrust.co/public/docs/pulls/10/files#diff-18fdadf0b69aef556c629d0cf6c3d0f1319c76cb
anton added this to the Custody Framework project 2024-12-01 14:38:24 +00:00
anton self-assigned this 2024-12-01 14:38:31 +00:00
scjudd commented 2024-12-04 19:26:49 +00:00
Member
Copy Link

@anton

  • What deliverable/milestone is this associated with?
  • When do you anticipate this being done? There is no due date set.
  • This issue is currently in the "Review" column on the board. What is to be reviewed?
@anton - What deliverable/milestone is this associated with? - When do you anticipate this being done? There is no due date set. - This issue is currently in the "Review" column on the board. What is to be reviewed?
anton commented 2024-12-05 20:43:44 +00:00
Author
Owner
Copy Link

@scjudd basically the whole body of documents depends on roles. This document is meant to specify what these roles are in a more clear manner, and this doc will be linked to by a number of other documents which refer to these roles. It's a part of the ongoing refactoring/extension of docs to keep them modular.

This is also basically done (initial draft), and waiting for another team member review.

@scjudd basically the whole body of documents depends on roles. This document is meant to specify what these roles are in a more clear manner, and this doc will be linked to by a number of other documents which refer to these roles. It's a part of the ongoing refactoring/extension of docs to keep them modular. This is also basically done (initial draft), and waiting for another team member review.
anton added this to the Vaulting Framework Documentation milestone 2024-12-06 01:32:27 +00:00
lrvick added reference feat/tamper-proofing-chain-of-custody 2024-12-06 04:05:25 +00:00
anton commented 2024-12-17 19:33:32 +00:00
Author
Owner
Copy Link

The basic roles doc has been completed. Further tickets will be created in order to add details as necessary.

The basic roles doc has been completed. Further tickets will be created in order to add details as necessary.
anton closed this issue 2024-12-17 19:33:32 +00:00
Sign in to join this conversation.
feat/tamper-proofing-chain-of-custody
Branches Tags
Clear current reference
main
feat/tamper-proofing-chain-of-custody
coding-standards
feat/quorum-kms
Clear current reference
Labels
Clear labels   
level-2

   
level-3

   
level-4

   
qvs

Quorum Vaulting System

No Label
level-2
level-3
level-4
qvs
Milestone
Clear milestone
No items
No Milestone
Vaulting Framework Documentation
Projects
Clear projects
No project
Custody Framework
Assignees
Clear assignees
No Assignees
anton
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/docs#12
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?