Design Layer / Framework

Common Coordination Gaps Across Civic Systems

Recurring coordination gap types that appear across ecosystems, institutions, and initiatives in Systems Atlas.

Overview

Design Layer prototypes are not random. They consistently emerge from a small set of repeatable coordination gaps visible across civic systems.

These gap types explain why coordination breaks down and why similar coordination structures appear across different domains.

Primary coordination gap types

Visibility gaps

Institutions cannot see related actors, initiatives, data, or opportunities across systems.

Participation barriers

Entry into programs, roles, or decision environments is unclear or unevenly accessible.

Responsibility ambiguity

Coordination roles are unclear, duplicated, or missing across institutions.

Infrastructure absence

Required coordination structures do not exist, even though the actors do.

Data fragmentation

Data systems, definitions, or classifications are incompatible across institutions.

Duplicate effort

Institutions independently perform similar work without alignment.

Funding misalignment

Funding timing, requirements, or structures do not align with implementation needs.

How these gaps generate prototypes

Each Design Layer category corresponds to one or more coordination gap types.

  • Information Coordination → visibility gaps
  • Participation Pathways → participation barriers
  • Procurement Alignment → funding misalignment and duplicate effort
  • Standards Layers → data fragmentation
  • Hub Models → infrastructure absence and responsibility ambiguity
  • AI Coordination → emerging combinations of all gap types

Why this matters

Recognizing coordination gap patterns allows Systems Atlas to move from describing systems to identifying repeatable coordination structures that can improve them.

The Design Layer is therefore not a collection of ideas, but a structured response to recurring coordination failures across civic environments.