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.

Frame the transparency page around the human maintainer

rcourtman02dac0ecdf77
diff --git a/docs/AI_TRANSPARENCY.md b/docs/AI_TRANSPARENCY.md
index f9a0bf21aa..899a373662 100644
--- a/docs/AI_TRANSPARENCY.md
+++ b/docs/AI_TRANSPARENCY.md
@@ -1,26 +1,26 @@
# Development and Automation Transparency
-Pulse is maintained by me and built with heavy use of coding agents. This page
-explains how, so it doesn't need repeating in every commit, release or issue.
+I maintain Pulse, and I build it with heavy use of coding agents and
+automation. This page explains how, so it doesn't need repeating in every
+commit, release or issue.
## Who does what
+- **I** maintain Pulse: I set direction, decide what gets built, and answer for
+ everything that ships. I don't claim to have written every line.
- **Coding agents** write code, tests and documentation from requirements I set.
-- **The automated maintainer** runs continuously. It investigates bugs, prepares
- fixes, triages issues and replies on GitHub as `pulse-triage[bot]`, and its
- commits carry that identity. Repository workflows appear as
- `github-actions[bot]`. Each problem in a mixed report gets its own answer
+- **Automation** handles routine triage and fixes within limits I set. Its issue
+ replies and commits come from `pulse-triage[bot]`; repository workflows appear
+ as `github-actions[bot]`. Each problem in a mixed report gets its own answer
under the [triage contract](ISSUE_TRIAGE.md).
-- **I** set product direction, decide what the automation may do, and answer
- for everything that ships. I don't claim to have written every line.
-I handle private support email myself. The automated maintainer does not read
-a support mailbox or send email. Keep credentials and private diagnostics out
-of public threads.
+I handle private support email myself. Automation does not read a support
+mailbox or send email. Keep credentials and private diagnostics out of public
+threads.
## How changes land and ship
-Every change reaches `main` through a pull request. Maintainer changes receive
+Every change reaches `main` through a pull request. Automated changes receive
independent review, and every change must pass the repository's required checks
before merging. Nobody can bypass this, me included.
@@ -35,15 +35,16 @@ after checking its released source.
## Issue resolution and retesting
-An issue is resolved when the reporter confirms the fix, or the maintainer
-reproduces it with no reported symptom left unresolved. A merged fix or a
+An issue is resolved when the reporter confirms the fix, or the fix is
+reproduced with no reported symptom left unresolved. A merged fix or a
workaround alone is not enough.
-Once the fix ships in a stable release, the maintainer names that version and
-asks for a retest. After 14 days with no reply, and nobody else reporting the
-same problem, the issue may be closed with the `closed-needs-retest-timeout`
-label. That is **not confirmed resolution**, and it can be reopened. Feature
-requests, `needs-human` issues and unexplained symptoms are never closed this way.
+Once the fix ships in a stable release, the issue gets a reply naming that
+version and asking for a retest. After 14 days with no reply, and nobody else
+reporting the same problem, the issue may be closed with the
+`closed-needs-retest-timeout` label. That is **not confirmed resolution**, and
+it can be reopened. Feature requests, `needs-human` issues and unexplained
+symptoms are never closed this way.
Still broken? Comment on the original issue rather than filing it again. Say
which symptom remains and which version you're on; add
@@ -52,11 +53,11 @@ have them. Don't repeat an outage, update or backup just to retest.
## Authority and responsibility
-The automated maintainer handles routine maintenance and issue replies without
-asking me each time. The release train publishes on schedule without
-per-release approval; no model chooses what goes in a release or when. None of
-this skips review, soak or release checks. I can revoke that authority at any
-time, and if an automated change is wrong, it's my bug to fix.
+Routine fixes and issue replies don't need my sign-off each time, and the
+release train publishes on schedule without per-release approval; no model
+chooses what goes in a release or when. None of this skips review, soak or
+release checks. I can switch any of it off, and if something automated is
+wrong, it's my bug to fix.
## How the work should be judged
diff --git a/frontend-modern/public/docs/AI_TRANSPARENCY.md b/frontend-modern/public/docs/AI_TRANSPARENCY.md
index f9a0bf21aa..899a373662 100644
--- a/frontend-modern/public/docs/AI_TRANSPARENCY.md
+++ b/frontend-modern/public/docs/AI_TRANSPARENCY.md
@@ -1,26 +1,26 @@
# Development and Automation Transparency
-Pulse is maintained by me and built with heavy use of coding agents. This page
-explains how, so it doesn't need repeating in every commit, release or issue.
+I maintain Pulse, and I build it with heavy use of coding agents and
+automation. This page explains how, so it doesn't need repeating in every
+commit, release or issue.
## Who does what
+- **I** maintain Pulse: I set direction, decide what gets built, and answer for
+ everything that ships. I don't claim to have written every line.
- **Coding agents** write code, tests and documentation from requirements I set.
-- **The automated maintainer** runs continuously. It investigates bugs, prepares
- fixes, triages issues and replies on GitHub as `pulse-triage[bot]`, and its
- commits carry that identity. Repository workflows appear as
- `github-actions[bot]`. Each problem in a mixed report gets its own answer
+- **Automation** handles routine triage and fixes within limits I set. Its issue
+ replies and commits come from `pulse-triage[bot]`; repository workflows appear
+ as `github-actions[bot]`. Each problem in a mixed report gets its own answer
under the [triage contract](ISSUE_TRIAGE.md).
-- **I** set product direction, decide what the automation may do, and answer
- for everything that ships. I don't claim to have written every line.
-I handle private support email myself. The automated maintainer does not read
-a support mailbox or send email. Keep credentials and private diagnostics out
-of public threads.
+I handle private support email myself. Automation does not read a support
+mailbox or send email. Keep credentials and private diagnostics out of public
+threads.
## How changes land and ship
-Every change reaches `main` through a pull request. Maintainer changes receive
+Every change reaches `main` through a pull request. Automated changes receive
independent review, and every change must pass the repository's required checks
before merging. Nobody can bypass this, me included.
@@ -35,15 +35,16 @@ after checking its released source.
## Issue resolution and retesting
-An issue is resolved when the reporter confirms the fix, or the maintainer
-reproduces it with no reported symptom left unresolved. A merged fix or a
+An issue is resolved when the reporter confirms the fix, or the fix is
+reproduced with no reported symptom left unresolved. A merged fix or a
workaround alone is not enough.
-Once the fix ships in a stable release, the maintainer names that version and
-asks for a retest. After 14 days with no reply, and nobody else reporting the
-same problem, the issue may be closed with the `closed-needs-retest-timeout`
-label. That is **not confirmed resolution**, and it can be reopened. Feature
-requests, `needs-human` issues and unexplained symptoms are never closed this way.
+Once the fix ships in a stable release, the issue gets a reply naming that
+version and asking for a retest. After 14 days with no reply, and nobody else
+reporting the same problem, the issue may be closed with the
+`closed-needs-retest-timeout` label. That is **not confirmed resolution**, and
+it can be reopened. Feature requests, `needs-human` issues and unexplained
+symptoms are never closed this way.
Still broken? Comment on the original issue rather than filing it again. Say
which symptom remains and which version you're on; add
@@ -52,11 +53,11 @@ have them. Don't repeat an outage, update or backup just to retest.
## Authority and responsibility
-The automated maintainer handles routine maintenance and issue replies without
-asking me each time. The release train publishes on schedule without
-per-release approval; no model chooses what goes in a release or when. None of
-this skips review, soak or release checks. I can revoke that authority at any
-time, and if an automated change is wrong, it's my bug to fix.
+Routine fixes and issue replies don't need my sign-off each time, and the
+release train publishes on schedule without per-release approval; no model
+chooses what goes in a release or when. None of this skips review, soak or
+release checks. I can switch any of it off, and if something automated is
+wrong, it's my bug to fix.
## How the work should be judged
diff --git a/scripts/tests/test_transparency_docs.py b/scripts/tests/test_transparency_docs.py
index 994a6dc475..9504c231da 100644
--- a/scripts/tests/test_transparency_docs.py
+++ b/scripts/tests/test_transparency_docs.py
@@ -128,7 +128,7 @@ class TransparencyDocsTest(unittest.TestCase):
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("Automated 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("no model chooses what goes in a release or when", text)