Skip to content

Vantage adoption follow-ups: every-tier bots wording, registry, carry blessing - #333

Merged
ptr727 merged 1 commit into
developfrom
vantage-adoption-followups
Jul 16, 2026
Merged

Vantage adoption follow-ups: every-tier bots wording, registry, carry blessing#333
ptr727 merged 1 commit into
developfrom
vantage-adoption-followups

Conversation

@ptr727

@ptr727 ptr727 commented Jul 16, 2026

Copy link
Copy Markdown
Owner

Incorporates the hub-side findings filed from the Vantage-Config operational onboarding (Vantage-Config #9). Fixes #328, fixes #329, fixes #331. (#330, the downstream carry-drift sweep, is handled by per-repo PRs, not here.)

AGENTS.md: every-tier bots (#328)

"Foundational Principles" claimed operational repos "run no bots and commit directly to develop" - contradicting the owner-confirmed every-tier merge-bot policy (and reality: Vantage-Config runs Dependabot dual-target plus the App-signed merge-bot). Reworded: operational repos run no codegen or auto-publish bots; Dependabot's dual-target sync and the App-signed merge-bot run on every tier. A next operational adoptee reading the old wording would have skipped the merge-bot standup.

Registry: Vantage-Config driftNotes (#329)

The entry recorded onboarding as "pending once content lands"; it completed 2026-07-16 per Vantage-Config #9. The stale note is replaced with the completed state (baseline docs, advisory lint CI, dispatch-only publisher, repo-config operational carry verified in sync, Dependabot + App merge-bot with the secret pair in both stores, adapted self-audit). spec/validate.py passes.

Downstream Carry: reference self-audit shape (#331)

"Adapted self-audit carry" required every downstream repo to carry adapted AUDIT.md + spec/secrets.json but shipped no reference shape - Vantage-Config had to invent the first one. Now:

  • The Vantage-Config carry is blessed as the reference adaptation (settings diff, normalized ruleset diff against the carried payloads, names-only secrets check, all targeting the current repo); a release repo adapts the same shape with its develop.json payload and its publish mechanisms' secret names.
  • spec/files.json letter-checks both carried files, so the fleet audit surfaces repos that don't carry them yet (today: all but Vantage-Config; the Earlier downstream carries drifted from the current repo-config and merge-bot reference #330 sweep starts closing that).

Verification

  • python3 spec/validate.py: OK (21 cataloged, 0 backlog).
  • markdownlint, cspell (CI scope), editorconfig-checker clean on the changed files.

🤖 Generated with Claude Code

… blessing

Incorporates the hub-side findings from the Vantage-Config operational
onboarding (Vantage-Config #9).

1. AGENTS.md "Foundational Principles" no longer claims operational
   repos "run no bots" - Dependabot dual-target sync and the App-signed
   merge-bot run on every tier (the owner-confirmed every-tier policy);
   only codegen and auto-publish bots are release-model. A next
   operational adoptee reading the old wording would skip the merge-bot
   standup. Fixes #328.

2. Registry: Vantage-Config driftNotes recorded onboarding as pending;
   it completed 2026-07-16 (baseline docs, advisory lint CI,
   dispatch-only publisher, repo-config carry in sync, merge-bot with
   the App secret pair, adapted self-audit). Fixes #329.

3. repo-config Downstream Carry: bless the Vantage-Config carry as the
   reference adaptation of AUDIT.md + spec/secrets.json (release repos
   adapt the same shape plus their publish-mechanism secret names), and
   letter-check both carried files in spec/files.json so the fleet
   audit flags repos missing them. Fixes #331.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 16, 2026 17:12

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the governance hub to incorporate post-onboarding follow-ups from the Vantage-Config operational adoption, aligning docs/spec/registry with the every-tier bot policy and establishing a reference shape for downstream self-audit carries.

Changes:

  • Clarifies AGENTS.md wording so operational repos are described as running no codegen/auto-publish bots (while still running Dependabot dual-target + the App-signed merge-bot).
  • Updates the registry entry for Vantage-Config to reflect completed onboarding status and details.
  • Makes AUDIT.md and spec/secrets.json part of the baseline file set and documents the blessed reference adaptation in repo-config/README.md.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
spec/files.json Adds AUDIT.md and spec/secrets.json to the baseline required carry set.
repo-config/README.md Documents the Vantage-Config self-audit carry as the reference adaptation and adds a reference-style external link.
registry/repos.json Replaces stale Vantage-Config drift notes with a completed-onboarding record.
AGENTS.md Rewords the operational repo description to match the every-tier bot policy (no codegen/auto-publish bots; Dependabot + merge-bot still apply).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants