Task and Role-Based Operating System
Liminal Village operates through a task and role-based system where collaboration, alignment, and action flow through consent-based roles and self-organized tasks rather than hierarchical management.
At Liminal Village, being part of the community means collaborating, aligning, and operating through a decentralized system organized around roles (ongoing accountabilities) and tasks (specific actions). This replaces traditional hierarchies with consent-based, self-organizing coordination.
Overview
Think of Liminal Village as a five-star hotel where the clients are the staff. The community maintains high standards of care, cleanliness, and functionality - but everyone who enjoys these conditions also participates in creating them. There's no separate "service class" doing the work while others consume.
Traditional organizations operate through positional authority - managers tell subordinates what to do, decisions flow top-down, and people are defined by their job titles.
Liminal Village operates through distributed authority - roles carry specific accountabilities consented to by the community, necessary tasks are shared among participants and coordinated through digital tools, and people fluidly move between multiple roles based on capacity and interest.
The work exists and must get done. Kitchens need cleaning, meals need cooking, supplies need ordering, infrastructure needs maintaining, governance needs facilitating. These aren't optional - they're what keeps the "hotel" running at five-star quality. The difference is how this necessary work gets organized: through consent-based roles, transparent coordination, and shared responsibility rather than hierarchical command.
This task and role-based operating system enables:
Clarity - Everyone knows who's accountable for what
Autonomy - People have authority to act within their roles
Shared Responsibility - Necessary work is distributed, not ignored or left to "someone else"
Adaptability - Roles and tasks evolve as needs change
Consent - No one is coerced into roles or tasks they object to
Transparency - All roles and tasks are visible through digital tools and boards
Core Concepts
Roles vs. Tasks
Roles are ongoing accountabilities that persist over time:
A role has a clear purpose (why it exists)
Defined accountabilities (what it's responsible for)
Specific domain (what it has authority over)
Filled by consent through the Role Selection process
Can be held by one or multiple people
Evolve through governance meetings
Tasks are specific, time-bound actions:
Emerge from roles, tensions, or community needs
Self-assigned based on capacity and interest
Completed and checked off
Don't require formal consent (unless significant)
Can be done solo or with Task Buddies
Tracked on "Did this" boards
Example:
Role: "Kitchen Coordinator" - Purpose: "Ensure community has access to nourishing meals." Accountabilities: "Organize meal planning, maintain kitchen supplies, coordinate cooking schedules."
Tasks: "Order 50 lbs of rice," "Clean fridge," "Organize Saturday meal prep with volunteers," "Update kitchen inventory spreadsheet"
The Operating System Flow
How Roles Work
Creating Roles
Roles are created when a recurring need or accountability emerges:
Step 1: Navigate via Tension
Someone senses something isn't working or is needed
"I notice our kitchen is often chaotic and we run out of supplies unexpectedly"
This tension signals a need for a role
Step 2: Propose Role in Governance Meeting
Use Co-Create Proposals pattern
Draft role with: Name, Purpose, Accountabilities, Domain
Example:
Step 3: Consent Decision Making
Community reviews proposal
Raise objections if the role would cause harm
Integrate objections to improve the role
Adopt through consent (no remaining objections)
Filling Roles
Use the Role Selection pattern (see handbook/patterns/cocreation/role-selection.md)
9-Step Consent-Based Process:
Present the role
Clarifying questions
Nominations (anyone can nominate anyone, including themselves)
Nomination round (why you nominated that person)
Change nominations (optional)
Proposal (facilitator proposes based on nominations)
Objection round
Integration (resolve objections)
Celebration
Key Principles:
You can nominate yourself (self-selection is valid!)
You can decline a nomination
Multiple people can share a role
Roles can rotate (e.g., monthly Kitchen Coordinator)
Role holders have authority within their domain
Community can recall/revise roles through governance
Role Authority
Within their domain, role holders have authority to:
Make decisions without asking permission
Take actions aligned with their accountabilities
Spend allocated budget
Organize people and resources
Create tasks and request help
Example:
Kitchen Coordinator doesn't need to ask permission to order rice (within domain)
Kitchen Coordinator CAN'T decide to renovate the entire kitchen (outside domain)
Kitchen Coordinator CAN'T force someone to cook (no coercion)
Kitchen Coordinator CAN post requests for cooking help (offers and requests)
Role Evolution
Roles are updated regularly through governance:
When to Update:
Role accountabilities are unclear or overlapping
Role is too large (split into multiple roles)
Role is no longer needed (sunset it)
New accountabilities need to be added
Role holder requests changes
Process:
Bring tension to governance meeting
Propose role update using Co-Create Proposals
Get consent from community
Update role documentation
How Tasks Work
Task Emergence
Tasks emerge from multiple sources:
From Roles:
Kitchen Coordinator role generates tasks: "Order supplies," "Clean fridge," "Plan Saturday meal"
From Community Needs:
Posted on Offers and Requests board
Surfaced in Open Space gatherings
Identified through Navigate via Tension
From Projects:
Building a root cellar generates: "Excavate hole," "Build walls," "Install shelving," "Waterproof interior"
From Tensions:
"The solar panels need cleaning" → Task: "Clean solar panels"
Task Assignment
Tasks are self-assigned, not assigned by authority:
Self-Selection:
See task on board or hear need in meeting
Assess: Do I have capacity? Skills? Interest?
Claim task: "I'll do this"
Optionally find Task Buddy
Task Buddy System (recommended):
Partner with someone to work together
Mutual validation and support
Share flow tokens if applicable
Learn from each other
Posting Tasks:
Use Offers and Requests board
"Request: Someone to help build raised garden beds this Saturday"
Include: what needs doing, when, what skills/resources needed, contact info
Example Flow:
Task Completion
When task is done:
Attest on "Did this" board
"Cleaned kitchen, organized pantry, created inventory sheet - 3 hours - Alex & Jordan"
Update any relevant tracking
Mark task complete on project board
Update role documentation if needed
Remove from Offers and Requests
Share outcomes
Tell Kitchen Coordinator (if task was role-generated)
Share at full moon gathering if significant
Post in community forum/chat
Receive recognition
Community gratitude
Flow tokens if applicable
Appreciative Scoring from peers
Digital Coordination Tools
The work exists, but no one "assigns" it hierarchically. Instead, necessary tasks are coordinated through digital tools that make needs visible and enable self-organization:
Making Work Visible
Asynchronous Forum (async.hackalong.io)
Community discussions about needs and projects
DiaLOG category for sharing insights and conclusions
Project proposals and collaboration requests
Longer-form coordination across time zones
Collective Knowledge Graph (Roam Research)
Linked documentation of roles, projects, and patterns
Shared knowledge base that evolves over time
Connections between ideas and initiatives
Communication Platforms
Interspace (interspace.chat) - Real-time coordination
Discord (discord.gg/zucJ4ssXtd) - Community chat and voice
Telegram - Quick coordination and updates
Physical & Digital Boards
"Did this" boards (contribution attestation)
"Offers and Requests" boards (resource matching)
Project boards (task tracking and status)
Role documentation (who's accountable for what)
How Coordination Works
1. Necessary Work Becomes Visible
Role holders post tasks that need doing
Community members post requests for support
Recurring needs (meals, cleaning, maintenance) are documented
Digital tools make all of this transparent to everyone
2. People See and Respond
Check boards and forums to see what's needed
Self-select tasks based on capacity, skills, interest
Offer help or resources where they can contribute
Coordinate timing and collaboration
3. Shared Responsibility, Not Central Assignment
No manager saying "You do this, you do that"
Instead: "This needs doing" → visible on tools → someone responds
If critical tasks aren't getting picked up, that creates tension → governance addresses it (adjust roles, redistribute work, offer flow tokens, etc.)
4. The "Five-Star Hotel" Standard
Everyone benefits from clean spaces, good food, functioning systems
Everyone contributes to maintaining those standards
Digital tools coordinate who does what when without requiring bosses
Shared pride in keeping the community functioning well
Example: Kitchen Coordination
Kitchen Coordinator role identifies: "Fridge needs deep clean by Friday"
Posts to Offers and Requests board digitally and physically
Jordan sees it, has time Thursday, self-selects
Jordan finds task buddy (Alex), they complete it together
They attest on "Did this" board
Kitchen Coordinator confirms completion, thanks them
Both receive flow tokens at new moon distribution
The Shift:
Traditional: Boss says "Jordan, clean the fridge by Friday"
Liminal Village: Need is visible → Jordan responds → Work gets done → Contribution recognized
Result: Same clean fridge, different power dynamic
Operating Through the System
What It Means to Be at Liminal Village
Being part of Liminal Village means:
1. Holding Roles (Optional)
You may hold one or more roles based on your capacity and gifts
Roles are consented to, not imposed
You have authority within your role domains
You can release roles when needed
2. Contributing Through Tasks
Necessary tasks exist and are coordinated through digital tools
You see what needs doing and self-select based on capacity and interest
The work must get done, but who does what emerges through coordination rather than command
You can work solo or find buddies
Your contributions are visible and recognized
3. Participating in Governance
Attend governance meetings (often monthly or at new moons)
Raise tensions when you notice something isn't working
Participate in role creation and selection
Give consent (or raise objections) to proposals
4. Navigating via Tension
Notice what's not working, what's needed, what wants to emerge
Bring tensions to governance rather than complaining
Trust that tensions are data showing where evolution is needed
5. Operating with Consent
Don't coerce others to do tasks or hold roles
Respect others' domains and authority
Raise objections if proposals would cause harm
Integrate objections to strengthen proposals
6. Transparency and Attestation
Make your work visible on "Did this" boards
Post offers and requests openly
Share role accountabilities publicly
Trust through verification, not blind faith
Daily Practice
Morning/Weekly Check-in:
What roles am I holding right now?
What are my role accountabilities this week?
What tasks have I claimed or want to claim?
What tensions am I noticing?
During Work:
Am I acting within my role authority?
Do I need to post a request for help?
Should I find a task buddy?
Am I working on what truly matters?
Evening/Weekly Reflection:
What did I complete? (Attest on "Did this")
What tasks remain?
What tensions emerged?
What roles need updating?
Monthly/Lunar Cycle:
New Moon: Governance meeting, role updates, set intentions
Full Moon: Share completions, attest contributions, receive flow tokens
Navigate tensions throughout the cycle
Integration with Other Patterns
Governance Patterns
Open Space - Surface needs that become roles or tasks Consent Decision Making - Approve role creation/updates Navigate via Tension - Identify when roles need evolution Co-Create Proposals - Draft role descriptions collaboratively Resolve Objections - Integrate concerns about roles Role Selection - Fill roles through consent Driver Mapping - Understand what drives need for roles
Operational Patterns
Task Buddy - Partner for task completion Offers and Requests - Surface tasks that need doing Did this - Attest task completion and role fulfillment Flow Tokens - Recognize contributions from roles and tasks Appreciative Scoring - Peer feedback on role performance Lunar Rhythms - Time governance and operations with natural cycles
Communication Patterns
Psychological Safety - Required for honest tension surfacing Imago Dialogue - Resolve role conflicts Sharing Circle - Process experiences in roles MonoLogs/DiaLogs/TriaLogs - Structure role-related conversations
Common Questions
"Who's in charge?"
No one is "in charge" hierarchically. Authority is distributed through roles. If you want to know who's responsible for something, look at role accountabilities. The Kitchen Coordinator has authority over kitchen matters. The Garden Coordinator has authority over garden matters. Each domain has clear accountability.
"What if I don't feel like doing any tasks?"
Remember the "five-star hotel where clients are staff" dynamic. You're benefiting from clean spaces, maintained infrastructure, prepared meals, and coordinated community - all created by others' labor. If you consistently consume without contributing, you're expecting others to serve you, which contradicts the shared responsibility model.
That said:
Short-term: Everyone has times of low capacity (illness, grief, burnout, life transitions). The community supports you during these periods.
Contribution varies: Some contribute physical labor, others offer land/resources, others provide care/facilitation, others financial support. All are valid.
If it persists: If you find you never want to contribute, there may be a mismatch between you and this community model. Liminal Village works because everyone participates in maintaining the conditions we all enjoy.
"What if no one wants to do a task?"
Option 1: The task might not be important. If it's truly urgent, someone will feel the tension and respond.
Option 2: Make the request more appealing - offer to teach the skill, provide resources, work as buddies, or offer flow tokens.
Option 3: Three Pathways - Purchase it (pay someone), Produce it (learn to do it), or Attract it (collective effort with pooled resources).
"What if someone isn't fulfilling their role?"
Step 1: Direct feedback - use Imago Dialogue or direct conversation. "I'm noticing kitchen supplies haven't been ordered - what's happening?"
Step 2: Governance conversation - bring tension to meeting. "I'm sensing Kitchen Coordinator role needs support or restructuring."
Step 3: Role update or re-selection - either add support, reduce accountabilities, or select new role holder through consent process.
"How do I know what to work on?"
Listen to your energy and tensions:
What needs doing that aligns with my gifts?
What posted requests call to me?
What role accountabilities do I hold?
What would I regret NOT doing?
Check the boards:
Offers and Requests - what's needed?
Project boards - what tasks are available?
Role documentation - what are my accountabilities?
Ask:
"What's needed right now?"
"Who needs support?"
"Where's the energy?"
"Can I create a new role?"
Yes! If you notice a recurring need or accountability that no existing role covers:
Sense the tension
Draft a role proposal
Bring to governance meeting
Get consent from community
Run role selection process
Begin operating in the role
"What if I want to leave a role?"
Roles are not forever. You can:
Announce intention to step down (give notice for transition)
Help find/train replacement
Attend governance meeting where new selection happens
Release the role with gratitude and grace
Real-World Example: Building a Root Cellar
Scenario: Community needs food storage
Tension Surfaced: "We're growing lots of food but have nowhere to store it long-term. Produce is spoiling."
Governance Meeting:
Tension raised using Navigate via Tension
Discussion: Is this big enough for a role or just a project?
Decision: It's a project (time-bound), but might generate an ongoing "Food Storage Coordinator" role later
Project Formation (Open Space):
Open Space session: "Who wants to work on root cellar project?"
8 people interested
Self-organize into tasks:
Research designs (Alex)
Site selection (Jordan & Casey)
Excavation (Riley, Sam, Morgan)
Building walls (Alex, Jordan)
Installing shelves (Casey)
Waterproofing (Riley)
Task Execution:
Each person/pair works on their tasks
They use Task Buddy system
Post requests on Offers and Requests: "Need someone with concrete experience"
Someone external responds, teaches concrete skills
Work happens over 3 lunar cycles
Task Attestation:
Each completion goes on "Did this" board
Full moon gatherings: share progress, celebrate milestones
Photos and documentation shared
Flow Token Distribution:
Hours contributed tracked
Flow tokens distributed monthly to contributors
External teacher receives payment + tokens
Role Creation:
Root cellar complete, but needs ongoing maintenance
New tension: "Someone should manage root cellar usage, temperature, rotation"
New role created: "Root Cellar Coordinator"
Role selected through consent
Riley chooses to hold role
Ongoing tasks emerge from role: "Monitor temperature," "Organize harvest storage," "Teach usage to new members"
Transitioning to This System
If you're new to Liminal Village:
Week 1-2: Observer
Attend governance meeting (observer role)
Read role documentation
Notice what tasks are posted
Ask questions, don't commit yet
Week 3-4: Small Tasks
Claim one small task
Work with a Task Buddy
Attest completion on "Did this"
Experience the flow
Month 2: More Engagement
Claim larger tasks aligned with your gifts
Participate in governance (raise tensions, give consent)
Consider which roles interest you
Month 3+: Full Participation
Potentially hold one or more roles
Regular task contribution
Active governance participation
Supporting others to integrate
Why This Works
Decentralized Authority:
No bottlenecks waiting for manager approval
Fast response to emerging needs
Authority distributed to those closest to the work
Intrinsic Motivation:
Self-selection ensures people work on what energizes them
Consent means no coercion
Attestation provides recognition
Clarity Without Control:
Roles make accountability clear
No need for micromanagement
Trust with verification
Evolutionary:
Roles and tasks adapt as needs change
System evolves through tension sensing
No rigid structures that resist change
Regenerative:
Values all forms of contribution (labor, care, wisdom, materials)
Flow tokens recognize what conventional economy ignores
Builds capacity while meeting needs
Related Patterns
Essential patterns for operating this system:
Governance:
Consent Decision Making - How decisions are made
Navigate via Tension - How evolution happens
Co-Create Proposals - How roles are designed
Role Selection - How roles are filled
Driver Mapping - Understanding what drives needs
Operations:
Task Buddy - How tasks are executed
Offers and Requests - How needs become visible
Did this - How contributions are attested
Flow Tokens - How value is recognized
Three Pathways to Abundance - How needs are met
Culture:
Psychological Safety - Foundation for honest participation
Imago Dialogue - Resolving role conflicts
Lunar Rhythms - Timing the cycles
Sharing Circle - Processing experiences together
Being at Liminal Village means embracing this task and role-based operating system - not as rigid rules but as living patterns that enable collaborative, aligned, and effective action. It's a shift from "someone tell me what to do" to "I sense what's needed and respond," from "boss and subordinate" to "roles and accountabilities," from extraction to regeneration.
The system works because it honors human autonomy while creating clear structure, enables rapid adaptation while maintaining coherence, and recognizes all forms of contribution while maintaining focus on real needs. This is how regenerative communities coordinate at scale without coercion - through consent, transparency, and distributed authority flowing through roles and tasks.
Last updated
Was this helpful?