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.
Go aialertsdashboarddockerdocker-monitoringgohomelabinfrastructure-monitoringkubernetesmonitoringmspproxmoxproxmox-backup-serverproxmox-mail-gatewayproxmox-veself-hostedtruenastypescriptvspherewebhooks
Make triage disclosure match the release train and private support
pulse-triage[bot]e0ea064e8fbf
diff --git a/docs/AI_TRANSPARENCY.md b/docs/AI_TRANSPARENCY.mdindex 2d8218ec14..52ddd6e877 100644--- a/docs/AI_TRANSPARENCY.md+++ b/docs/AI_TRANSPARENCY.md@@ -14,8 +14,9 @@ human review. The continuously running maintainer does this within boundariesI define.I set the product direction and remain responsible for everything that ships.-The automated maintainer owns day-to-day maintenance, public issue replies,-and qualified releases. I do not claim to have personally written every line.+The automated maintainer owns day-to-day maintenance and public issue replies;+releases follow the fixed train described below. I do not claim to have+personally written every line.Automated changes must pass the applicable project tests and audit gates, andreleased builds still go through Pulse's release qualification process.@@ -25,17 +26,17 @@ released builds still go through Pulse's release qualification process.architectural, issue, and operational requirements.- **Maintenance.** Automation monitors project signals, investigates defects,prepares fixes, and performs bounded routine repository work continuously.-- **Documentation and releases.** The maintainer prepares documentation,- changelogs, and release material, then qualifies and publishes prereleases- and stable releases under standing authority. Release claims must stay- consistent with the code and qualification evidence.-- **Issue triage and support.** Automated issue and discussion replies post+- **Documentation and releases.** The maintainer prepares documentation and+ changelogs. The release train builds, checks and publishes releases. Release+ claims must stay consistent with the actual published source and checks.+- **Issue triage.** Automated issue and discussion replies postunder the dedicated `pulse-triage` bot identity and link back to this page.Automated issue state changes use that identity as well. Mixed reports followthe [topic-integrity triage contract](ISSUE_TRIAGE.md): automation can surfacedeclared secondary topics, but a maintainer or triage agent must give every- actionable topic a linked disposition. Automated support replies are sent as- Pulse Triage and link here as well.+ actionable topic a linked disposition. Private support email is handled by+ Richard, not the automated maintainer: it does not read a support mailbox or+ send email. Keep credentials and private diagnostics out of public threads.- **Change provenance.** Commits made by the continuously running maintainercarry a dedicated bot author and committer identity. Issue-driven changeslink back to the originating report where applicable.@@ -47,29 +48,40 @@ are not given tool-specific labels.## How changes land and ship-Every change reaches `main` the same way, whoever or whatever wrote it: a-pull request that auto-merges when the repository's required checks pass.+Every change reaches `main` through a pull request, whoever or whatever wrote+it. Maintainer changes receive independent review and must pass the+repository's required checks before merging.The `main` branch ruleset requires that for every writer, with no bypass, soa red check blocks the maintainer and me alike. The maintainer's pullrequests are opened by `pulse-triage[bot]` and state what changed, why itwas needed, which reports or demand-ledger entries it answers, and whatvalidation was used, so the record on GitHub is the record of the decision.-Releases run on a train rather than on demand. A release candidate is cut-from `main` into a `release/vX.Y` branch on a fixed schedule, soaks on the-opt-in preview channel, takes only backports of regression and security-fixes while it soaks, and is promoted to stable as the exact candidate-content. The promotion resolver in the release pipeline enforces the soak-and the exact-content rule for every dispatcher. The full rules are in-[RELEASE_PROMOTION_POLICY.md](https://github.com/rcourtman/Pulse/blob/b64709e7b7ad174e9c94ad2a0d3d841678690935/docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.md),-under "Release Train".+Every 14 days after the last stable release, the train cuts the next minor+release candidate from the head of `main`. It carries everything on `main` at+that cut, not a selected set of fixes. Repairs go on `main`, not onto an older+release line.++The candidate soaks for 24 hours on the opt-in preview channel, then is promoted+unchanged to stable unless an open issue labelled `release-blocker` stops+promotion. A candidate regression from the previous stable release or a release+failure is repaired on `main`; once the blockers are closed, the train cuts a+fresh candidate that carries the repair. Product changes are not inserted into the frozen candidate.++A fix merged to `main` is not yet a published fix. A published beta or release+candidate is available to preview users, not proof that stable users have it.+Issue replies name the containing version only after checking its actual+released source, and ask for a retest when appropriate. See the+[published releases](https://github.com/rcourtman/Pulse/releases) for available+versions; a source commit or a passing test alone does not establish availability.## Authority and responsibility-On 8 September 2026 I confirmed standing authority for the automated maintainer-to own public Pulse issue replies and release publication, including stable-releases. These actions do not require my approval for each comment or release.-The maintainer chooses release scope, maturity and timing from current evidence.+The automated maintainer owns ordinary maintenance and public Pulse issue+replies under standing authority. These actions do not require my approval for+each change or comment. The release train publishes prereleases and stable+releases without per-release approval; it follows the cycle above rather than+having a model choose release scope, maturity or timing.Standing authority does not waive independent review, release qualification,exact-candidate promotion, required soak, or verification after publication.diff --git a/frontend-modern/public/docs/AI_TRANSPARENCY.md b/frontend-modern/public/docs/AI_TRANSPARENCY.mdindex 2d8218ec14..52ddd6e877 100644--- a/frontend-modern/public/docs/AI_TRANSPARENCY.md+++ b/frontend-modern/public/docs/AI_TRANSPARENCY.md@@ -14,8 +14,9 @@ human review. The continuously running maintainer does this within boundariesI define.I set the product direction and remain responsible for everything that ships.-The automated maintainer owns day-to-day maintenance, public issue replies,-and qualified releases. I do not claim to have personally written every line.+The automated maintainer owns day-to-day maintenance and public issue replies;+releases follow the fixed train described below. I do not claim to have+personally written every line.Automated changes must pass the applicable project tests and audit gates, andreleased builds still go through Pulse's release qualification process.@@ -25,17 +26,17 @@ released builds still go through Pulse's release qualification process.architectural, issue, and operational requirements.- **Maintenance.** Automation monitors project signals, investigates defects,prepares fixes, and performs bounded routine repository work continuously.-- **Documentation and releases.** The maintainer prepares documentation,- changelogs, and release material, then qualifies and publishes prereleases- and stable releases under standing authority. Release claims must stay- consistent with the code and qualification evidence.-- **Issue triage and support.** Automated issue and discussion replies post+- **Documentation and releases.** The maintainer prepares documentation and+ changelogs. The release train builds, checks and publishes releases. Release+ claims must stay consistent with the actual published source and checks.+- **Issue triage.** Automated issue and discussion replies postunder the dedicated `pulse-triage` bot identity and link back to this page.Automated issue state changes use that identity as well. Mixed reports followthe [topic-integrity triage contract](ISSUE_TRIAGE.md): automation can surfacedeclared secondary topics, but a maintainer or triage agent must give every- actionable topic a linked disposition. Automated support replies are sent as- Pulse Triage and link here as well.+ actionable topic a linked disposition. Private support email is handled by+ Richard, not the automated maintainer: it does not read a support mailbox or+ send email. Keep credentials and private diagnostics out of public threads.- **Change provenance.** Commits made by the continuously running maintainercarry a dedicated bot author and committer identity. Issue-driven changeslink back to the originating report where applicable.@@ -47,29 +48,40 @@ are not given tool-specific labels.## How changes land and ship-Every change reaches `main` the same way, whoever or whatever wrote it: a-pull request that auto-merges when the repository's required checks pass.+Every change reaches `main` through a pull request, whoever or whatever wrote+it. Maintainer changes receive independent review and must pass the+repository's required checks before merging.The `main` branch ruleset requires that for every writer, with no bypass, soa red check blocks the maintainer and me alike. The maintainer's pullrequests are opened by `pulse-triage[bot]` and state what changed, why itwas needed, which reports or demand-ledger entries it answers, and whatvalidation was used, so the record on GitHub is the record of the decision.-Releases run on a train rather than on demand. A release candidate is cut-from `main` into a `release/vX.Y` branch on a fixed schedule, soaks on the-opt-in preview channel, takes only backports of regression and security-fixes while it soaks, and is promoted to stable as the exact candidate-content. The promotion resolver in the release pipeline enforces the soak-and the exact-content rule for every dispatcher. The full rules are in-[RELEASE_PROMOTION_POLICY.md](https://github.com/rcourtman/Pulse/blob/b64709e7b7ad174e9c94ad2a0d3d841678690935/docs/release-control/v6/internal/RELEASE_PROMOTION_POLICY.md),-under "Release Train".+Every 14 days after the last stable release, the train cuts the next minor+release candidate from the head of `main`. It carries everything on `main` at+that cut, not a selected set of fixes. Repairs go on `main`, not onto an older+release line.++The candidate soaks for 24 hours on the opt-in preview channel, then is promoted+unchanged to stable unless an open issue labelled `release-blocker` stops+promotion. A candidate regression from the previous stable release or a release+failure is repaired on `main`; once the blockers are closed, the train cuts a+fresh candidate that carries the repair. Product changes are not inserted into the frozen candidate.++A fix merged to `main` is not yet a published fix. A published beta or release+candidate is available to preview users, not proof that stable users have it.+Issue replies name the containing version only after checking its actual+released source, and ask for a retest when appropriate. See the+[published releases](https://github.com/rcourtman/Pulse/releases) for available+versions; a source commit or a passing test alone does not establish availability.## Authority and responsibility-On 8 September 2026 I confirmed standing authority for the automated maintainer-to own public Pulse issue replies and release publication, including stable-releases. These actions do not require my approval for each comment or release.-The maintainer chooses release scope, maturity and timing from current evidence.+The automated maintainer owns ordinary maintenance and public Pulse issue+replies under standing authority. These actions do not require my approval for+each change or comment. The release train publishes prereleases and stable+releases without per-release approval; it follows the cycle above rather than+having a model choose release scope, maturity or timing.Standing authority does not waive independent review, release qualification,exact-candidate promotion, required soak, or verification after publication.diff --git a/scripts/tests/test_transparency_docs.py b/scripts/tests/test_transparency_docs.pynew file mode 100644index 0000000000..f9ebb4d389--- /dev/null+++ b/scripts/tests/test_transparency_docs.py@@ -0,0 +1,75 @@+#!/usr/bin/env python3+"""Keep the public triage disclosure honest about delivery and private support.++These checks cover documentation claims, not operation of the release train.+"""++from pathlib import Path+import unittest+++ROOT = Path(__file__).resolve().parents[2]+DOCUMENTS = (+ ROOT / "docs/AI_TRANSPARENCY.md",+ ROOT / "frontend-modern/public/docs/AI_TRANSPARENCY.md",+)+++class TransparencyDocsTest(unittest.TestCase):+ def documents(self):+ for path in DOCUMENTS:+ yield path, " ".join(path.read_text(encoding="utf-8").split())++ def test_all_main_minor_cycle_not_selective_backports(self):+ for path, text in self.documents():+ with self.subTest(document=path):+ self.assertIn("Every 14 days after the last stable release", text)+ self.assertIn("next minor release candidate from the head of `main`", text)+ self.assertIn("everything on `main` at that cut", text)+ self.assertIn("Repairs go on `main`, not onto an older release line", text)+ self.assertNotIn("takes only backports", text)++ def test_blockers_need_a_fresh_candidate_not_a_changed_soak(self):+ for path, text in self.documents():+ with self.subTest(document=path):+ self.assertIn("soaks for 24 hours", text)+ self.assertIn("promoted unchanged to stable", text)+ self.assertIn("open issue labelled `release-blocker`", text)+ self.assertIn("candidate regression from the previous stable release", text)+ self.assertIn("train cuts a fresh candidate that carries the repair", text)+ self.assertIn("not inserted into the frozen candidate", text)++ def test_source_preview_and_stable_availability_are_separate(self):+ for path, text in self.documents():+ with self.subTest(document=path):+ self.assertIn("A fix merged to `main` is not yet a published fix", text)+ self.assertIn("not proof that stable users have it", text)+ self.assertIn("checking its actual released source", text)+ self.assertIn("https://github.com/rcourtman/Pulse/releases", text)+ self.assertIn("passing test alone does not establish availability", text)++ def test_private_support_is_not_automated_or_public_diagnostics(self):+ for path, text in self.documents():+ with self.subTest(document=path):+ self.assertIn("Private support email is handled by Richard", text)+ self.assertIn("does not read a support mailbox or send email", text)+ self.assertIn("Keep credentials and private diagnostics out of public threads", text)+ self.assertNotIn("Automated support replies are sent", text)+ self.assertIn("[topic-integrity triage contract](ISSUE_TRIAGE.md)", text)++ def test_standing_authority_preserves_review_and_mechanical_releases(self):+ for path, text in self.documents():+ with self.subTest(document=path):+ self.assertIn("Maintainer changes receive independent review", text)+ self.assertIn("must pass the repository's required checks before merging", text)+ self.assertIn("without per-release approval", text)+ self.assertIn("rather than having a model choose release scope", text)+ self.assertNotIn("maintainer chooses release scope, maturity and timing", text)+ self.assertNotIn("b64709e7b7ad174e9c94ad2a0d3d841678690935", text)++ def test_shipped_disclosure_matches_the_triage_link_target(self):+ self.assertEqual(DOCUMENTS[0].read_bytes(), DOCUMENTS[1].read_bytes())+++if __name__ == "__main__":+ unittest.main()