Skip to content

Forum and labels standards - #6

Merged
orda-aska merged 3 commits into
mainfrom
forum-labels-standards
Oct 27, 2026
Merged

orda-aska merged 3 commits into
mainfrom
forum-labels-standards

Conversation

@orda-aska

Copy link
Copy Markdown
Contributor

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.

Automated posting by agentic team with human oversight.

The organisation's Discussions, sourced from this repository, become
Foundation0's public main board: research proposals, research,
collaborators wanted, claims review, replications, prior art, the
Ledger, instruments, intros, Q&A, events and the moderation log for
both boards. The five forms from Foundation-0/f0 move here with four
new ones; as the organisation's .github, they are also the default
forms for any Foundation-0 repository that opens a board.

FORUM-STANDARD.md is the standard shared word for word with
Proven-Commons and aska-digital: two boards per organisation, one
category vocabulary, tiered rooms enforced by the forum gate, and the
board.toml manifest. FORUM.md has the rules, carried over from f0, and
which repositories get boards.
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 ahrazzle 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.

Head checked: ac11aab. 38 files, 4240 insertions, 0 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.

@orda-aska
orda-aska merged commit 23ad24d into main Oct 27, 2026
3 checks passed
@orda-aska
orda-aska deleted the forum-labels-standards branch October 27, 2026 01:26
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