NOTICE
This is still a work in progress as the document and materials to go with it are still being developed. Items marked TBD are To Be Developed.
Grand Unified Plan Protocol Infrastructure #
Credit: Schwarzenarzisse (pixabay)
The PNARS Grand Unified Plan Protocol Infrastructure (GUPPI) is a modular, functional framework for decentralized activity, enabling participants to self-select tasks and scale involvement organically. Built on input requirements, output results, and sandbox testing, it ensures flexibility, independence, and measurable growth without top-down management or sequential timebased flows.
The Core Principles are:
- Modules: Every component is a pure function (self-contained, stateless, reusable), requiring inputs (eg participants, resources), and producing predictable outputs (eg actions, materials, hubs).
- Sandboxing: All new outputs are tested in small, local batches before scaling. Feedback loops are built into every module.
- Mechanism: The plan is a collection of independent modules, each operating autonomously, triggered by input requirements.
- No Timelines: Progress is driven by completion of inputs, not calendars thus facilitating participant involvement.
- No Top-Down Assignments: Tasks are self-selected from the Open Task Pool. The core team acts as an Infrastructure Review Board, not a management hierarchy.
GUPPI Framework Overview #
The GUPPI Framework is organized into four modules that can run in parallel whenever resources and triggers allow:
- Persona Routing (Self-selection via desired ability level)
- Core Assets (Foundational materials and tools)
- Autonomous Hub Activation (Local and specialized network growth)
- Macro Policy Pressure (Systemic advocacy and global alignment)
Each module requires input, then produces output which must pass 66% success rate in local sandbox testing.
Module 1: Persona Routing #
Self-selection mechanism which enables plug-and-play onboarding without top-down management. Individuals can choose a persona based on 3 levels:
- Comfort - do what you already find easy
- Flex - exercise your existing skill muscles
- Enhance - develop new abilities for yourself
| Persona | Profile | Assignment |
|---|---|---|
| Messenger | Social media native, leafleter, casual talker | Distribute standardized packages; run campaigns using pre-approved PNARS assets (online or in person). |
| Networker | Socially confident, well-connected | Act as a Hub Catalyst mapping existing groups (science, ethics, environment) for PNARS to approach. |
| Organizer | Methodical, task-oriented | Coordinate local petition drives, manage distribution lists, or set up information tables. |
| Investigator | Analytical, academic, tech-leaning | Investigate and document local bioeducation/research practices; identify sympathetic faculty. |
| Advocate | Persuasive, public-speaking inclined | Engage with MPs, school boards, or university departments using PNARS talking points and reports. |
| Creator | Creative, content-focused | Develop infographics, video/audio, or written content (eg, NAM success stories, comparisons). |
Component for this module are shown below.
Choosing a Role #
Input: Choice of level(s) and Persona from above, any applicable Core Assets (eg Talking Points, Action Packs from Module #2).
Output: Persona receives the corresponding assets and activates.
Sandbox: Deploy with 6+ volunteers and verify process functions autonomously without intervention.
Module 2: Core Assets #
Foundational materials that may be used by all other modules. These must be completed and tested in local sandboxes before scaling. All Core Assets are developed based on usage needs such as talking points for speakers, paper petitions for advocates, and action packs for network developers.
Components for this module are shown below.
Talking Points #
These are 1 page pdf bulletins to be printed. The front provides the talking point, while the back has FAQ relating to the topic. The pdf provides both QR code and url links to a duplicate webpage which contains references. The page can be discussed, then handed out.
TP1 NAM vs Animal Testing #
Input: Comparative research (NAM vs. animal testing: scientific, ethical, efficiency).
Output: One page, undeniable summary for all audiences (youth, scientists, policymakers, educators).
Sandbox: Print 100 copies, distribute to a local youth group or university club. Collect feedback on clarity and persuasiveness.
Action Packs TBD #
Input: Persona Matrix Choice.
Output: “Six Steps” for each Persona to follow.
Sandbox:: Provide 6 volunteers from different personas. Refine based on their ability to execute steps without additional guidance.
Local Audit Guide TBD #
Input: Institutional policies on animal use (eg dissection requirements, research practices).
Output: Questionnaire for students/academics to assess local policies.
Sandbox:: Pilot with 2–3 local schools or university departments. Verify ease of use and usefulness of collected data.
General Handout Package TBD #
Input: Existing materials (eg the CYC meeting handouts).
Output: Standardized digital PDF package for global use, with space for local customization.
Sandbox:: Print and distribute to 1–2 local groups. Measure response rate and feedback.
Petition Templates TBD #
Input: Legal and ethical considerations for NAM advocacy.
Output: Audience-specific petitions (students, scientists, policymakers).
Sandbox: Launch a local petition with a small group (eg 100 signatures). Verify language and ease of distribution.
Hub Activation Kit #
Input: Networker persona and action pack.
Output: Formation of appropriate hub(s) with access to other assets.
Sandbox: Test that hub functions autonomously.
Module 3: Autonomous Hub Activation #
Local and specialized networks that operate independently, scaling organically.
The system is dependent on the Unit Hub Activation component (shown below) and enables PNARS to expand through self-sustaining, locally managed hubs. Each hub operates independently but remains connected to PNARS Central sharing resources and support. Hubs may self-replicate as well. Each hub should have a webpage on PNARS listing description and activities.
Hub possibilities span a wide range of focused areas such as
- Scientific: universities, labs, research institutions.
- Educational: schools, teacher networks, curriculum developers.
- Political: riding associations, policy advocates, legislative advisors.
- Artisan: writers, social media creators, artists, musicians
- Institution: library, municipality, industry
Here is an example structure showing multilevel development due to self-replication. Though the subhub develops inspired by the original hub, it is nevertheless an autonomous entity.
PNARS CENTRAL (Infrastructure Review Board)
-
Youth Hub: Vancouver High School NAM Club
- Subhub: Neighborhood Elementary School NAM Club (K-7 outreach)
- Subhub: University of BC NAM Society (student-led advocacy)
- Subhub: Surrey Youth Science Network (regional expansion)
-
Educational Hub: BC Teachers’ Crossboard Network
- Subhub: Provincial Curriculum Development Team (NAM lesson plans)
- Subhub: School District Science Coordinators (teacher training)
- Subhub: Home Education Co-op (parent resources)
-
Scientific Hub: UBC Lab Research Group
- Subhub: SFU Graduate Student NAM Initiative (peer mentoring)
- Subhub: Local Biotech Company NAM Task Force (industry collaboration)
- Subhub: Vancouver Island Research Consortium (regional labs)
-
Political Hub: Vancouver-Quilchena Riding Association
- Subhub: Cross-Party NAM Caucus (MP engagement)
- Subhub: Municipal Green Initiative (local policy)
- Subhub: Provincial Youth Advisory Council (youth representation)
-
Artisan Hub: Creative Collective for NAM
- Subhub: Social Media Campaign Team (digital outreach)
- Subhub: Documentary Filmmakers Collective (storytelling)
- Subhub: Graphic Designers for NAM (branding and materials)
Components for this module are shown below.
Unit Hub Activation #
Input: A Networker persona identifies a local group (eg youth club, university lab, riding association).
Output: New hub is formed, with access to Core Assets and Persona Routing.
Sandbox: Verify the hub can operate autonomously and share resources, insights, and other supports.
Cross-Pollination Mechanisms #
Input: Multiple active (sub)hubs.
Output: Shared resources, joint campaigns, and feedback loops between hubs.
Sandbox: Requires at least 2 active hubs before formalizing cross-pollination.
Module 4: Macro Policy Pressure #
Systemic advocacy and global alignment to drive large-scale change.
Macro Policy Pressure enables PNARS to influence policy, education, and research at institutional and governmental levels. By leveraging data from autonomous hubs and comparative research, PNARS and the hubs can advocate for NAM adoption across Canada and align with global movements. Each initiative should have measurable outcomes and be documented for broader dissemination.
Components for this module are shown below.
Comparative Report TBD #
Input: Research on “What worked in other countries that didn’t happen in Canada.”
Output: Public briefing document highlighting Canada’s lag vs. others in NAM adoption.
Sandbox: Share with 2–3 policymakers or academic institutions. Refine based on feedback.
Lobbying Toolkit TBD #
Input: Comparative Report, Talking Points Bulletin.
Output: Training materials for engaging MPs, school boards, and funding bodies.
Sandbox: Test with 1–2 local policymakers or institutions.
Global Alignment TBD #
Input: Active hubs, Comparative Report.
Output: Join international networks (eg Youth for Animals, World Congress on Alternatives). Attend global conferences to present PNARS’s work.
Sandbox: Present at 1 local or virtual conference before scaling.
Thought Leadership TBD #
Input: Data from Autonomous Hubs, Comparative Report.
Output: White papers, annual summits, and interactive tools (eg online courses, webinars).
Sandbox: Publish 1 white paper or host 1 virtual summit.
Open Task Pool (OTP) #
The OTP is a public list of tasks posted on pnars.org (eg in the Nexus section). Anyone can:
- Pick a task and work on it without permission, but with consultation if desired.
- Report success to PNARS by identifying yourself and providing a brief description of what was achieved (e.g., “The Talking Points Bulletin passed sandbox testing with 66%+ approval - Lana, May 28”).
- See updates as completed tasks are noted on the website.
There is no tracking, assignments, or bureaucracy. The only interaction is:
- Task List: Public and always visible.
- Success Reporting: This worked - here’s the feedback, who did it, and what was achieved.
- PNARS Recognition: Successful tasks are highlighted in Nexus and can be used by everyone if suitable (eg a design).
The system has
- Autonomy: People act independently.
- Feedback: The 66%+ metric is only for visibility - not a gate.
- Low Friction: No overhead, no forums, no surveys. Just a list + success updates.
- Recognition: Contributors are acknowledged for their work.
Example Flow:
- A Creator sees: “Design social media templates” in the OTP.
- They design the templates, test them locally, and report: “Templates passed sandbox testing with 70% approval - John, June 1.”
- PNARS adds this to Nexus: “Completed: Social Media Templates (70% success) - John, June 1.”
Infrastructure Review Board #
The core team acts as a coordination hub for:
- Maintaining the Open Task Pool and GUPPI documents.
- Updating the Nexus with successful task completions (including contributor names and descriptions of achievements).
- Ensuring the 66%+ feedback metric is used consistently for visibility, not as a gate.
- Offering consultation for anyone who requests it.
Operations:
- No top-down assignments: Volunteers and hubs self-select tasks from the Open Task Pool.
- No micromanagement: The board only intervenes to document feedback, resolve ambiguities in task descriptions, and provide consultation when required.
Conclusion #
The GUPPI Framework is a modular, autonomous, self-replicating system for scaling NAM advocacy. Volunteers and hubs independently identify opportunities, contribute based on interests and skills, and scale without top-down direction or rigid dependencies.
It operates on three principles:
- Modular Independence: Four self-contained units (Core Assets, Persona Routing, Autonomous Hub Activation, Macro Policy Pressure) run in parallel, each with its own Input → Output → Sandbox workflow.
- Open Task Pool: A public, self-service list of tasks enables decentralized contribution without hierarchy or assignments.
- Feedback-Driven: The 66%+ metric is a visibility tool for Nexus, not a gate, thus ensuring transparency and continuous improvement.
The Infrastructure Review Board maintains the framework’s integrity by documenting successes and clarifying tasks, while the Nexus showcases achievements. Together, these elements create a scalable, adaptive, and low-friction system.