Skip to main content

Research Project Commissioning Packs

projects owns the cross-repository recipe, static assembly, routing guidance and pack contract. Participating repositories remain authoritative for their source semantics, runtime commands, data, tests and research judgments.

The producer is deliberately read-only:

declared evidence files from authoritative repositories
    ↓
private local commissioning assembler
    ↓
evidence-linked handoff pack

It never executes, installs, imports or mutates a participating repository. An operator explicitly supplies each local checkout root; generated packs are ignored because they may combine private/local evidence.

FCV prototype​

The tracked recipes currently cover FCV, Accounting and Poverty. Each produces eight handoff pages plus manifest.json.

For FCV:

python3 scripts/project_commissioning.py build \
  --spec estate/commissioning/fcv.json \
  --repo-root repo.fcv-empirical-data=/path/to/fcv-empirical-data \
  --repo-root repo.fcv-experiment-harness=/path/to/fcv-experiment-harness \
  --repo-root repo.fcv-spatial-data-research-onboarding=/path/to/fcv-spatial-data-research-onboarding \
  --out artifacts/project-commissioning/fcv

The manifest records source repository IDs, relative source paths and SHA-256 values—not local absolute paths. Rebuilding against unchanged evidence yields byte-identical substantive pages and manifest.

For the other exercised projects:

make commissioning-accounting ACCOUNTING_ROOT=/path/to/accounting-workflows
make commissioning-poverty POVERTY_ROOT=/path/to/indice-pobreza-UBA

Agent route​

An agent resuming a project starts with the pack and follows estate/templates/research-project-commissioning-agent.md. The pack is a navigation and evidence surface, never a substitute for repository-local authority.

Adding another project​

Add one small JSON spec with a stable project ID, declared repositories, and a bounded allowlist of Markdown/JSON/YAML/CSV/TXT evidence files. Do not add raw data, secrets, generated binary outputs, or broad filesystem scanning. The resulting pack should help a competent researcher identify the next bounded verification step—not manufacture a research conclusion.