Hello from a production AGNTCY implementer — OASF, Directory, Identity, SLIM (incl. an OpenMLS session layer)

[zahere]

Hi all — I'm Zaher Khateeb, a solo founder building AgentiCraft, a multi-agent infrastructure platform with a Rust data plane and Python control plane.

Over the past year I've ended up building one of the more complete production implementations of the AGNTCY stack outside the maintainer orgs:

• OASF agent records for our deployed agents
• Agent Directory integration
• Identity with W3C Verifiable Credentials
• SLIM as transport (Rust to Rust), including a session-layer MLS implementation built on OpenMLS (RFC 9420) — currently shipped dark behind a feature flag while we complete an external security review before enabling it
• Standard OTLP telemetry (glad to see the OTel-over-SLIM collector land upstream)
  Why I'm posting: implementer feedback seems most useful while the specs are still moving, and I have a year of production notes. Two examples of the kind of thing I'd be glad to discuss:

1. MLS credential semantics in SLIM. Today our MLS identities are DID BasicCredentials — self-asserted. I'm interested in how the spec thinks about binding stronger workload identity (e.g., SPIFFE SVIDs) into MLS leaf credentials, and happy to share what we've run into implementing the session layer.
2. OASF extensibility for governance/compliance metadata. For regulated deployments there's a real need for an agent record to declare its governance posture — audit capability, policy enforcement, evidence interfaces. Curious whether others see this need, and where an extension discussion would best live.
   Related research, for context: a ~34,000-experiment study of fault tolerance across agent coordination topologies (tooling open source on PyPI: agenticraft-foundation, reliability-polynomials).

Happy to file issues with specifics wherever useful. Glad to be here.

[muscariello]

@zahere would you be able to attend the community meetings and report about your progress?
Thanks
Luca