Logos Assembly

Evangelism Plan - Q1 2026

5 min read

This is currently a WIP draft, not approved or finalized.

Current Priorities

Technical Communication

  • Content pipeline is active — see Content Tracker for full status
  • Browser Privacy article — currently under review; Jinho has validated interactivity works within the Logos Press Engine
  • Intro to Logos (Logos as an Operating System) — in review, next article queued for publication. Draft available with public review on forum
  • Blockchain Privacy Leaks — published
  • After the current two articles are published, prioritization of the remaining proposed articles (Anonymous Block Proposers, Gasless L2 RLN, Logos Core Architecture, Privacy-Preserving File Sharing, libchat SDK) will be determined

Specification Culture and Alignment

  • Specs repo unified (specs-rfc-repo) and specs-front-end operational — positive org feedback
  • Filip and Florin leading the lion’s share of ongoing effort
  • Next milestone: Define and publish a “documentation home” for specifications — guides, examples, justifications, tooling — as an org-wide reference
  • Alignment survey (alignment-survey-2025) has started detailing initiatives and results from specification culture changes
  • Org feedback has been positive toward the changes made so far

All-Hands Planning and Execution

  • In full swing — draft agenda shared and being iterated on
  • Working with all section owners to ensure delivery expectations are clear and up to date
  • Agenda document to be incorporated into Assembly site (currently circulated as standalone HTML)
  • Brief to be generated from agenda content

Previous Quarter’s Retro

General Notes

This role was defined and honed last quarter, so there has been a bit of an on-ramping and momentum building as the org adjusts to my new efforts. That being said, even among the ambiguity, it has been fruitful and invigorating for me. I am very appreciative of everyone’s excitement for this role and me being the one that fills it.

I haven’t received much critical feedback in my new role, but what I have gotten has been around my need to improve clarity of progress. The roles starting initiatives last quarter were laid out, but there was no “project management” effort that ensured the progress and status of each initiative was trackable. There will be efforts this quarter to rectify that issue such that anyone watching this rep can see how things have and are going.

Org wide agreement on specifications: what and how (Critical Focus)

Significant progress was attained in this initiative. It was brought on as a critical focus half way through the quarter but efforts have been fruitful

  • All specifications have been unified into a single repo, specs-rfc-repo.
  • A new specs-front-end has been created and shopped around to navigate the available specifications. this is an effort to mimic the behavior of IETF’s data tracker
  • All teams have committed to leveraging this repository for anything specification related
  • The boundaries of how we differentiate between a “specification” and any other associated technical documentation is under way, but there is a general consensus among the development leads. This is a significant improvement from before where expectations were all over the place.
  • A #lips channel was created in the Logos Discord for all leads and relevant stakeholders to discuss this effort. It is designed to be a temporary channel until a process is put into place
  • Interviews were done across the team leads and stakeholders to understand their gaps and preferences on both what a specification is and how it should be used. This lead to a clear understanding of the pros and cons of each approach (e.g. IEFT-based process of Vac vs Executable Spec-driven process of Nimbus/EF/Nomos).

Things that need to improve from here:

  • Unified understanding around what we call each type of technical document, how they’re inter-related, and what information goes into each one.
  • General agreement and understanding on the process of creating and iteratively improving these documents.
  • The tooling associated with ensuring that shared documents conform to some reasonable similarity without getting in the way of engineering and communication.

Maintenance of Logos Assembly (this site)

  • Serving as shared reference for content work and resource tracking
  • Doubling as project management surface — leveraging agentic AI to systematically maintain status and progress so others can track what’s happening
  • Addressing Q4 feedback around improving clarity of progress

Logos Circles coaching

  • Taken a backseat relative to other priorities
  • Key alignment achieved: shared understanding of why and what needs to happen — linking Circles outcomes to tech stack development
  • All Hands will include Circles Stewards for the first time — dedicated time scheduled to dig into the Circles ↔ tech stack linkage

Logos.co Website monitoring

Strategy Roll-out and uptake

  • Identified as a need via the alignment survey
  • Now owned by EcoDev, informed by the evangelist starting plan
  • Evangelist role: advisory input, not primary driver

Logos Broadcast Network creation and contribution

  • Now owned and operated by Chair, folded into Comms (officially led by Jonny)
  • Comms is under EcoDev alongside Movement (led by Santi)
  • Evangelist contribution to LBN is indirect — content production rather than network operations:
    • Townhalls and Logos strategy updates
    • Technical writing that serves as foundation for talking points and derivative material
    • Updated and aggregated pages for weekly dev updates (both Vac and Logos)
    • This website (Assembly) as navigable reference

Logos Stack Technical Diagram contribution and distribution

  • Current diagram deemed sufficient by KSR for Testnet v0.1
  • General enough but accurate enough to serve as reference for “what Logos is”
  • Used as context in the Intro to Logos article and tracked in Content Tracker
  • Foundation to build on — updates expected for Testnet v0.2+ as changes occur

All Hands Planning contribution

Contextual AI / CaaS

  • Low priority for this role — continues in that fashion
  • Owned by BI team; evangelist contributes by providing structured, RAG-friendly content
  • Progress tracked at infra-bi issues
  • MCP Server PoC (Claire / Context7) — status unknown, check with BI team

Graph View