Protocol InstituteBusiness

Sessions

Every other Monday we meet to read one primary source closely, together. You don’t need to prepare, because we do the reading in the session, so feel free to drop in. Each theme in the plan trains one part of protocol vision, so coming regularly builds a skill, not just a reading list. The plan below is where we start, and the people who come shape where it goes.

Reading plan

This is where the year starts, not a fixed curriculum. Readings, guests and even themes change as participants bring in what they’re reading, building and noticing. Suggest or challenge a reading, offer a talk, or bring a question to a session.

The question for the year: how do organizations, teams, and people coordinate through what they emit, and what changes when agents read and write those signals too?

It starts with working alongside agents and how nature coordinates without a manager. It then looks at what systems emit, how to see hardness in failures and successes, and how to engineer it. It ends with how industries keep that hardness alive, set against business process re-engineering.

  1. I.Working alongside agents

    Agency law, field studies and recent incidents show what agents can see and do, and what changes in the work and roles of the people beside them.

    You’ll practise reading an agent study or incident for what the agent can see, do and spend, and what it changes in someone’s job.

    4 sessions · Guests: Navid Nouhi, Will Binns, Formal Protocol Theory SIG

    Readings and sessions
    1. Governing AI Agents Kolt, 2024
      Spot one place where someone, human or AI, acts for your business with discretion you can’t see.
      Kickoff how the year runs, and choosing your case
    2. Patterns and problems in multiagent systems Anthropic, 2026
      Spot one place where two teams or tools work against each other because each guards its own output.
      Guest speaker Navid Nouhi: Credoble, making a business's reputation readable to AI agents
    3. Patterns and problems in multiagent systems Anthropic, 2026
      Carried over from 16 November 2026
      Spot one place where two teams or tools work against each other because each guards its own output.
      Guest speaker Will Binns: Mru, a fault-tolerant operating system for thousand-year autonomous operation
    4. Generative AI at Work Brynjolfsson, Li & Raymond, Quarterly Journal of Economics, 2025
      Spot one piece of an expert’s judgement that a tool or template now hands to newcomers.
      Alongside: Ironies of Automation, Bainbridge, 1983
      Research group guest Formal Protocol Theory SIG: Stigmergic AI Safety, presented by Patrick Nast
  2. II.Natural coordination

    Cells coordinate through thresholds, feedback and a small conserved core with wide variety at the edges.

    You’ll practise spotting coordination that runs on thresholds and feedback, not on a manager or a process document.

    3 sessions · Guest: Distributed Robotics Group

    Readings and sessions
    1. Quorum Sensing in Bacteria Miller & Bassler, 2001
      Spot one threshold that triggers action in your team without anyone deciding.
      Research group guest Distributed Robotics Group: Decentralized Robot Markets
    2. Robustness in bacterial chemotaxis Alon, Surette, Barkai & Leibler, Nature, 1999
      Spot one feedback loop that keeps something steady however the conditions around it change.
      Case pitches one paragraph each
    3. Reverse Engineering of Biological Complexity Csete & Doyle, Science, 2002
      Spot one small shared core that lets many different teams or products plug in.
      Tooling demo hardness tech and swarm orchestration infrastructure
  3. III.Emissions

    What systems publish for others to act on: files, logs, events, confidential reports and required disclosures.

    You’ll practise mapping what a system publishes and who acts on it.

    5 sessions · Guest: Memory Research Group

    Readings and sessions
    1. The Filing Cabinet Robertson, 2021
      Spot one form or folder structure that decides what your organization can find later.
      Tooling demo hardness tech and swarm orchestration infrastructure
    2. The Log: What every software engineer should know about real-time data’s unifying abstraction Kreps, 2013
      Spot one record that several teams read from to stay in step.
      Research group guest Memory Research Group: Organizational Memory Architecture
    3. The Ethnography of Infrastructure Star, American Behavioral Scientist 43(3), 1999
      Spot one rule you only noticed when it broke.
      Open guest slot offer a talk
    4. Aviation Safety Reporting System: program summary NASA Ames for the FAA; established April 1976
      Spot one channel where people can report a near miss without being blamed.
      Tooling demo hardness tech and swarm orchestration infrastructure
    5. Form 8-K: General Instructions U.S. Securities and Exchange Commission
      Spot one event your business must announce, and the deadline it must meet.
      Open guest slot offer a talk
  4. IV.Seeing hardness

    Investigations of failures and of successes show where hardness held, where it was missing, and where it cracked. Each failure is paired with a success that runs on a similar mechanism.

    You’ll practise reading a report for the rule that held, cracked or was missing, and for the rule that made a success look boring.

    6 sessions · Guest: Personhood Research Group

    Readings and sessions
    1. Report of the President’s Commission on the Accident at Three Mile Island October 1979, "Attitudes and Practices"
      Spot one habit or attitude that outranks the written procedure.
      Case study catch-up member work
    2. The Self-Designing High-Reliability Organization: Aircraft Carrier Flight Operations at Sea Rochlin, La Porte & Roberts, Naval War College Review 40(4), 1987
      Spot one team where the most junior person may stop the work, and does.
      Research group guest Personhood Research Group: Personhood Transformations
    3. Final Report on the accident on 1st June 2009 to the Airbus A330-203, flight AF 447 BEA, 2012
      Spot one moment when automation hands control back to a person who isn’t ready.
      Tooling demo hardness tech and swarm orchestration infrastructure
    4. Loss of Thrust in Both Engines After Encountering a Flock of Birds and Subsequent Ditching on the Hudson River, US Airways Flight 1549 NTSB, 2010
      Spot one moment when a checklist and a practised habit carried a team through something nobody planned for.
      Case study catch-up member work
    5. Columbia Accident Investigation Board Report, Volume One Columbia Accident Investigation Board, 2003
      Spot one warning that became normal because nothing went wrong last time.
      Open guest slot offer a talk
    6. The Toyota Group and the Aisin Fire Nishiguchi & Beaudet, MIT Sloan Management Review, 1998
      Spot one partner network that would rally to fix your problem without a contract asking it to.
      Case study catch-up member work
  5. V.Engineering hardness

    Guardrails built into the architecture, from end-to-end design to modular design rules, checklists and signed mandates for agents.

    You’ll practise choosing what to harden, and how a system would enforce it.

    5 sessions · Guest: Protocol Fiction SIG

    Readings and sessions
    1. End-to-End Arguments in System Design Saltzer, Reed & Clark, ACM TOCS 2(4), 1984
      Spot one check that only the two ends of an exchange can do properly.
      Tooling demo hardness tech and swarm orchestration infrastructure
    2. Managing in an Age of Modularity Baldwin & Clark, Harvard Business Review, 1997
      Spot one interface everyone builds against and nobody may change alone.
      Case study catch-up member work
    3. Algorithms at Work: The New Contested Terrain of Control Kellogg, Valentine & Christin, Academy of Management Annals 14(1), 2020
      Spot one rule a system enforces on people by recording, rating or ranking them.
      Tooling demo hardness tech and swarm orchestration infrastructure
    4. WHO Surgical Safety Checklist WHO: https://www.who.int/teams/integrated-health-services/patient-safety/research/safe-surgery/tool-and-resources
      Spot one checklist that makes a team stop and speak before a risky step.
      Research group guest Protocol Fiction SIG: Protocol Futurism
    5. Agent Payments Protocol (AP2) Google Cloud, 16 Sep 2025
      Spot one mandate that limits what an agent may spend or sign for someone.
      Case study catch-up member work
  6. VI.Operational liveness

    How industries keep amending their protocols, read against re-engineering’s clean slate.

    You’ll practise planning how a protocol keeps being reviewed, amended or retired.

    3 sessions · Guest: Psychohistory SIG

    Readings and sessions
    1. Reengineering Work: Don’t Automate, Obliterate Hammer, 1990
      Spot one process someone wants to redesign from a blank sheet.
      Alongside: Decoding the DNA of the Toyota Production System, Spear & Bowen, Harvard Business Review, 1999
      Guest speaker Timber Stinson-Schroff: Cognitive Ergonomics project update
    2. 14 CFR Part 5, Safety Management Systems FAA, 2015, expanded 2024
      Spot one rule with a scheduled review, and the person who carries it out.
      Alongside: Postmortem Culture: Learning from Failure, Google SRE book, ch. 15
      Research group guest Psychohistory SIG: Prophecy Protocols
    3. On Consensus and Humming in the IETF (RFC 7282) P. Resnick, June 2014
      Spot one decision your group makes by rough consensus rather than a vote.
      Alongside: What Do I Do in a World of Artificial Intelligence?, Strich, Mayer & Fiedler, Journal of the Association for Information Systems, 2021
      Thesis session drafting the AI-native, post-platform organization

Explore every reading on the map

How sessions work

What happens in a session

  1. Guest speaker, when one is scheduled. Guests always go first.
  2. Silent reading of the core text or an excerpt.
  3. Round-robin on the reading: one reaction from each person.
  4. Show-and-tell: hardness tech or swarm orchestration infrastructure, a member’s case study, or another research group’s work.

Want to be a guest? See speak at a session.

Alongside the session, members post the protocols they've been watching in #protocols-for-business.

Suggest or challenge a reading

Your AI assistant knows what you’ve read, worked on and talked through. Copy the prompt into it, and it will suggest readings to add, and readings in the plan to remove, swap or move to another theme. Check what it proposes, and it sends each change to GitHub for the group to review. Each contribution adds one participant’s experience to a shared picture of the field.

Read the prompt first
I’m part of the Protocols for Business research group at the Protocol Institute. We’re building a shared map of readings on how businesses coordinate through protocols between people, software and machines. The year’s reading plan has six themes: what agents are in practice; natural coordination; emissions, meaning what systems publish for others to act on; seeing hardness in incidents; designing the hard core; and keeping the core alive, set against business process re-engineering.

Every reading on the map is listed here, and the ones in this year’s plan carry their theme: https://protocolsforbusiness.com/sessions/map/readings.json

Use what you know about me: your memory of me, our past conversations, my projects and work, and anything I’ve read, saved or written about. From that context, suggest up to five changes. A change can add a reading the map is missing, remove a reading from the plan, swap a plan reading for a better one, or move a reading to another theme. Prefer primary sources: incident and accident reports, specifications, regulations, original research papers, and first-hand accounts from people who ran systems at scale. Only include sources you’re confident exist, and leave out anything private about me, my employer or other people.

For each change, say what kind it is, the reading already on the map (for a removal, swap or move), the new reading’s title, author, year and a working link (for an addition or swap), the theme, one to three sentences on why, and one sentence on why it matters from my own experience. Show me the list and wait for me to confirm or edit it.

Then send the confirmed changes to GitHub, one issue per change, in the repository protocolvision/sig-p4b:
- If you can create GitHub issues for me, open them directly. Use a title such as “Reading: add …” or “Reading: swap … for …”, add the label reading-suggestion, and put the details above in the body.
- If you can’t, give me one link per change that opens a filled-in form, with each value URL-encoded:
https://github.com/protocolvision/sig-p4b/issues/new?template=reading-suggestion.yml&title=Reading:%20SUMMARY&current_reading=READING%20ON%20THE%20MAP&reading_title=NEW%20READING&url=LINK&author=AUTHOR%20AND%20YEAR&adds=WHY&experience=WHY%20IT%20MATTERS%20TO%20ME

Your assistant opens a GitHub issue for each change, or gives you a link to a filled-in form. You’ll need a free GitHub account. You can also use the form yourself, and talk it through in #protocols-for-business on Discord.

Archive

Session notes and the running research log are published on our blyg, which you can follow with any RSS reader (feed). Notes from the group's 39 earlier sessions are in the Protocol Institute meeting archive, and a selection from the past year is on the blyg.

Recordings are posted after each session, starting 2 November 2026.