@dreamteamer/responsibilities 0.0.0-stage → 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -2
- package/UPDATING.md +19 -0
- package/collections/responsibilities.collection.yaml +65 -0
- package/collections/users.collection.yaml +8 -0
- package/package.json +31 -5
package/README.md
CHANGED
|
@@ -1,3 +1,14 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @dreamteamer/responsibilities
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
The areas someone owns — release sign-off, the relationship with a client, the CI pipeline,
|
|
4
|
+
onboarding — as one list the whole workspace shares. A person lists the responsibilities they carry
|
|
5
|
+
on `users.responsibilities` (an overlay this module adds to users), and each area lists who carries
|
|
6
|
+
it, generated. Not a task (a commitment with an end), not a role (a position), and never
|
|
7
|
+
project-bound.
|
|
8
|
+
|
|
9
|
+
```bash
|
|
10
|
+
npm install @dreamteamer/responsibilities @dreamteamer/users
|
|
11
|
+
npx dreamteamer compile
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
Until core 0.12.0 this shipped inside `@dreamteamer/core`; records stay in `data/responsibilities/` under the same ids.
|
package/UPDATING.md
ADDED
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# Updating @dreamteamer/responsibilities
|
|
2
|
+
|
|
3
|
+
One section per release, newest first. Each says what you have to **do** in a workspace that
|
|
4
|
+
installs this module; most of the time it is `dt compile`, then `dt check`.
|
|
5
|
+
|
|
6
|
+
```bash
|
|
7
|
+
npm install @dreamteamer/responsibilities@latest
|
|
8
|
+
npx dreamteamer compile
|
|
9
|
+
npx dreamteamer check
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## 0.1.0 — out of core, a package of its own
|
|
15
|
+
|
|
16
|
+
`responsibilities` shipped inside `@dreamteamer/core` through 0.11; from core 0.12.0 core is a preset of the small
|
|
17
|
+
modules and this is one of them. The descriptor moved verbatim — the same fields, the same storage path
|
|
18
|
+
and the same id shape — so no record moves and nothing is migrated. A workspace that updates core gets
|
|
19
|
+
this package as a preset member; nothing to do but `dt compile`.
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
# responsibilities — the areas someone owns, as one list the whole workspace shares.
|
|
2
|
+
name: responsibilities
|
|
3
|
+
singular: responsibility
|
|
4
|
+
description: >-
|
|
5
|
+
An area of ownership — release sign-off, the relationship with a client, the CI pipeline, onboarding. One record per area; a person lists the responsibilities they carry on `users.responsibilities`. Not a task (a commitment with an end), not a role (a position), and never project-bound.
|
|
6
|
+
use_when: >-
|
|
7
|
+
someone is said to "own" or "be responsible for" an area — find or create it here, then list it on the person's `responsibilities`; asked "who owns X", read here
|
|
8
|
+
storage:
|
|
9
|
+
path: data/responsibilities
|
|
10
|
+
format: md
|
|
11
|
+
suffix: responsibility
|
|
12
|
+
ids:
|
|
13
|
+
from: '{{ name | slug }}'
|
|
14
|
+
pattern: ^[a-z0-9][a-z0-9-]*$
|
|
15
|
+
fields:
|
|
16
|
+
name:
|
|
17
|
+
type: string
|
|
18
|
+
required: true
|
|
19
|
+
description: The area, as a noun phrase — "release sign-off", "client onboarding".
|
|
20
|
+
description:
|
|
21
|
+
type: string
|
|
22
|
+
description: What owning it means, in one line.
|
|
23
|
+
users:
|
|
24
|
+
type: users
|
|
25
|
+
many: true
|
|
26
|
+
mirror_of: responsibilities
|
|
27
|
+
description: GENERATED — who carries it. Set `responsibilities` on the user.
|
|
28
|
+
notes:
|
|
29
|
+
type: markdown
|
|
30
|
+
body: true
|
|
31
|
+
description: The boundaries — what is in, what is out, who to ask.
|
|
32
|
+
tags:
|
|
33
|
+
type: string
|
|
34
|
+
many: true
|
|
35
|
+
examples: ['onboarding', 'client:northwind']
|
|
36
|
+
pattern: ^[a-z0-9]+(-[a-z0-9]+)*(:[a-z0-9]+(-[a-z0-9]+)*)?$
|
|
37
|
+
description: Free labels, lowercase and hyphenated, optionally key:value with no space around the colon.
|
|
38
|
+
author:
|
|
39
|
+
type: string
|
|
40
|
+
examples: ['agents/claude-code', 'scripts/read-git@2']
|
|
41
|
+
pattern: '^(agents|scripts)/[a-z0-9][a-z0-9-]*(@[a-z0-9][a-z0-9./-]*)?$'
|
|
42
|
+
description: >-
|
|
43
|
+
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`.
|
|
44
|
+
creation_context:
|
|
45
|
+
type: string
|
|
46
|
+
description: How and why this record came to be, in one line — and the reason whenever confidence is low.
|
|
47
|
+
source:
|
|
48
|
+
title: Information source
|
|
49
|
+
type: string
|
|
50
|
+
description: 'Where the INFORMATION came from, prefixed so it stays machine-readable: <collection>/<id> · file:<path> · url:<…> · migration:<id>.'
|
|
51
|
+
confidence:
|
|
52
|
+
type: string
|
|
53
|
+
default: normal
|
|
54
|
+
enum: [low, normal, high]
|
|
55
|
+
description: How much to trust this record. When low, the reason goes in creation_context — there is no separate note field.
|
|
56
|
+
display:
|
|
57
|
+
nav:
|
|
58
|
+
icon: key
|
|
59
|
+
list:
|
|
60
|
+
columns: [name, description, users]
|
|
61
|
+
form:
|
|
62
|
+
sections:
|
|
63
|
+
- title: Provenance
|
|
64
|
+
fields: [author, creation_context, source, confidence]
|
|
65
|
+
collapsed: true
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
# OVERLAY of users — the areas a person owns, so "who owns onboarding" is a filter.
|
|
2
|
+
name: users
|
|
3
|
+
overlay: true
|
|
4
|
+
fields:
|
|
5
|
+
responsibilities:
|
|
6
|
+
type: responsibilities
|
|
7
|
+
many: true
|
|
8
|
+
description: The areas they own — `responsibilities` records, one list the whole workspace shares.
|
package/package.json
CHANGED
|
@@ -1,6 +1,32 @@
|
|
|
1
1
|
{
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
2
|
+
"name": "@dreamteamer/responsibilities",
|
|
3
|
+
"version": "0.1.0",
|
|
4
|
+
"description": "Areas of ownership — release sign-off, a client relationship, onboarding — as one shared list each person names on users.responsibilities.",
|
|
5
|
+
"license": "Apache-2.0",
|
|
6
|
+
"repository": {
|
|
7
|
+
"type": "git",
|
|
8
|
+
"url": "git+https://github.com/dreamteamer/dreamteamer-modules.git",
|
|
9
|
+
"directory": "modules/responsibilities"
|
|
10
|
+
},
|
|
11
|
+
"keywords": [
|
|
12
|
+
"dreamteamer",
|
|
13
|
+
"dreamteamer-module",
|
|
14
|
+
"responsibilities"
|
|
15
|
+
],
|
|
16
|
+
"files": [
|
|
17
|
+
"README.md",
|
|
18
|
+
"UPDATING.md",
|
|
19
|
+
"collections"
|
|
20
|
+
],
|
|
21
|
+
"peerDependencies": {
|
|
22
|
+
"@dreamteamer/users": ">=0.3.0"
|
|
23
|
+
},
|
|
24
|
+
"dreamteamer": {
|
|
25
|
+
"title": "Responsibilities",
|
|
26
|
+
"description": "`responsibilities`: an area of ownership — release sign-off, the relationship with a client, the CI pipeline, onboarding — one record per area, and an overlay of `users` adding `responsibilities`, so \"who owns X\" is one read and each area lists who carries it. Not a task and not a role. Depends on `users`.",
|
|
27
|
+
"engine": ">=0.48.0",
|
|
28
|
+
"dependencies": [
|
|
29
|
+
"@dreamteamer/users"
|
|
30
|
+
]
|
|
31
|
+
}
|
|
32
|
+
}
|