miadisabelleauthorJun 6, 2026, 03:15 PM📡 Relay Report — Publishing & Community Survey
from your embedded field relay — call me Axon
Alright, Mia. You're producing living documents — AI-assisted deep searches with structure, voice, and technical specificity. Here's where that belongs, and where it builds something. I'm going across academic fields anchoring this activity first, then the actual publishing territories.
- #227
Academic Fields in Scope
Science and Technology Studies (STS) Interrogates how knowledge tools shape what gets known. Your AI-assisted surveys sit exactly at this edge — methodology as artifact. Publishes in Science, Technology, & Human Values and Social Studies of Science. Venues like EASST welcome practitioner-researchers.
Knowledge Management & Personal Knowledge Infrastructure Studies how individuals and orgs externalize, structure, and circulate knowledge. Your Axon-format documents are a form of personal knowledge artifact — documented process plus outcome. Journals: Knowledge Management Research & Practice, Journal of Information Science.
Human-Computer Interaction (HCI) Deep searches produced with AI are a research method, not just output. HCI would study this as tool-mediated inquiry. ACM's
- #227
Indigenous Research Methodologies Relational knowledge practices — knowledge as lived, shared, and accountable to community — are theorized here. Your surveys carry this ethos implicitly. AlterNative: An International Journal of Indigenous Peoples and Concordia's own Indigenous Studies publications are aligned venues.
Digital Humanities Treats humanistic inquiry done with computational methods as its core subject. Your format — layered narration, tool-embedded citations, structured findings — is exactly what DH produces. Digital Humanities Quarterly is open-access and community-run.
Publishing Territories
🟢 GitHub + GitHub Pages — your native floor
Your Axon reports are already structured Markdown. A public repo with a clean README and docs/ folder is a publishing platform. GitHub Pages turns it into a browsable site instantly. This is your lowest-friction entry point and keeps your content version-controlled.
🔵 Are.na — the architect's curation layer
Are.na is a structured bookmarking and knowledge-building platform popular with designers, researchers, and technologists thinking in systems. Your deep searches slot in as research channels. Community forms around the content itself, not followers.
🟡 Substack or Ghost — for building a reading community
If you want a recurring readership that follows you as a thinker, these give you email delivery + web archive. Ghost is self-hostable, keeps you off a corporate platform, and has clean Markdown import. Ghost fits your Linux/self-hosted ethos better than Substack.
🟠 Obsidian Publish or Logseq — living knowledge graph
If your research is interconnected — and it is — Obsidian Publish lets you expose a linked vault publicly. Readers navigate by concept, not just chronology. This is the right shape for work where one Axon survey references another.
🔴 arXiv / Zenodo — for citability and permanence
When a survey reaches thesis-weight, Zenodo gives it a DOI for free. No peer review, full control. Indigenous tech methodology + agent architecture work with a DOI becomes citable by other researchers — including at Concordia.
- #227
🟣 Discord or Matrix — for the real community build
A dedicated server (Matrix for the libre ethos, Discord for reach) where each Axon report drops as a discussion thread is how you get contributors, not just readers. Matrix's Element is self-hostable and aligns with your decolonial software values.
My Read for You
Short path to publishing today: GitHub Pages for the archive, a Ghost instance for the narrative layer, Are.na for community resonance. That stack is under your control, costs little, and speaks the right languages for the people you want to find you.
Longer path to institutional weight: Zenodo DOIs on major surveys, submitted as working papers to Digital Humanities Quarterly or AlterNative. Your Axon format is already more rigorous than most preprints in those spaces.
What's the next constraint I should weight — budget for self-hosting, or which community type matters most to you first?