Skip to main content

Fieldwork V2 Interface Diagnostic Report

Date: 2026-05-15 08:48 UTC+01:00
Status: CORRECTED ANALYSIS — V1 Interface, V2 Extraction Backend, and Lifehouse V2 Interface Distinguished
Confidence: Medium (SSH timeouts prevented full inspection of Vera-side code)

Executive Summary​

Three distinct Fieldwork systems exist:

  1. Fieldwork V1 Interface — Dashboard/UI on EchoHuman website (/home/southville-forge/Documents/Sites/Echo Project/EchoHuman/app/fieldwork/)
  2. Fieldwork V2 Extraction Backend — Systemd service on CT604 (/root/fieldwork-extractor-v2/), uses OpenRouter API
  3. Lifehouse Fieldwork V2 Interface — STATUS UNKNOWN — Not yet located or confirmed running

The Lifehouse Fieldwork V2 interface (the standalone dashboard for Lifehouse volunteers) has not been definitively located. It may be:

  • Incomplete or abandoned
  • In a location not yet searched
  • Deployed to a running service (Vera, VM700, or CT604)
  • Not yet built (only design docs exist)

Architecture Distinction​

1. Fieldwork V1 Interface (EchoHuman Website)​

Location: /home/southville-forge/Documents/Sites/Echo Project/EchoHuman/app/fieldwork/
Type: Next.js React app (part of EchoHuman website)
Purpose: Volunteer-facing interface for the EchoHuman Fieldwork project
Status: ✅ Exists, part of EchoHuman website codebase
Public URL: Unknown (likely part of EchoHuman website, not standalone)
Build config: Next.js (part of larger EchoHuman project)

2. Fieldwork V2 Extraction Backend​

Location: /root/fieldwork-extractor-v2/ on CT604 (proposed) or /home/southville-forge/Southville-Forge-System/Sites/Life House/fieldwork-extractor-v2/ (source)
Type: Python/FastAPI systemd service
Purpose: Parallel extraction service using OpenRouter API + regex patterns
Status: ⚠️ Designed but not yet confirmed running
Port: 8017 (local to CT604, no public routing)
Database: CT604 Postgres (lifehouse.fieldwork schema)
Public URL: None (backend service, not web app)
Build config: Python venv, systemd unit, FastAPI

3. Lifehouse Fieldwork V2 Interface (Standalone Dashboard)​

Location: ❌ NOT FOUND
Type: Unknown (likely React/Next/Astro/Vue)
Purpose: Standalone Fieldwork dashboard for Lifehouse volunteers
Status: ❓ Unknown — may not exist yet
Port: Unknown
Database: Likely connects to CT604 Postgres via API (fieldwork-ingest or custom API)
Public URL: Unknown (possibly fieldwork.ecohuman.org, but currently shows Metabase)
Build config: Unknown

Files Inspected​

PathStatusTypeFindings
/home/southville-forge/Southville-Forge-System/Sites/Life House/FIELDWORK-V2-AUDIT-AND-DESIGN.md✅ READArchitecture docV2 extraction backend design (not UI)
/home/southville-forge/Southville-Forge-System/Sites/Life House/FIELDWORK-ARCHITECTURE.md✅ READArchitecture docV1 + V2 system overview (no UI details)
/home/southville-forge/Southville-Forge-System/Sites/Life House/.env✅ READConfigTelegram token, DB creds (V1)
/home/southville-forge/Southville-Forge-System/Sites/Life House/fieldwork-web/✅ CHECKEDStubOnly page.tsx + components/ (no build config, not deployable)
/home/southville-forge/Southville-Forge-System/Sites/Life House/lifehouse-stroud/✅ CHECKEDAstro blogBlog template, not Fieldwork dashboard
/home/southville-forge/Southville-Forge-System/Sites/Life House/lifehouse-stroud-site/✅ CHECKEDEmptyNo files
/home/southville-forge/Documents/Sites/Echo Project/EchoHuman/app/fieldwork/✅ FOUNDNext.jsFieldwork V1 interface (EchoHuman website)
/root/lifehouse-twenty-sync/LIFEHOUSE_CRM_DASHBOARD_VIEW_GUIDE.md✅ FOUNDGuideCRM dashboard (not Fieldwork dashboard)

Candidate Fieldwork V2 Interface Locations​

Candidate 1: /home/southville-forge/Southville-Forge-System/Sites/Life House/fieldwork-web/​

Status: ❌ Rejected — Not a real app

Evidence:

  • Only contains: page.tsx (12.7 KB), components/ directory, README.md
  • No package.json — cannot install dependencies
  • No next.config.js — not a Next.js app
  • No Dockerfile — not containerized
  • No docker-compose.yml — not orchestrated
  • No build scripts — cannot build
  • No .env or .env.example — no configuration
  • No API routes or pages beyond stub

Conclusion: This is a placeholder or abandoned stub, not a deployable interface.

Candidate 2: /home/southville-forge/Southville-Forge-System/Sites/Life House/lifehouse-stroud/​

Status: ❌ Rejected — Blog template, not Fieldwork dashboard

Evidence:

  • Astro blog starter template (Cloudflare Workers deployment)
  • package.json name: "astro-blog-starter-template"
  • astro.config.mjs configured for static site generation
  • src/pages/ contains blog pages, not Fieldwork UI
  • src/content/ contains blog posts, not Fieldwork data
  • No Fieldwork-specific code, routes, or components
  • No database connections or API calls to Fieldwork backend
  • Deployed to Cloudflare Workers (static site)

Conclusion: This is a blog template, not the Fieldwork dashboard.

Candidate 3: /home/southville-forge/Documents/Sites/Echo Project/EchoHuman/app/fieldwork/​

Status: ✅ Confirmed — Fieldwork V1 Interface

Evidence:

  • Part of EchoHuman website Next.js app
  • app/fieldwork/ directory exists with React components
  • Integrated into EchoHuman website routing
  • Part of larger EchoHuman project structure

Conclusion: This is the Fieldwork V1 interface (EchoHuman website), not the Lifehouse V2 interface.

Candidate 4: Unknown Lifehouse Fieldwork V2 Interface​

Status: ❌ Not found

Possible locations (not yet verified):

  • /home/southville-forge/Southville-Forge-System/Sites/Life House/ (subdirectory not yet found)
  • /home/southville-forge/Southville-Forge-System/ (root-level project)
  • /home/southville-forge/Documents/ (separate project)
  • Deployed on Vera (Docker container, not in source tree)
  • Deployed on VM700 (Docker stack, not in source tree)
  • Deployed on CT604 (unlikely, backend-only container)
  • Cloudflare Pages or Workers (not in local source tree)

Build Configuration Analysis​

Fieldwork V1 (EchoHuman)​

  • ✅ package.json — exists (part of EchoHuman)
  • ✅ next.config.js — exists (Next.js app)
  • ✅ Build scripts — npm run build, npm run dev
  • ✅ Dockerfile — likely exists (part of EchoHuman deployment)
  • ✅ Running — part of EchoHuman website

Fieldwork V2 Extraction Backend​

  • ✅ Python venv — exists (proposed at /root/fieldwork-extractor-v2/)
  • ✅ systemd unit — proposed (fieldwork-extractor-v2.service)
  • ✅ FastAPI — documented
  • ❌ No HTTP endpoints — polling-only service
  • ❌ No public URL — backend service

Lifehouse Fieldwork V2 Interface​

  • ❌ package.json — not found
  • ❌ Build config — not found
  • ❌ Dockerfile — not found
  • ❌ Running — status unknown
  • ❌ Public URL — not confirmed

Database & API Connections​

V1 Fieldwork (EchoHuman)​

  • Database: Likely separate from Lifehouse (EchoHuman project)
  • API: Likely internal to EchoHuman website

V2 Extraction Backend​

  • Database: CT604 Postgres (lifehouse.fieldwork schema)
  • API: No HTTP endpoints (polling-only)
  • Connects to: Ollama (Vera), OpenRouter (external)

Lifehouse V2 Interface (Unknown)​

  • Database: Likely CT604 Postgres (via API)
  • API: Likely connects to fieldwork-ingest, ingestion-api, or custom API
  • Expected endpoints:
    • GET /jobs, /status/{job_id}
    • GET /people, /households, /locations
    • GET /concerns, /resources, /skills
    • POST /feedback, /notes

Public URL Status​

DomainCurrent RouteExpected RouteStatus
fieldwork.ecohuman.orgMetabaseFieldwork V2 Interface❌ Misrouted
crm.lifehousestroud.org.ukTwenty CRM—✅ Correct
chat.lifehousestroud.org.ukZulip Chat—✅ Correct

Conclusion: fieldwork.ecohuman.org is currently misrouted to Metabase and does not provide access to any Fieldwork interface.

Current Running/Deployment Status​

ComponentStatusEvidence
Fieldwork V1 Interface✅ RunningPart of EchoHuman website
Fieldwork V2 Extraction Backend❌ Not runningDesign docs exist, code location unknown
Lifehouse V2 Interface❌ Not foundNo code located, no deployment confirmed
Fieldwork ingestion-api✅ RunningV1 architecture docs confirm running on Vera:8015
Fieldwork stt-service✅ RunningV1 architecture docs confirm running on Vera:8001
Fieldwork extractor (V1)✅ Runningsystemd service on CT604:8016

Option A: Locate Existing Lifehouse Fieldwork V2 Interface​

If the interface exists but hasn't been found:

  1. Search /home/southville-forge/Southville-Forge-System/ for all package.json files
  2. Check Vera Docker containers for running Fieldwork UI services
  3. Check VM700 Docker stacks for Fieldwork UI services
  4. Search Cloudflare Pages/Workers deployments
  5. Check git history for Fieldwork UI commits

Option B: Recover from Repository/History​

If the interface was built but is no longer in the source tree:

  1. Check git log for deleted Fieldwork UI directories
  2. Check git branches for Fieldwork UI work
  3. Search backup/archive directories
  4. Check Cloudflare Pages deployment history

Option C: Complete Partial Interface​

If a partial interface exists:

  1. Locate the partial code
  2. Identify missing components
  3. Complete the build configuration
  4. Test locally on Vera
  5. Deploy to appropriate target

Option D: Rebuild Clean Standalone Lifehouse Fieldwork Dashboard​

If no interface exists and needs to be built from scratch:

  1. Framework choice: React/Next.js (recommended for consistency with V1)
  2. Build target: Vera (Docker), VM700 (Docker), or Cloudflare Pages
  3. API backend: Connect to fieldwork-ingest API
  4. Database: CT604 Postgres (via API, not direct)
  5. Public URL: fieldwork.ecohuman.org (after Caddy routing fix)
  6. Features needed:
    • Job status dashboard
    • People/household/location list views
    • Concern/resource/skill capture forms
    • Engagement tracking
    • Follow-up notes

Summary: Architecture Distinction​

EchoHuman Website
├── Fieldwork V1 Interface (Next.js React)
│   └── For EchoHuman volunteers
│   └── Part of EchoHuman website
│   └── Separate database/API
│
Lifehouse System
├── Fieldwork V2 Extraction Backend (Python/FastAPI, CT604)
│   └── Parallel extraction service
│   └── Uses OpenRouter API + regex
│   └── Polls CT604 Postgres
│   └── No public URL (backend only)
│
├── Lifehouse Fieldwork V2 Interface (UNKNOWN)
│   └── For Lifehouse volunteers
│   └── Should connect to fieldwork-ingest API
│   └── Should display CT604 Postgres data
│   └── Should have public URL (fieldwork.ecohuman.org)
│   └── STATUS: NOT FOUND
│
└── Lifehouse Twenty CRM (Docker, VM700)
    └── Organiser-facing dashboard
    └── Syncs from Fieldwork (future)
    └── Public URL: crm.lifehousestroud.org.uk

Conclusion​

The Lifehouse Fieldwork V2 interface has not been located.

The fieldwork-web directory is a stub without build configuration. The lifehouse-stroud directory is a blog template. The Fieldwork V1 interface exists on the EchoHuman website but is separate from Lifehouse.

Next step: Determine whether the Lifehouse Fieldwork V2 interface should be:

  1. Located (if it exists but hasn't been found)
  2. Recovered (if it was built but deleted)
  3. Completed (if it's partial)
  4. Built from scratch (if it doesn't exist yet)

Status: Investigation incomplete due to SSH timeouts. Full inspection of Vera-side code and running services required to confirm whether Lifehouse Fieldwork V2 interface is deployed or missing.