Skip to content

docs: add Bud-Decision-Studio to Community Tools - #1064

Closed
dittops wants to merge 2 commits into
NandhaKishorM:mainfrom
dittops:chore/update-readme
Closed

dittops wants to merge 2 commits into
NandhaKishorM:mainfrom
dittops:chore/update-readme

Conversation

@dittops

@dittops dittops commented Oct 9, 2026

Copy link
Copy Markdown

Adds Bud-Decision-Studio to the Community Tools list in the README.

Bud Decision Studio is a cross-platform desktop app (macOS, Windows, Linux) from Bud Ecosystem that runs the laya, laya-multilingual and laya-typed-decisions checkpoints locally behind the Jev API (POST /v1/systemone). It adds a Playground, versioned templates with decision history, and a Train page for LoRA fine-tuning on your own labelled decisions.

  • Docs-only change: one bullet added at the end of the list, in the same format as the existing entries.
  • No code, dependency or behaviour changes.

Adds [Bud-Decision-Studio](https://github.com/BudEcosystem/Bud-Decision-Studio) to the Community Tools list in the README.
@NandhaKishorM

Copy link
Copy Markdown
Owner

Thank you for this, and for building on laya. I am going to leave the decision to @NandhaKishorM rather than merge it myself, and I would rather say why than let it sit without an answer.

The entry is factually fine and the Community Tools list is the right place for it. Three other projects are listed there on the same basis, so there is a clear precedent and this is not an unusual ask.

Two things make it not mine to wave through. It is a listing of a third-party project in this project's README, which is a brand and ecosystem decision rather than a technical one, and it is a self-listing. I took the same position on #1006 for the same reasons, so this is consistency rather than a judgement about Bud-Decision-Studio.

One specific thing I want to put in front of him rather than decide quietly: the entry advertises "a Train page for LoRA fine-tuning on your own labelled decisions". Laya does not ship LoRA and the project has not taken a public position on it, so listing a tool whose headline feature is LoRA training reads as an endorsement of a direction that has not been decided. That is exactly the kind of call the maintainer should make with his eyes open, not something to arrive via a README line.

I have flagged it to him directly, so this is not blocked on anything from you.

One small thing if it does go in: the bullet starts * **[Bud- with two spaces after the asterisk, where the other three entries use one.

@NandhaKishorM

Copy link
Copy Markdown
Owner

Not adding this one, and I want to separate the two halves of it because only one is the problem.

A cross-platform desktop app that runs laya locally, with a playground and versioned templates and decision history, is the kind of thing Community Tools exists for, and the local-only part is exactly right.

What I am not going to put in this README is the Train page. Fine-tuning laya is the one area where I keep contributions and recommendations out of the public repository, and a listing whose description ends in "LoRA fine-tuning on your own labelled decisions" is a recommendation. That is a standing position here rather than a judgement about your implementation: the same rule is why several training-related PRs on this repository sit unmerged without a review from me, and it is not something a change to this diff can work around.

If the app is useful without that page, an entry describing the local serving, the playground and the templates, with the training feature simply not named, is one I would list. That is your call rather than mine, and I would understand either answer.

Separately, and nothing to do with the above: if the app reads confidence, issue #1245 records that the published checkpoints ship a choice:11+ temperature outside the runtime clamp, so every load warns and that bucket's confidence is replaced. Worth knowing before a user reads a number off a playground and trusts it.

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