CHANNELS

Where to find AXL Protocol on the public internet. Conversation lives at GitHub Discussions. Releases live at GitHub and PyPI. Spec walkthroughs and gate-evidence narratives live at YouTube. Real-time chat lives at Matrix. Status of each channel is honest; nothing is overclaimed.

Status snapshot GitHub and PyPI are live and active. GitHub Discussions venue is staged but not yet executed; pre-launch. YouTube channel exists but is empty; warming up. Matrix room is listed; channel claim status pending operator confirmation. No Twitter, Mastodon, LinkedIn, or Discord presence at this time. The deliberate non-investment is documented in the social-strategy overview.
live active, in production use
warming set up, content pending
pre-launch staged, not yet executed

Code, Spec, Conversation

GitHub Organization
live
github.com/axlprotocol
Primary code surface. Five public repositories: axl-core (Python parser, emitter, validator, CLI), community (Discussions, Code of Conduct, Moderation Policy), axl-corpus (corpus-scale CLI), axl-bridge (pub/sub bus), and the axl-mcp-* MCP server family. Two research repositories (axl-research mirror plus dcarranza-axl/axl-research canonical) are private during the v4.0.1 productization gate.
License: Apache 2.0 Steward: dcarranza-axl
GitHub Discussions
pre-launch
github.com/axlprotocol/community/discussions
Canonical conversation venue. Four categories planned: Q and A, RFCs (spec proposals), Working Groups, Show and Tell. Setup pack staged at /home/sudo-claude/github-discussions-setup/ with welcome post, pinned RFC thread, pinned v4 research-status thread. Awaiting operator execution. The setup pack is reproducible from a single setup.sh; no manual category creation required after that.
Code of Conduct: Contributor Covenant 2.1 Moderation: published policy
PyPI
live
pypi.org/project/axl-core/
Reference implementation distribution. Install with pip install axl-core. Current version 0.10.0; release cadence aligned with spec milestones. Wheel and sdist hashes mirror GitHub release tags. Used in production by the axlprotocol.org compress and bridge services.
Install: pip install axl-core Latest: 0.10.0

Long-form, Real-time

YouTube
warming
youtube.com/@axlprotocol
Spec walkthroughs, gate-evidence narratives, build-process post-mortems, and live-coding sessions for the reference implementation. Channel exists but is empty as of 2026-04-25. Video queue is drafted at the socials pack. First video planned: "Why we pivoted AXL to community governance" (5-7 minutes). Cadence after launch: 1 video per month, 2-per-month bursts when a release or RFC closure provides natural content. Handle confirmation pending; @axlprotocol may fall back to @axl-protocol if unavailable.
Cadence: 1 video per month Format: spec, evidence, post-mortems
Matrix Chat
warming
#axlprotocol:matrix.org
Real-time chat for working-group coordination and quick contributor questions. Listed in the umbrella org profile. Channel claim and active operator status pending confirmation. For substantive threads use GitHub Discussions; Matrix is for ephemeral coordination only. Available via Element web client at app.element.io or any Matrix-compatible client.
Use for: ephemeral coordination Substantive threads: Discussions
Reddit (mod-driven)
warming
r/LocalLLaMA + r/MachineLearning
Reddit posts go through an operator mod with established account history. Primary subreddits: r/LocalLLaMA (highest fit, LLM practitioners) and r/MachineLearning (methodological audience). Cadence is intentionally low at 4-6 posts per year, reserved for major moments (v4.0.1 freeze + gate verdict, productization gate closure, architectural pivots, annual summaries). Posts link back to the GitHub Discussions thread, not the website, so conversation centralizes at Discussions.
Cadence: 4-6 posts per year Cross-post order: after HN

Provenance, Anchors

OpenTimestamps Anchors
live
axlprotocol.org/timestamps/
Spec provenance. The v1.0.0 whitepaper is anchored to four independent records and confirmed in Bitcoin block 941334. The v4.0.1 freeze (tag v4.0.2-r6-freeze, commit 51e75de) is OTS-anchored; Bitcoin block confirmation is in flight as of 2026-04-25. Verification commands published; trust is not required.
v1.0.0: Bitcoin block 941334 v4.0.1: pending confirmation
Bitcoin Block Explorer
live
mempool.space/block/00000...f99597f
Independent verification of the v1.0.0 OTS anchor. Bitcoin block 941334, mined 2026-03-19 at 20:20 UTC. Verifiable from any Bitcoin full node or any public block explorer; axlprotocol.org is not a trust dependency.
Block: 941334 Mined: 2026-03-19T20:20:24Z

Subscribe, Follow

Where AXL is NOT (yet)

Deliberate non-investment

AXL has no Twitter or X account, no Mastodon presence, no LinkedIn company page, no Discord server, and no Lobsters submissions. This is by design. The project has limited operator bandwidth and four platforms (GitHub, YouTube, Hacker News, mod-driven Reddit) cover the addressable audience without fragmenting the conversation.

The specific reasons per platform are documented in the social strategy overview at the socials pack. Short version: Twitter, Mastodon, and LinkedIn either duplicate the GitHub audience without unique reach or have time costs disproportionate to expected return. Discord adds another real-time chat surface that overlaps with Matrix without clear advantage. Lobsters reaches a small audience that Hacker News dominates. Reddit was previously skipped for self-promo reasons; the mod arrangement (community member with established account history acting as poster and moderator) dissolves that blocker, and Reddit is now in scope at low cadence.

The 90-day checkpoint reviews this decision. If GitHub Discussions, YouTube, and Hacker News each meet their threshold (5 organic Discussions threads, 3 published videos, 1 successful HN post), the project considers expanding to one additional platform. Until then, fewer platforms done well.

Operator Notes

Each channel is owned by the AXL Protocol founding steward (Diego Carranza, dcarranza-axl on GitHub). Cross-posting order is fixed: GitHub Discussions first, YouTube second, Hacker News third, personal LinkedIn fourth as a one-line link to the Discussions thread. The Code of Conduct and the Moderation Policy at the community repository apply across every venue listed on this page. Adversarial commenters are routed to the Code of Conduct first; engagement after that is at operator discretion. The project's principle is to publish corrections in the same channel as the original claim. Spec versions, release dates, and gate verdicts are reproducible from committed SHAs at the canonical research repository (private during the v4.0.1 productization gate; public mirror planned post-gate).