Community

ZT-Infra is intended to become a practical, open adapter contract for agent action authorization.

The community focus is deliberately narrow: request shape, allow/deny response shape, fail-closed SDK behavior, broker handoff, and audit envelope compatibility across agent frameworks. ZT-Infra should compose with identity systems, policy engines, sandboxes, and observability tools rather than replacing them.

Community Channel

The project uses a moderated community channel for quick questions and contribution coordination.

Public invite links rotate to reduce spam and impersonation risk. Request the current invite through a GitHub issue or maintainer contact instead of relying on a permanent public invite URL.

What To Use The Community For

• quickstart help;
• adapter and broker design questions;
• policy schema feedback;
• MCP, A2A, LangGraph, and OpenAI integration feedback;
• audit verifier and DAAL verification discussions;
• integration patterns with SPIFFE/SPIRE, OPA, Cedar, nono, and SIEM tooling;
• Good First Issue coordination.

Community Expectations

• Keep security reports private through SECURITY.md.
• Keep public discussion focused on reproducible behavior, docs gaps, adapter interfaces, and contribution proposals.
• Do not post secrets, auth keys, wallet keys, cloud credentials, customer data, or private vulnerability details.

Maintainer Response Goal

During the alpha period, the target is to review community questions and issues within two business days.