meta4 min read (774 words)

LongHouse Civic Intake And Map Schema

Updated: 2026-04-16

This is the minimum viable operating schema for LongHouse Civic Systems Intake + Map.

The point is not to publish a polished civic platform yet. The point is to capture real civic projects, institutions, stakeholders, and next moves in one workable system so LongHouse can operate like a lane instead of a library-only concept.

Operating model

Use three linked layers:

1. Civic Intake

The first capture surface for a project, issue, or opportunity.

2. Stakeholder Map

The people, institutions, and groups connected to that issue.

3. Project Map

The working record of the civic effort itself, including status and next move.

If this eventually becomes Airtable, keep these as separate tables linked by record ID. If it starts in markdown or JSON, preserve the same field names so migration stays clean.

1. Civic Intake

One row per inbound opportunity, question, issue, or founder-originated civic lead.

Required fields:

• intake_id

Stable ID like LH-INTAKE-2026-04-001

• created_at

ISO timestamp

• source

One of: self-initiated, referral, conversation, event, website, email, other

• title

Short human-readable label

• summary

One paragraph max

• civic_domain

One of: education, constitutional, municipal, state-policy, community-systems, media, land-use, other

• geography

City, county, state, or multistate

• institution_type

One of: public-agency, school, nonprofit, business, community-group, informal-network, mixed, unknown

• problem_type

One of: coordination, governance, information-access, public-trust, systems-design, research, relationship-building, other

• current_stage

One of: intake, triage, mapping, active, paused, archived

• priority_level

One of: P0, P1, P2, P3

• owner

Default Brady

• next_move

One concrete action

• next_touch_date

ISO date

• evidence_notes

Links, quotes, context, and source notes

Optional fields:

• linked_project_id
• linked_stakeholder_ids
• strategic_value

One of: high, medium, low, unknown

• time_horizon

One of: immediate, quarter, year, multi-year

2. Stakeholder Map

One row per person, institution, office, coalition, or relevant node.

Required fields:

• stakeholder_id

Stable ID like LH-STKH-2026-04-001

• name
• entity_type

One of: person, institution, office, coalition, media, community-node, other

• role

Their practical role in the issue

• relationship_status

One of: unknown, aware, warm, active, stalled, sensitive

• influence_level

One of: high, medium, low, unknown

• alignment

One of: aligned, mixed, unclear, opposed

• geography
• next_touch

One concrete follow-up

• last_touch

ISO date

Optional fields:

• institution
• contact_path

Email, intro path, meeting context, or no-contact note

• linked_project_ids
• notes

3. Project Map

One row per active civic project or long-term systems effort.

Required fields:

• project_id

Stable ID like LH-PROJ-2026-04-001

• name
• project_type

One of: civic-library, policy-research, institutional-relationship, community-infrastructure, education, advocacy-support, other

• status

One of: idea, mapping, active, paused, archived

• strategic_role

One of: entry, research, relationship, systems-design, support

• geography
• primary_issue
• linked_intake_ids
• linked_stakeholder_ids
• current_hypothesis

What LongHouse believes is worth doing here

• next_move
• review_date
• scope_cap

Optional fields:

• institutional_window

Why now

• constraints
• proof_assets

Docs, sources, or case briefs that support the effort

• notes

Triage rules

Use these before anything becomes active:

1. Is there a real issue, institution, or relationship to map?
2. Is the next move concrete?
3. Is this LongHouse work rather than generic politics consumption?
4. Can it fit within the current scope cap?

If any answer is no, keep it in intake or mapping, not active.

First practical implementation

For the first pass, LongHouse only needs:

• one Civic Intake template
• one Stakeholder Map template
• one Project Map template
• one weekly review question:

What is the next real civic move, and who does it involve?

Example starter records

Civic Intake example

{
  "intake_id": "LH-INTAKE-2026-04-001",
  "source": "self-initiated",
  "title": "Arizona constitutional literacy lane",
  "summary": "Turn the civic library into a practical intake path for Arizona-focused constitutional and institutional questions.",
  "civic_domain": "constitutional",
  "geography": "Arizona",
  "institution_type": "mixed",
  "problem_type": "information-access",
  "current_stage": "mapping",
  "priority_level": "P1",
  "owner": "Brady",
  "next_move": "Define the stakeholder map and first project categories for LongHouse civic work.",
  "next_touch_date": "2026-04-23"
}

Stakeholder example

{
  "stakeholder_id": "LH-STKH-2026-04-001",
  "name": "Arizona civic education operators",
  "entity_type": "community-node",
  "role": "Potential collaborators, validators, and distribution nodes for civic primers.",
  "relationship_status": "unknown",
  "influence_level": "medium",
  "alignment": "unclear",
  "geography": "Arizona",
  "next_touch": "List the first five concrete institutions or people worth mapping.",
  "last_touch": "2026-04-16"
}

Project example

{
  "project_id": "LH-PROJ-2026-04-001",
  "name": "LongHouse Civic Systems Intake + Map",
  "project_type": "civic-library",
  "status": "active",
  "strategic_role": "entry",
  "geography": "Arizona",
  "primary_issue": "No operating intake or map exists yet for civic work.",
  "linked_intake_ids": ["LH-INTAKE-2026-04-001"],
  "linked_stakeholder_ids": ["LH-STKH-2026-04-001"],
  "current_hypothesis": "LongHouse should begin with an intake-and-mapping layer that connects civic library content to real people, institutions, and projects.",
  "next_move": "Stand up the first intake, stakeholder, and project templates.",
  "review_date": "2026-04-23",
  "scope_cap": "Intake, map, and tracking only."
}