Domain Councils

Part of Institutional Design

Specialized governance bodies with authority over specific functional areas of community life.

Why This Matters

General-purpose governance bodies — a community council, an assembly — cannot develop deep expertise in every domain they must govern. The same body cannot be experts in agricultural planning, medical standards, construction engineering, and dispute resolution simultaneously. And yet all of these domains require both technical knowledge and legitimate governance authority.

Domain councils solve this problem by delegating specific governance authority to bodies that combine relevant expertise with community accountability. A domain council for food production includes experienced farmers and is accountable to the community for food security outcomes. A domain council for medical standards includes experienced healers and is accountable for health outcomes. Each council has genuine authority within its domain — it is not merely advisory — while remaining subordinate to the community’s overall governance framework.

This structure produces better decisions in complex technical domains, builds specialist investment in community governance, and prevents generalist councils from making uninformed decisions in areas they do not understand.

Defining Domain Boundaries

The first design challenge is deciding which domains warrant their own council. Criteria:

Technical complexity: The domain requires specialized knowledge that a general council is unlikely to possess. Medical care, structural engineering, and agricultural planning all qualify. Basic maintenance tasks probably do not.

Ongoing governance burden: The domain generates a continuous stream of governance decisions, not just occasional ones. Food production policy requires constant attention to season, weather, inventory, and labor allocation.

High stakes: Errors in the domain have significant consequences for community welfare. Structural failures, disease outbreaks, food security failures are all high-stakes.

Clear scope: The domain has reasonably well-defined boundaries. “Infrastructure” is a workable domain. “Things that matter” is not.

Common domains for post-collapse communities:

• Food and agriculture
• Health and medicine
• Construction and infrastructure
• Water and sanitation
• Resource and inventory management
• Education and knowledge
• External relations and trade

Composition Design

Expert core: Every domain council must include people with genuine expertise in the domain. The food council that contains no experienced farmers is not fit for purpose. Define minimum expertise requirements: number of years of practice, demonstrated competency, and active involvement in the domain.

Generalist representation: Expert councils without community representation can become self-serving — optimizing for practitioner interests rather than community interests. Include community representatives without domain expertise on each council. These members represent the interests of those served by the domain, ask basic questions that experts overlook, and provide democratic accountability.

Users and affected parties: Where relevant, include representatives of those most directly affected by domain decisions. The community members who depend on medical care for chronic illness have interests in health governance that differ from those of the medical practitioners. The farmers who work under agricultural policy have interests that differ from agricultural administrators.

Size: Domain councils work best with 5-11 members. Smaller than five loses diversity of perspective; larger than eleven becomes unwieldy for technical deliberation.

Authority and Limits

Domain council authority should be explicit, complete for its domain, and bounded at its edges.

What domain councils may do:

• Set standards and protocols within their domain
• Allocate resources assigned to their domain
• Hire and evaluate practitioners
• Make day-to-day operational decisions
• Bring recommendations for larger resource allocation to the general council

What domain councils may not do without general council approval:

• Make major resource allocation decisions that affect the overall community budget
• Establish rules that affect community members outside the domain
• Engage in external relationships or binding commitments on behalf of the community
• Take actions that affect other domains without coordination

Conflict resolution between domains: When two domain councils have conflicting interests or overlapping jurisdiction, a defined mechanism resolves the conflict. This might be escalation to the general council, a joint session of both councils, or a designated inter-domain coordination role.

Accountability Mechanisms

Domain councils must answer to the community, not only to their expert members.

Regular reporting: Each domain council reports to the general council and/or community assembly at regular intervals — monthly for active domains, quarterly for less active ones. Reports should include: what decisions were made, what outcomes resulted, what challenges exist, and what resources are needed.

Performance metrics: Define in advance what success looks like for each domain. For food production: caloric reserves per capita, crop failure rate, agricultural labor productivity. For health: outbreak response time, mortality from preventable causes, access to care metrics. Councils are evaluated against these metrics, not just against their own judgment of how well they are doing.

Community oversight: Community members should have a clear pathway to raise concerns about domain council decisions. This might be a petition process, a regular open session where community members can address the council, or the ability to appeal domain council decisions to the general council.

Term limits and renewal: Domain council membership should turn over regularly. Expert members serve defined terms; renewal requires positive reappointment rather than being assumed. This prevents domain councils from becoming self-perpetuating guilds.