Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Withdraw the unactivated transition refund proposal

rcourtman4d64638b18f2
diff --git a/docs/release-control/v6/internal/records/community-transition-refund-preparation-2026-10-25.md b/docs/release-control/v6/internal/records/community-transition-refund-preparation-2026-10-25.md
index 87808de2cc..59773f8465 100644
--- a/docs/release-control/v6/internal/records/community-transition-refund-preparation-2026-10-25.md
+++ b/docs/release-control/v6/internal/records/community-transition-refund-preparation-2026-10-25.md
@@ -1,11 +1,27 @@
-# Community transition refund preparation
+# Community transition refund preparation: historical record
+
+**Status, 25 October 2026: proposal withdrawn before activation.**
+
+The expanded transition-refund proposal described below is no longer part of
+current planning. Pulse's published refund policy remains unchanged. No
+programme dates or production payment actions were adopted by this preparation.
+
+Community product changes do not depend on implementing or activating this
+withdrawn programme. The prepared source and tests remain dormant technical
+work. Any separate future use requires its own reviewed policy and proof.
+
+The following sections preserve the historical preparation record. Their
+proposed eligibility rules and implementation requirements are superseded,
+and must not be treated as an active roadmap or customer refund offer.
+
+## Historical technical preparation
25 October 2026. Commercial preparation under L2 and L3. The preview and
subsequent annual quote/apply preparation do not adopt programme dates, deploy
the service, change the published offer, remove runtime gates or authorize
production payment actions.
-## Prepared boundary
+### Prepared boundary
`pulse-pro:license-server/v6_commercial_refunds.go` binds the requested
subscription and invoice to a configured annual Pulse price, one complete annual
@@ -55,7 +71,7 @@ local fence only through an explicit, audited operator attestation of provider
evidence that the request cannot complete. An active read or elapsed time is
insufficient. No financial request is repeated by that resolution.
-## Individual requests
+### Individual requests
Refunds are on request; there is no blanket payout or automatic cancellation.
Publish clear terms and a simple request route so customers need not argue a
@@ -80,7 +96,7 @@ full, including monthly renewals up to cancellation. This amount rule still
needs its separate original-payment/history proof and implementation; the
annual-only executor does not provide that remedy yet.
-## Remaining implementation
+### Remaining implementation
Keep the public free-feature change out of the automatic release train until
the notice and effective release are coordinated. Community history, remote
@@ -116,7 +132,7 @@ cancellation resolution cannot apply to an already canceled subscription.
This record does not close the external commercial transition proof or claim
that the free-feature release or complete customer programme has shipped.
-## Verification
+### Verification
The standalone license-server Go suite includes
`v6_commercial_refunds_test.go` for exact-payment admission, grandfathered and
diff --git a/docs/release-control/v6/internal/status.json b/docs/release-control/v6/internal/status.json
index f4b9f1e11e..8de6d33bd7 100644
--- a/docs/release-control/v6/internal/status.json
+++ b/docs/release-control/v6/internal/status.json
@@ -4580,7 +4580,7 @@
},
{
"id": "RA41",
- "summary": "The released self-hosted commercial surface remains coherent across the canonical offer, Stripe billing, Pulse Account, license-server persistence, runtime and Relay entitlements, and support policy: Community, Relay, and Pro keep distinct jobs with Pro bundling Relay, while unproved self-service plan and cadence transitions remain unavailable and unadvertised until their external lifecycle and Relay version-floor proof passes. Any Community transition refund or cancellation of paid access requires an individually recorded, verified customer request; the programme must not issue blanket refunds or automatically cancel subscriptions.",
+ "summary": "The released self-hosted commercial surface remains coherent across the canonical offer, Stripe billing, Pulse Account, license-server persistence, runtime and Relay entitlements, and support policy: Community, Relay, and Pro keep distinct jobs with Pro bundling Relay, while unproved self-service plan and cadence transitions remain unavailable and unadvertised until their external lifecycle and Relay version-floor proof passes. No blanket refund or automatic subscription cancellation is introduced by this work. The expanded transition-refund proposal is withdrawn and is not an activation dependency for Community product changes; the published refund policy remains unchanged.",
"kind": "trust-gate",
"blocking_level": "release-ready",
"proof_type": "manual",
@@ -9577,7 +9577,7 @@
},
{
"id": "community-commercial-transition-cutover",
- "summary": "Activate the notice-bound Community transition remedy after adopted policy, prior-refund/credit and renewal-period reconciliation, recent-first-purchase proof, failed/absent-refund recovery, production-schema migration proof and external event/runtime convergence. Annual legacy/v6 quote/apply preparation does not close these obligations.",
+ "summary": "Complete the notice-bound Community commercial cutover with coherent artifacts, grants, public offer and access guidance, preserved subscriptions/prices/purchased rights, safe legacy/v6 runtime convergence and demonstrated remaining paid value. The expanded transition-refund proposal is withdrawn; its first-purchase, multi-payment and programme-activation work is not a prerequisite for the Community changes. Ordinary refund policy remains unchanged.",
"owner": "project-owner",
"status": "planned",
"recorded_at": "2026-10-25",
diff --git a/docs/release-control/v6/internal/subsystems/cloud-paid.md b/docs/release-control/v6/internal/subsystems/cloud-paid.md
index 1f7e6b920f..3e9478560f 100644
--- a/docs/release-control/v6/internal/subsystems/cloud-paid.md
+++ b/docs/release-control/v6/internal/subsystems/cloud-paid.md
@@ -15,7 +15,12 @@
## Purpose
-### Community transition refund preparation
+### Dormant transition refund preparation
+
+The expanded transition-refund proposal was withdrawn before activation.
+Pulse's published refund policy is unchanged, and Community product changes
+do not depend on implementing that programme. The source below remains
+dormant technical preparation, not an active offer or activation task.
`pulse-pro:license-server/v6_commercial_refunds.go` owns the admin-only annual
transition refund preview. Its proposed announcement and release dates do not
@@ -44,14 +49,12 @@ withdrawal cannot race that intent. Unrequested historical quotes cannot begin
cancellation. Already-dispatched obligations retain recovery. There is no
blanket payout or automatic subscription cancellation.
-The Community history/probe/seat boundary and Business sales pause remain
-pending the notice-bound cutover. Before a refund exit is offered, adopt the
-programme and complete prior-refund/credit and renewal-period reconciliation,
-the separate recent-first-purchase remedy, failed/absent-refund recovery,
-production-schema migration proof and external event/runtime convergence.
-Customer-wide outstanding billing requires explicit reconciliation. No payment
-effect may be inferred from an unsigned preview or its dates. The preparation
-record is
+The Community commercial cutover remains separately governed. Preserve
+existing subscriptions, pricing protection and purchased rights. Do not
+activate or extend the withdrawn refund programme as part of that cutover.
+Existing ordinary refund handling remains unchanged. Separately justified
+financial work would require its own adopted scope and operational proof.
+The historical preparation record is
`docs/release-control/v6/internal/records/community-transition-refund-preparation-2026-10-25.md`.
### Reporting measurement precedes commercial feature decisions