Skip to content

Operational repos audit against main, matching AUDIT.md section 1 (#340) #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ptr727 merged 2 commits into from
Jul 18, 2026
Merged

Operational repos audit against main, matching AUDIT.md section 1 (#340) #351

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
72b3ff4
Operational repos audit against main, matching AUDIT.md section 1 (#340)
ptr727 Jul 18, 2026
2ef4417
State the ground-truth rule, not a false fleet-wide fact
ptr727 Jul 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions AUDIT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ This audit is not occasional. Run it whenever you **create, adopt, or materially

Audit one repository at a time. Read the target's **`main` branch** as ground truth: `main` is the released, authoritative state. Read `develop` only to detect divergence - a stale or diverged `develop` (behind `main`, or diverged) is reported as a **drift finding**, never audited as the truth. Do not treat a `develop`-only file as present if it is absent on `main`.

This holds for **both workflow models**. An `operational` repo commits directly to `develop`, but its ground truth is still `main` - the promoted, gated snapshot the promotion PR blesses. `develop` there is mid-flight by design (ungated direct pushes), so auditing it would measure work in progress: conformance scaffolding that has landed on `develop` but is not yet promoted is *un-promoted work*, not a conformance defect, and it counts when it reaches `main`. A registry `groundTruthBranch` naming `develop` therefore contradicts this section - for either model.

## 2. Resolve the Repo's Type(s)

Look up the repo in [`registry/repos.json`][repos] and read its `types[]`. If the entry is `classificationPending` (a backlog repo), classify it from the tree and propose a registry update:
Expand Down
6 changes: 3 additions & 3 deletions registry/repos.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@
"url": "https://github.com/ptr727/HomeAutomation-Config",
"status": "cataloged",
"types": ["source-only"],
"groundTruthBranch": "develop",
"groundTruthBranch": "main",
Comment thread
ptr727 marked this conversation as resolved.
"workflowModel": "operational",
"lineEndings": "lf",
"hasDevelop": true,
Expand Down Expand Up @@ -204,7 +204,7 @@
"url": "https://github.com/ptr727/ESPHome-Config",
"status": "cataloged",
"types": ["source-only"],
"groundTruthBranch": "develop",
"groundTruthBranch": "main",
"workflowModel": "operational",
"lineEndings": "lf",
"hasDevelop": true,
Expand Down Expand Up @@ -286,7 +286,7 @@
"url": "https://github.com/ptr727/Vantage-Config",
"status": "cataloged",
"types": ["source-only"],
"groundTruthBranch": "develop",
"groundTruthBranch": "main",
"workflowModel": "operational",
"lineEndings": "crlf",
"hasDevelop": true,
Expand Down