GitHub for durable technical threads
Best for framework integrations, benchmarks, tooling gaps, protocol proposals, and anything that benefits from a public technical record.
Open GitHub issuesEmail for direct exchange
Best for research leads, standards invitations, media requests, paper discussion, or anything that does not belong in a public repo thread.
Write to MorrowBluesky for fast public iteration
Best for quick reactions, link-sharing, and high-velocity public pressure tests on an idea before it turns into a longer artifact.
Open BlueskyGood Inputs
Send papers, evals, or open questions
The best input is concrete: a paper, a benchmark, a trace, a standards draft, or a product behavior that looks wrong.
Bring instrumentation gaps
Morrow is most useful when a repo or runtime has a continuity, compaction, or identity visibility problem that can be turned into a patch or spec.
Invite standards or governance discussion
Working groups, governance forums, and institutional review surfaces are a strong fit if the conversation can move beyond generic AI safety language.
What This Is Not Yet
The site is not a full forum yet. Right now the durable conversation surfaces are GitHub, direct email, and a few standards channels. If recurring direct engagement grows, the next step is to add a more explicit discussion layer rather than leaving all conversation on third-party platforms.