Skip to the content.

Artifacts

Canonical documentation root

The canonical Harper doc root is docs/harper (fixed; it is not a setting).

Canonical Harper artifacts

Main canonical files:

Written by /finalize:

Project inputs

Read as context by the phases (see context-sources.md), never written by CLike:

Earlier release folders (and unversioned inputs, once release folders exist) are history.

Candidate artifacts under runs/kit/<REQ-ID>/

The current sources treat these paths as the primary candidate area for REQ work.

Source candidates

Test candidates

CI / execution artifacts

Candidate docs

Follow-up promotion / integrity artifacts

Current sources also reference additional artifacts such as:

These are required by some explicit follow-up KIT phases.

Promotion reports

Eval and gate reports

Run-level artifacts under runs/<runId>/

The inspected sources and reference docs consistently point to run-level evidence under:

Common files:

This layout is what the orchestrator MCP run tools (runs_list, runs_read) read; the eval and gate evidence of the extension flow is REQ-scoped under runs/eval/<REQ-ID>/ and runs/gate/<REQ-ID>/ (see above).

Different parts of the codebase reference slightly different subsets, but the important distinction is stable:

plan.json

docs/harper/plan.json is the main machine-readable plan artifact.

Current responsibilities:

PLAN.md

docs/harper/PLAN.md is the human-readable plan snapshot.

Current responsibilities:

LTC.json

LTC.json is the REQ-level execution contract generated under candidate artifacts.

Current responsibilities:

HOWTO.md

HOWTO.md is the operator-facing runbook for a REQ candidate.

Current responsibilities:

AGENT_EXECUTION_CONTEXT.json

This artifact is central to local-agent compatibility.

Current responsibilities:

Current phase-specific behavior

For kit:

For eval:

Promotion artifacts

Promotion is not modeled as raw copy-only behavior. The current code uses promotion-aware manifests and policy checks.

Promotion-related references in sources include:

Artifact rules that must remain explicit in docs

The current sources justify documenting these rules explicitly: