You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e300bca
Browse filesBrowse the repository at this point in the historyBrowse files
- Sensitive Runtime Data Protection: `references/protocols/sensitive-runtime-data-protection.md`
19
19
20
-
**Post-deployment (optional, non-intrusive)**: after a deployment is verified successful, you may offer at most once to generate anonymized shareables and, in that same offer, optionally submit the work to the case wall (Deployment Share) — see `references/protocols/deployment-share.md`. Never follow up if declined; never publish or submit on the user's behalf.
20
+
**Post-deployment (optional, non-intrusive)**: after a deployment is verified successful, you may offer at most once to generate anonymized shareables (Deployment Share) — see `references/protocols/deployment-share.md`. Deliver the card, the copy and the case-wall entry in one reply; shareables only if that is all the user asked for. Never follow up if declined; never publish or submit on the user's behalf.
Copy file name to clipboardExpand all lines: skills/cloudbase-platform/references/protocols/deployment-share.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,20 @@ A soft, non-intrusive flow for turning a verified deployment milestone into anon
4
4
5
5
## Trigger & Boundaries
6
6
7
-
- Only after a deployment is **verified successful** (public URL reachable, or mini program upload/publish completed), offer **at most once**. The offer is one sequence: generate shareables, then optionally submit the work to the case wall. Do not ask these as two prompts.
8
-
- If the user declines or ignores, stop immediately — never follow up, and do not ask about the case wall later in the same session.
9
-
- Generate shareables only after the user explicitly agrees. Publishing is always a manual user action — **never post on the user's behalf**.
10
-
- The case-wall step stays inside that same agreement. Show the full draft and wait for an explicit confirmation before giving a submission link or asking the user to paste. Never submit on the user's behalf. If the user only wants the shareables, stop after delivering them.
7
+
- Only after a deployment is **verified successful** (public URL reachable, or mini program upload/publish completed), offer **at most once**. Do not ask the same thing twice in one session.
8
+
- If the user declines or ignores, stop immediately — never follow up.
9
+
- Generate shareables only after the user asks for them (or clicks the share action on the deployment card). **Never post on the user's behalf**, and never fill the form for them: submission is theirs to do.
11
10
- Never delay, bloat, or overshadow the deployment report itself. This is a closing pleasantry, not a step of the deployment workflow.
12
11
12
+
## Two Modes
13
+
14
+
Pick the mode the user's request implies; do not make them ask twice.
15
+
16
+
-**One round (default)** — deliver the visual card, the paste-ready copy **and** the case-wall submission entry (`prepareFeedback` with `channel="case"`) together in a single reply. The user reads it, decides, and submits by hand if they want. Asking a second time just to hand over a link the user can ignore costs a whole turn and reads as nagging.
17
+
-**Shareables only (on demand)** — if the user asked for the card/copy alone, or said they do not want to submit anywhere, stop after the deliverables and do not bring up the case wall again in this session.
18
+
19
+
In both modes the draft is shown in full before anything else, and the entry is a link the user opens while signed in — we never submit, never prefill, never post.
20
+
13
21
## Required Information (both deliverables must cover all items)
0 commit comments