feat(dir): add optional trust ranking reference extension

[leocharny]

No description provided.

[leocharny]

Summary

This PR adds a reference-only trust ranking PoC as an optional extension.

It is intentionally:

• additive (no core behavior changes)
• non-authoritative
• not a security system or standard

The goal is to provide a concrete artifact for discussion around
how trust-related signals could influence discovery and ranking.

What’s included

• A minimal trust ranking interface
• A toy reference implementation with explainable output
• Sample data and a CLI runner
• Basic unit tests (stdlib only)
• Documentation clarifying scope and limitations

What’s not included

• No protocol changes
• No server-side enforcement
• No governance or policy assumptions

Feedback welcome.

[ramizpolic]

Hi @leocharny, thank you for the PoC submission. Would you mind restoring the original formatting on unaffected file changes? It makes it a bit difficult for us right now to review the changes.

Also, would you be interested in joining our Community Meeting to demo these changes? I think there is a lot of interest on this.

[leocharny]

Superseded by a clean PR that restores upstream formatting and limits changes to the trust-ranking PoC: #791

[leocharny]

Hi Ramiz, thanks for the review and for the suggestion. I rebuilt the PR on top of upstream/main and removed all formatting-only changes so the diff is now limited to the trust-ranking extension plus a small README hook. Here’s the clean PR: #791 And yes, I’d be happy to join the Community Meeting and do a short demo. I’d keep it strictly as a reference PoC to spark discussion, not as a proposed standard or production approach. Let me know which meeting works best and how much time you’d like me to plan for. Best, Leo

…

On Mon, Jan 5, 2026 at 3:57 AM Ramiz Polic ***@***.***> wrote: *ramizpolic* left a comment (agntcy/dir#790) <#790 (comment)> Hi @leocharny <https://github.com/leocharny>, thank you for the PoC submission. Would you mind to restore the original formatting on unaffected file changes? It makes it a bit difficult for us right now to review the changes. Also, would you be interested joining our Community Meeting to demo these changes? I think there is a lot of interest on this. — Reply to this email directly, view it on GitHub <#790 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM5ZLC737MHRU2GLRNXX34D4FIRPJAVCNFSM6AAAAACQH4WEGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBZGQ4TGMZUHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>