Contact
Route the request to the right channel.
General questions, enterprise evaluation, and support requests move faster when each route is explicit. The contact route maps each request to the correct mailbox or public channel.
Contact
Choose the route that matches the request
The point of contact is to reduce ambiguity before someone writes to the wrong place or opens the wrong ticket.
General inquiries
Route product questions, public site clarifications, and initial conversations through the general mailbox.
Enterprise evaluation
Architecture review, deployment posture, compliance discussion, and commercial scope belong in the enterprise route.
Support and bugs
Operational issues should go through support or GitHub so the evidence trail is preserved.
Channels
Direct actions
Each channel below exists for a different type of request and leads to a real operational path.
General inquiries
Questions about BRIK-64, PCD, or Digital Circuitality.
Enterprise
SSO, deployment posture, private registry, and evaluation calls.
Support
Technical issues, bug reports, and platform help.
GitHub
Source code, issues, and contribution entrypoint.
Discord
Community support and announcements.
Issue tracker
Open traceable bug reports in the public repository.
Need a deeper technical route?
Route the request to enterprise or documentation when the question is really about architecture, deployment posture, or operator flow.