minutework 0.1.24 → 0.1.25
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.
|
@@ -53,6 +53,10 @@ extending MinuteWork app packs. An app pack is the product unit. The workspace
|
|
|
53
53
|
usually composes schemas, manifests, `mw.core.site`, runtime capabilities,
|
|
54
54
|
agents, overlays, and published-web flows before writing bespoke code.
|
|
55
55
|
|
|
56
|
+
MinuteWork supports two legitimate paths: build a native MinuteWork product
|
|
57
|
+
from scratch, or wrap an existing product/OSS system with a governed, agentic
|
|
58
|
+
control surface.
|
|
59
|
+
|
|
56
60
|
Implementation surfaces are:
|
|
57
61
|
|
|
58
62
|
- `tenant-app`: Next.js web surface for public routes and private `/app`
|
|
@@ -105,3 +109,8 @@ concrete workspace surfaces. A good answer should usually cover:
|
|
|
105
109
|
|
|
106
110
|
Do not end broad strategy answers by asking the user to name a skill. Choose
|
|
107
111
|
the relevant skills yourself and give the integrated answer.
|
|
112
|
+
|
|
113
|
+
If the user has not named a product or workflow yet, close by asking for that
|
|
114
|
+
concrete target and say you will map it to shell vs `tenant-app` vs `sidecar` vs
|
|
115
|
+
`mobile`, decide build-native vs `attached_app`, and identify the first
|
|
116
|
+
schemas, agents, and bridges to author.
|