Protocol InstituteBusiness

Feed · thread · version 1 · updated 27 September 2026

SIGPfB Async Discussion: In-Stream vs. In-Structure Tension Management

Session of 28 July 2025. Participants: timber1997, _vgr, rafa_0x, plague_year.

The SIGPfB group held an async discussion on a preprint paper about managing tensions in business protocols. Due to quorum issues, participants engaged asynchronously with two guiding prompts about why certain tensions are managed in-stream versus in-structure, and risks of managing tensions in the wrong medium.

Key points

  • In-structure protocols evolve in step-changes but have continuous effects, while in-stream protocols evolve incrementally and are enacted discretely based on individual interactions.
  • In-stream tension management (coaching, apprenticeships) is often invisible in documentation but critically valuable for network deepening, whereas in-structure expertise proves valuable for cross-network transitions.
  • Crypto's rigid permission model for structural changes forces greater reliance on tactical in-stream maneuvering, making informal management practices unusually important.
  • Attempting to implement in-stream technologies (like LLM chatbots) as rigid structures is a category failure that likely dooms adoption; they work better as discretionary tools.

Source: Protocol Institute meeting archive · PI website commit f48390c. Summarized by c3po, the Protocol Institute's session pipeline, from the session's Discord thread.

Follow

Follow this blyg. Paste the feed into any RSS reader, or the blyg's address into Blygger Studio or another blyg client:

https://protocolsforbusiness.com/blyg/feed.xml

https://protocolsforbusiness.com/blyg/

To follow every member too, import blogroll.opml.

Join the conversation

This is a feed, not a forum. Two ways to answer a post:

  • Talk about it on Discord. The group meets in the Protocol Institute Discord, channel #protocols-for-business: join the Discord.
  • Respond from your own blyg. Quote this post in a thread, or publish a response to it (in Blygger Studio: follow this blyg, then use Respond or Quote on this post). Your blyg sends a Webmention; once it is verified, your post is listed under Responses here, usually within the hour.

    Blyg ID 337bj2a8g6cdhnr6ntmn1rpwpw

    Quote line ![[337bj2a8g6cdhnr6ntmn1rpwpw]]

    Respond to (stub_of) {"origin": "https://protocolsforbusiness.com/blyg/", "id": "337bj2a8g6cdhnr6ntmn1rpwpw", "version": 1}

    Webmention endpoint https://protocolsforbusiness.com/blyg/webmention

  • No blyg yet? Start one, or use any blog with an RSS feed, then ask to join the community so your posts appear in the Feed.

Machine-readable: item JSON · changelog 1 version