@dreamteamer/roles 0.0.0-stage → 0.1.0

package/README.md

@@ -1,3 +1,13 @@
-# Temporary Holding Version
+# @dreamteamer/roles
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The positions people hold — team leader, backend developer, product manager, QA engineer — as one
+list the whole workspace shares. A person lists the roles they hold on `users.roles` (an overlay this
+module adds to users), and each role lists its people back, generated. A role is a position, never a
+task and never an area of ownership (that is `@dreamteamer/responsibilities`).
+
+```bash
+npm install @dreamteamer/roles @dreamteamer/users
+npx dreamteamer compile
+```
+
+Until core 0.12.0 this shipped inside `@dreamteamer/core`; records stay in `data/roles/` under the same ids.

package/UPDATING.md

@@ -0,0 +1,19 @@
+# Updating @dreamteamer/roles
+
+One section per release, newest first. Each says what you have to **do** in a workspace that
+installs this module; most of the time it is `dt compile`, then `dt check`.
+
+```bash
+npm install @dreamteamer/roles@latest
+npx dreamteamer compile
+npx dreamteamer check
+```
+
+---
+
+## 0.1.0 — out of core, a package of its own
+
+`roles` shipped inside `@dreamteamer/core` through 0.11; from core 0.12.0 core is a preset of the small
+modules and this is one of them. The descriptor moved verbatim — the same fields, the same storage path
+and the same id shape — so no record moves and nothing is migrated. A workspace that updates core gets
+this package as a preset member; nothing to do but `dt compile`.

package/collections/roles.collection.yaml

@@ -0,0 +1,64 @@
+# roles — the positions people hold, as one list the whole workspace shares.
+name: roles
+description: >-
+  A position a person holds — team leader, backend developer, product manager, QA engineer. One record per role; a person lists the roles they hold on `users.roles`.
+use_when: >-
+  a person's position is named — find or create the role here, then list it on the person's `roles`; asked "who are the backend developers", list users filtered by role
+storage:
+  path: data/roles
+  format: md
+  suffix: role
+ids:
+  from: '{{ name | slug }}'
+  pattern: ^[a-z0-9][a-z0-9-]*$
+fields:
+  name:
+    type: string
+    required: true
+    description: The role as the workspace says it — "team leader", "backend developer".
+  description:
+    type: string
+    description: What the role covers, in one line.
+  users:
+    type: users
+    many: true
+    mirror_of: roles
+    description: GENERATED — who holds this role. Set `roles` on the user.
+  notes:
+    type: markdown
+    body: true
+    description: Expectations, scope, how the role is filled.
+  tags:
+    type: string
+    many: true
+    examples: ['onboarding', 'client:northwind']
+    pattern: ^[a-z0-9]+(-[a-z0-9]+)*(:[a-z0-9]+(-[a-z0-9]+)*)?$
+    description: Free labels, lowercase and hyphenated, optionally key:value with no space around the colon.
+  author:
+    type: string
+    examples: ['agents/claude-code', 'scripts/read-git@2']
+    pattern: '^(agents|scripts)/[a-z0-9][a-z0-9-]*(@[a-z0-9][a-z0-9./-]*)?$'
+    description: >-
+      Which agent or script wrote this record: `agents/<harness>`, or `scripts/<name>@<version>` for a reader. Absent when a person wrote it. The model, when it matters, goes in `creation_context`.
+  creation_context:
+    type: string
+    description: How and why this record came to be, in one line — and the reason whenever confidence is low.
+  source:
+    title: Information source
+    type: string
+    description: 'Where the INFORMATION came from, prefixed so it stays machine-readable: <collection>/<id> · file:<path> · url:<…> · migration:<id>.'
+  confidence:
+    type: string
+    default: normal
+    enum: [low, normal, high]
+    description: How much to trust this record. When low, the reason goes in creation_context — there is no separate note field.
+display:
+  nav:
+    icon: symbol-class
+  list:
+    columns: [name, description, users]
+  form:
+    sections:
+      - title: Provenance
+        fields: [author, creation_context, source, confidence]
+        collapsed: true

package/collections/users.collection.yaml

@@ -0,0 +1,8 @@
+# OVERLAY of users — the roles a person holds, so "who are the backend developers" is a filter.
+name: users
+overlay: true
+fields:
+  roles:
+    type: roles
+    many: true
+    description: The positions they hold — `roles` records, one list the whole workspace shares.

package/package.json

@@ -1,6 +1,32 @@
 {
-  "name": "@dreamteamer/roles",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+	"name": "@dreamteamer/roles",
+	"version": "0.1.0",
+	"description": "The positions people hold — team leader, backend developer — as one shared list each person names on users.roles.",
+	"license": "Apache-2.0",
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/dreamteamer/dreamteamer-modules.git",
+		"directory": "modules/roles"
+	},
+	"keywords": [
+		"dreamteamer",
+		"dreamteamer-module",
+		"roles"
+	],
+	"files": [
+		"README.md",
+		"UPDATING.md",
+		"collections"
+	],
+	"peerDependencies": {
+		"@dreamteamer/users": ">=0.3.0"
+	},
+	"dreamteamer": {
+		"title": "Roles",
+		"description": "`roles`: a position a person holds — team leader, backend developer, product manager, QA engineer — one record per role, and an overlay of `users` adding `roles`, so \"who are the backend developers\" is a filter and each role lists its people back. Depends on `users`.",
+		"engine": ">=0.48.0",
+		"dependencies": [
+			"@dreamteamer/users"
+		]
+	}
+}