Recovered FCV spatial analysis archive and pipeline

• Day: 2026-04-23
• Time: 10:35 to 10:45
• Project: Dev
• Workspace: WP 2: Operational
• Status: In Progress
• Priority: HIGH
• Assignee: Matías Nehuen Iglesias
• Tags: Project-Recovery, Archive, Spatial-Analysis, Matching, Reproducibility, Documentation

Description

Session Goal

Reconstruct the structure, outputs, and missing dependencies of the 2023_Duke FCV/spatial analysis archive so it can be exported, documented, and potentially resumed.

Key Activities

• Screened multiple strategic project briefs and recovery notes for Obsidian-style archival export, focusing on metadata, decision axes, and bounded next actions.
• Mapped the project as a layered pipeline: standardized geographies (GADM) feeding violence, DHS, Afrobarometer, investment/project data, matching, and downstream empirical analysis.
• Identified 86 - Produce Matching Outputs.ipynb as the likely consolidated entrypoint for final matching outputs and documentation packaging.
• Compared recovered notebooks, outputs, and documentation to infer the original run contract and assess reproducibility.
• Drafted recovery memos for Eric summarizing what was preserved and what remains missing.

Achievements

• Clarified the archive’s conceptual structure and the role of the matching workflow within the broader FCV analysis pipeline.
• Distinguished between preserved analytical outputs and the documentation layer versus the missing or displaced investment preprocessing layer.
• Established that the project is recoverable in principle, but not yet fully executable without restoring the investment/project input layer and validating dataset contracts.
• Produced a concise recovery-oriented narrative suitable for handoff and future archival organization.

Pending Tasks

• Locate or reconstruct the missing investment preprocessing assets and any displaced input notebooks.
• Validate the canonical dataset versions and administrative-level assumptions used across the pipeline.
• Compare surviving outputs against documentation templates to rebuild a reproducible execution path.
• Confirm which files belong in the final delivery folder versus broader project documentation and exploratory data-lab materials.

Evidence

• source_file=2026-04-23.sessions.jsonl, line_number=1, event_count=0, session_id=a75cb6aa73c3cfec2702ab6a5e9634a046d205ee0ad2cec94c7d2596b0f1e10d
• event_ids: []