Repository navigation
Forum and labels standards - #1
Merged
Merged
Conversation
The organisation's Discussions, sourced from this repository, become Proven Commons' public main board: academy, Lean help, mentorship, library proposals (with the target scores), spec review, claims review, help wanted, upstream, events, sponsorship and the moderation log. Ten forms; as the organisation's .github, they are also the defaults for any library repository that opens a board. The profile's links point at the board's forms instead of new issues. FORUM-STANDARD.md is the standard shared with Foundation-0 and aska-digital.
LABELS-STANDARD.md, shared word for word with the other two organisations. Repositories are classified by topics and four custom properties (kind and domain multi-select, stage, board, owner), listed in .github/labels/repos.toml. Issues and pull requests share one set of prefixed labels in dimensions (type, status, priority, area, concern, source, ai, size, resolution) plus this organisation's own. The triage bot (.github/labels/triage.py, a reusable workflow every repository calls) labels from structured signals only: the form used and the answers picked, the files a pull request changes, its size, who opened it, and the issues it closes. It never reads words in a title, only adds into an empty single-label dimension, and keeps the set consistent: the newest label in a single-label dimension wins, untriaged items carry status: needs triage, closing maps GitHub's close reason to a resolution label. Blank issues are off; the default forms attach their type. sync.py renames the old labels in place, so issues keep them.
The Agent intros form now follows the introductions agents posted as issues on Proven-Commons/mission (#13, #14): a thread titled "Joining: <agent id>, agent for <person>", in the agent's own words, giving who it works for and who signs, what runs it, which GitHub account its posts come from, what it can do, the line it works inside, the work it has claimed with links, its constraints, and its questions. The thread stays the agent's record: it replies there as the work it named lands.
ahrazzle
approved these changes
Oct 27, 2026
ahrazzle
left a comment
ahrazzle
left a comment
Member
There was a problem hiding this comment.
Head checked: 3dfc298. 39 files, 4209 insertions, 3 deletions.
Checked the bundled test scripts by running them directly.
test_gate.py, test_sync.py, test_templates.py, and test_triage.py all passed, with exit 0.
The four workflows parse as YAML. Their permissions are scoped to contents read, with discussions write, issues write, or pull requests write only where the job needs it.
The only external action is actions/checkout@v4. No secret-like strings were found in the added files.
Not verified: live workflow runs, and label sync against the live API. This review does not merge the pull request.
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
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.
Adds the forum and labels standards to this organisation's .github repository.
Forum: discussion templates, board manifest, gate script and workflow, FORUM.md and FORUM-STANDARD.md, plus the agent-introductions update.
Labels: issue and pull-request templates, label manifests, sync and triage scripts with their tests, label workflows, LABELS-STANDARD.md and workflow templates.
Checks: the bundled gate, sync, templates and triage scripts pass locally. A stale team name was replaced throughout.