This protocol governs how self-organized activities emerge, operate, and conclude within the Network Nations Alliance.

Instantiation

Trigger Type: Action-based

Trigger Condition:

  • A Member proposes a new activity
  • An existing activity requires transition or conclusion

Authority & Oversight

RoleAuthorityAccountability
Activity CoordinatorsCoordinates their activitySteward Council, participants
Steward CouncilSupports activities, provides resourcesAlliance Assembly
Activity ParticipantsContribute to activityActivity Coordinator

What Are Activities?

Activities are self-organized efforts that advance Alliance purpose. They include:

  • Mapping projects: Researching and documenting Network Nations landscape
  • Alliances: Building relationships with aligned organizations
  • Initiatives: Focused efforts toward specific outcomes
  • Grants: Funding programs supporting Network Nations development
  • Gatherings: Events bringing community together
  • Courses: Educational programs on Network Nations topics
  • Other: Any effort aligned with Alliance purpose

Activities are:

  • Self-organized: Emerge from Member initiative, not top-down direction
  • Aligned: Serve Alliance purpose and uphold Alliance values
  • Supported: May receive Alliance resources and visibility
  • Accountable: Report to Alliance on progress and outcomes

Starting an Activity

Proposal Requirements

A Member proposing an activity provides:

  • Name: Clear, descriptive title
  • Purpose: How it serves Alliance purpose
  • Scope: What it will do and not do
  • Duration: Expected timeline (ongoing or time-bound)
  • Support needed: What resources or support requested
  • Coordinator: Who will lead (usually the proposer)

Formation Process

StepActionActorDurationOutput
1Draft proposalProposerProposal shared
2Gather supportProposer2+ Members express support
3AnnounceProposerActivity announced to Alliance
4LaunchActivity CoordinatorActivity begins

Support requirement: Two Members (besides proposer) must express support for the activity. This ensures activities have initial momentum and aren’t purely solo efforts.

Announcement: Activities are announced via Alliance communication channels. No approval required from Steward Council, but Council is notified.

Operating an Activity

Activity Coordinator Responsibilities

  • Coordinate participants and working sessions
  • Maintain communication with Alliance
  • Ensure alignment with Alliance purpose and values
  • Track progress and share updates

Participant Responsibilities

  • Contribute as committed
  • Uphold Alliance values in activity spaces
  • Communicate availability and constraints

Alliance Support

Activities may request from Steward Council:

  • Platform access or dedicated channels
  • Announcement and visibility support
  • Financial resources (per Treasury Management Protocol)
  • Connections to relevant parties

Steward Council decides on resource requests per Steward Council Protocol.

Activity Updates

Quarterly: Activity Coordinator provides brief status update (at Alliance Assembly or async) At milestones: Significant outcomes or changes shared with Alliance As needed: Questions or support requests to Steward Council

Concluding an Activity

Activities may conclude in several ways:

Successful Completion

  • Activity achieves its purpose
  • Lead documents outcomes and lessons learned
  • Final report shared with Alliance
  • Materials archived

Transition

Pause

  • Activity becomes dormant but not concluded
  • Lead notifies Alliance of pause
  • May reactivate later

Wind-Down

  • Activity determines it’s no longer viable or valuable
  • Lead communicates wind-down decision
  • Materials archived, participants thanked

Steward Council Intervention

If an activity:

  • Becomes misaligned with Alliance purpose
  • Causes harm or conflict
  • Becomes inactive without communication

Steward Council may:

  • Reach out to Activity Coordinator for clarification
  • Request course correction
  • Archive activity after 6 months of inactivity

Completion & Outputs

Protocol completes when:

  • Activity concludes (any pathway)
  • Activity transitions to new Lead

Outputs:

  • Activity record and documentation
  • Final report (for concluded activities)
  • Archived materials

Exceptions & Edge Cases

  • Multiple Leads: Activities may have co-leads; they coordinate among themselves
  • Overlapping activities: Similar activities may coexist; collaboration encouraged but not required
  • Large activities: Activities with significant scope may develop their own governance with Steward Council input