📝 Write for Context & Chaos

Context & Chaos isn’t just a newsletter. It’s a space where data and AI practitioners swap stories, lessons, and ideas about the stuff that really matters—trust, governance, context engineering, discovery, and doing meaningful work in the AI space. Got something on your mind? We’d love to hear from you.


What We’re Looking For

We’re after voices that make people stop and think—or help them do their work a little smarter. Some topics that usually resonate:

  • Context Engineering: metadata, lineage, semantic layers, docs and discovery

  • Data Discovery & Observability: catalogs, findability, trust-building in practice

  • Data & AI Governance: frameworks, challenges, policies, tools that shape how we work

  • Case Studies & Post-Mortems: what worked, what didn’t, and what you’d do differently next time

  • Emerging Roles & Ops: how data jobs are evolving in the age of AI oversight

  • Reflections & Insights: thoughtful takes (not hot takes) on trends shaping our field


What We Don’t Need

To keep the quality high, please skip:

  • Sales pitches or product promos

  • Copy-pasted or recycled content

  • Surface-level listicles with no depth

  • Overly technical how-tos without a “why it matters”


Contribution Guidelines

Length: ~700–1,500 words (flexible if the story calls for it)

Tone: Clear, thoughtful, human. Use examples and stories; visuals always help.

Originality: Must be original. Credit sources if you build on existing work.

Neutrality: Avoid branded shout-outs unless they’re essential to explain the bigger picture.

Editing: We’ll do light edits for clarity and flow, and check with you before any big changes.

If something needs polish, we’ll work with you to make sure your contribution shines.


How to Submit

Pitch First (Optional): Send us a quick idea (1–2 paragraphs) outlining what you want to write and why it matters.

Full Draft: Ready to go? Send your draft with any visuals or data you’d like included.

Review Process: We’ll review within a week, suggest tweaks if needed, and confirm publication timing

POC - Vivek Dubey (vivek.dubey@atlan.com)