Service - Issue - Revision history

Sven the Barbarian at 10:46, 14 February 2026

2026-02-14T10:46:37Z

@@ Line 296: / Line 296: @@
 * Any number of users can add support or disagree for an issue, this will help indicate the importance of the issue to the community
 * no flow required for this, user can create at any time, but maybe have hook/flow that validates user not already added a link
 = Working documents =

2026-02-14T10:46:04Z

disagreeWithIssue

← Older revision		Revision as of 10:46, 14 February 2026
Line 295:		Line 295:

	* Any number of users can add support or disagree for an issue, this will help indicate the importance of the issue to the community		* Any number of users can add support or disagree for an issue, this will help indicate the importance of the issue to the community
			* no flow required for this, user can create at any time, but maybe have hook/flow that validates user not already added a link

	= Working documents =		= Working documents =

2026-02-14T10:44:53Z

Object Relationships

@@ Line 258: / Line 258: @@
 </syntaxhighlight>
-* Any number of users can add support for an issue, this will help indicate the importance of the issue to the community
+=== disagreeWithIssue ===
 = Working documents =

2026-02-14T10:42:17Z

juror

@@ Line 91: / Line 91: @@
 		status: {
 			type: "string", // pending|invalid|confirmed is pending until user confirms, if request expires is invalid and a new juror is attempted
 			canUpdate: true,
 			storageResourceTags: ['myGraph']

2026-02-14T10:41:42Z

Notes

← Older revision		Revision as of 10:41, 14 February 2026
Line 11:		Line 11:
	* have levels of users to create levels of appeal, eg first level jury, appeal to a higher level jury sorted from senior or skilled users, then final appeal where the entire community can vote if the decision/s should be overturned		* have levels of users to create levels of appeal, eg first level jury, appeal to a higher level jury sorted from senior or skilled users, then final appeal where the entire community can vote if the decision/s should be overturned
	* initially punishments can be informally decided on inside the comment thread, then have another forum where admins are tasked with actioning decisions. In the future these could be formalized into standard flows depending on how the community develops.		* initially punishments can be informally decided on inside the comment thread, then have another forum where admins are tasked with actioning decisions. In the future these could be formalized into standard flows depending on how the community develops.
			* in future integrate range choice voting, for now jurors decide how to complete the issue, any juror can complete/acquit
			* after completion it is a juror's responsibility to pass the decision to admins, eg have forum for this work

	= Repository =		= Repository =

2026-02-14T10:00:40Z

issue

← Older revision		Revision as of 10:00, 14 February 2026
Line 47:		Line 47:
	type: "string", // list/boolean? acquitted\|pending\|complete		type: "string", // list/boolean? acquitted\|pending\|complete
	canUpdate: true,		canUpdate: true,
			storageResourceTags: ['myGraph']
			}
			numberOfJurors: {
			type: "integer",
	storageResourceTags: ['myGraph']		storageResourceTags: ['myGraph']
	}		}

2026-02-14T09:51:33Z

Notes

← Older revision		Revision as of 09:51, 14 February 2026
Line 7:		Line 7:
	= Notes =		= Notes =

	* jurors could be rewarded with tokens that can be traded and used be sellers to increase exposure of their listings		* jurors could be rewarded with tokens that can be traded and used by sellers to increase exposure of their listings
	* users can opt-in/out of being available for jury selection		* users can opt-in/out of being available for jury selection
	* have levels of users to create levels of appeal, eg first level jury, appeal to a higher level jury sorted from senior or skilled users, then final appeal where the entire community can vote if the decision/s should be overturned		* have levels of users to create levels of appeal, eg first level jury, appeal to a higher level jury sorted from senior or skilled users, then final appeal where the entire community can vote if the decision/s should be overturned

2025-08-11T01:49:35Z

@@ Line 27: / Line 27: @@
 	objectType: "issue",
 	canDelete: false,
 	storageResources: {
 		myGraph: {
@@ Line 129: / Line 133: @@
 					linkType: "one",
 					requiredOnCreate: true,
 				},
 				to: {
@@ Line 169: / Line 172: @@
 					},
 					linkType: "many",
 				},
 				to: {
@@ Line 177: / Line 179: @@
 					},
 					linkType: "many",
+				}
+			}
@@ Line 197: / Line 198: @@
 			myGraph: {
 				storageType: "graph",
 				graphServerTag: "GraphHandler"
+			}
 		},
@@ Line 209: / Line 210: @@
 					},
 					linkType: "many",
 				},
 				to: {
@@ Line 216: / Line 216: @@
 						objectType: "user"
 					},
 					linkType: "one"
+				}
+			}
@@ Line 225: / Line 225: @@
 * Link Juror object to it's user, one juror has one isJuror link
 = Working documents =

2025-05-22T03:03:04Z

← Older revision		Revision as of 03:03, 22 May 2025
Line 10:		Line 10:
	* users can opt-in/out of being available for jury selection		* users can opt-in/out of being available for jury selection
	* have levels of users to create levels of appeal, eg first level jury, appeal to a higher level jury sorted from senior or skilled users, then final appeal where the entire community can vote if the decision/s should be overturned		* have levels of users to create levels of appeal, eg first level jury, appeal to a higher level jury sorted from senior or skilled users, then final appeal where the entire community can vote if the decision/s should be overturned
			* initially punishments can be informally decided on inside the comment thread, then have another forum where admins are tasked with actioning decisions. In the future these could be formalized into standard flows depending on how the community develops.

	= Repository =		= Repository =

2025-05-20T10:06:46Z

@@ Line 13: / Line 13: @@
 = Repository =
-https://bitbucket.org/izara-core-shared/izara-core-shared-issues
+https://bitbucket.org/izara-core-shared/izara-core-shared-issue
 = Object Schemas =
@@ Line 224: / Line 224: @@
 * Link Juror object to it's user, one juror has one isJuror link
 = Working documents =