Repository navigation
Disclosure: Commercial Interest #626
Description
I am a maintainer in this repository, and I am recording a commercial interest so that it is on the record before it bears on any decision.
I build Custodian, a key broker for model weights that uses the Weight Custody Manifest SDK as a dependency rather than a fork.
- I will note this interest on any proposal where it applies, whether I am proposing it or taking part in its review.
- I will recuse where Custodian's own design is the question.
- I will not present Custodian as endorsed by this project or as the reference implementation. It is neither.
- I will update this notice if the interest changes materially.
Mohammed Zoheb Shaik
Activity
github-actions commentedon Sep 9, 2026
🟡 Contributor Check: MEDIUM
Automated check by AgenTrust Contributor Check.
imran-siddique commentedon Sep 11, 2026
Accepted, and on the record. Thank you for filing it before it bore on anything rather than after.
The four undertakings are the right ones, and the third is the one that matters most to this project: not presenting Custodian as endorsed or as the reference implementation. An SDK with a commercial dependant is healthy; an SDK whose dependant is read as its blessed implementation is not, and that distinction is easier to protect before anyone has reason to blur it.
Recusal where Custodian's own design is the question is accepted as stated. It does not extend to the SDK itself: you remain a maintainer on the dependency and your review there is wanted, which is the ordinary position for anyone who builds on something they help maintain.
Two follow-ups, neither a criticism of the filing.
The disclosure is missing from the repository the interest actually depends on. You have filed in
agent-manifest,ca2aandcmcp. Custodian depends on the Weight Custody Manifest SDK, andweight-custody-manifesthas no disclosure. That is the one repo where a WCM-dependent commercial interest is most likely to bear on a decision, so please file there too.A standing disclosure should not live only in an issue. An issue can be closed, and it is not somewhere a reviewer looks before weighing a proposal.
GOVERNANCE.mdexists inweight-custody-manifest,cmcpandagent-manifest, which is where a reader goes for exactly this. Proposing: add a short Disclosures section to eachGOVERNANCE.mdnaming the interest and the recusal scope, and reference this issue as where it was first recorded. Once that lands these can close, with the durable record in the file and the provenance in the history.Happy for you to carry that as a PR, or I will if you would rather not be the one editing the governance file that names you.
zohebk8s commentedon Sep 24, 2026
@imran-siddique Sorry for the delayed response; this slipped past me.
Thank you for the clear review and guidance.
GOVERNANCE.mdPRs: Please do carry out the PRs adding the Disclosures section across the repositories. Having project leadership author and land the governance updates directly provides the cleanest record and avoids any optics around me editing a file named after myself.weight-custody-manifestfiling: Because I'm not a maintainer onweight-custody-manifest, the repo's issue template configuration doesn't present an open blank issue option for non-maintainers. Would you prefer to open the tracking issue there directly, or should I submit the disclosure via one of the available issue forms (e.g., general discussion/task)? Alternatively, you could include the WCM standing disclosure directly in yourGOVERNANCE.mdPR for that repo and reference this issue thread as the provenance.Let me know which route you prefer for WCM, and we will get it aligned.
imran-siddique commentedon Sep 24, 2026
The disclosure is now recorded in GOVERNANCE.md via #687. Closing this tracker.