chore: align repo to kellerai-oss-template (structural)#1
Open
jonathan-kellerai wants to merge 3 commits into
Open
chore: align repo to kellerai-oss-template (structural)#1jonathan-kellerai wants to merge 3 commits into
jonathan-kellerai wants to merge 3 commits into
Conversation
Blast-radius pulse — blocked |
…BR-011 blast-radius gates
Blast-radius pulse — blocked |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Aligns
trust-boundary-protocoltojonathan-kellerai/kellerai-oss-template@main— structural alignment (Plan C of the OSS-template rollout). Adds 13 governance / meta-governance files; no existing content is modified. Targetsdevper the canonical four-tier flow (dev → qa → main).Produced by a four-wave dynamic workflow (Analyze → Edit → Verify; Publish handled manually so commit + push went through the audited
gm-fullpath). Audit trail inartifacts/trust-boundary-protocol/{gap.md,changes.json}.Files added (13)
.github/workflows/— 7 meta-governance workflowsblast-radius-outcome.ymlblast-radius-pulse.ymltrust-dial-gate.ymltrust-dial-outcome.ymlvalidate-branch-name.ymlvalidate-branch-tier.ymlvalidate-linked-issue.ymlconformance/— blast-radius frameworkaffects.jsonblast_radius.regoblast_radius_test.regoaudit/— blast-radius pulse ledgerblast-radius.jsonlscripts/— pulse orchestrationpulse.sh(mode755)root
.kellerai-oss.json— rollout manifest (artifact_type,artifact_dir,primary_validator,owner)Files modified
None.
Conformance + sanitization gates
check-sanitization: OK — no denied terms in the publishable tree(exit 0), confirmed both standalone and by thepre-commitlefthook.check-structure: OK — 17 canonical files present, specification sections intact(pre-commitlefthook).Residual warnings: none surfaced by the workflow or the sanitization gate.
Branch protection
This rollout also configured branch rulesets mirroring the canonical template —
protect-main,protect-qa,protect-dev: block branch deletion and non-fast-forward (force-push), require a pull request with 1 approving review (code-owner review onmainandqa; not required ondev); repository-admin bypass.Why draft
Draft so a human can confirm the 7 workflow files fire correctly in this repo's CI and that
conformance/affects.jsonreflects the right blast scope before promotingdev → qa → main.