# Harness Memory Promoter

> Promote explicitly approved reusable project or harness knowledge after review, replay, rollback, and release evidence gates.

- Skill: `munlucky/harness-memory-promoter` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add munlucky/harness-memory-promoter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/munlucky/harness-memory-promoter/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: munlucky (https://skillmd.com/u/munlucky)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/munlucky/harness-memory-promoter

---


# Harness Memory Promoter

Use this skill only when the user explicitly asks to promote reusable project knowledge into global or harness memory. Project-local facts are not promoted by default.

## Required Inputs

Promotion must consume durable manifests instead of raw transcript or graph dumps:

- proposal: `improvement/proposals/<proposalId>.yaml`
- independent review: `improvement/reviews/<proposalId>-review.yaml`
- replay evidence: `improvement/replay/<proposalId>-replay.json`
- rollback evidence for harness stable promotion: `improvement/rollback/<proposalId>-rollback.json`
- release manifest for harness stable promotion: `improvement/releases/<proposalId>-release-manifest.json`

Runtime ledger input is mandatory before any long-term memory write:

```bash
node scripts/runtime-state.mjs record-memory-promotion \
  --run-id "{runId}" \
  --goal-id "{goalId}" \
  --memory-id "{memoryId}" \
  --status promoted \
  --evidence-json "{...fresh evidence...}" \
  --reviewer-json "{...approved review...}" \
  --replay-json "{...passed replay...}" \
  --rollback-json "{...rollback plan...}" \
  --scope-owner "{owner}" \
  --json
```

If evidence, review, replay, rollback, or scope owner is missing, record a rejected ledger decision and stop promotion.

For harness self-improvement, the meta-project contract is:

```yaml
projectId: moonshot-relay
knowledgeRoot: "${MOONSHOT_RELAY_HOME:-~/.moonshot-relay}/state/projects/moonshot-relay/knowledge"
improvementRoot: "${MOONSHOT_RELAY_HOME:-~/.moonshot-relay}/state/projects/moonshot-relay/improvement"
candidateReleaseRoot: "${MOONSHOT_RELAY_HOME:-~/.moonshot-relay}/state/harness/releases/candidate"
stableReleaseRoot: "${MOONSHOT_RELAY_HOME:-~/.moonshot-relay}/state/harness/releases/stable"
```

## Required Flow

1. Run from the `moonshot-relay` repository root.
2. Load the proposal and evidence manifests.
3. Validate the proposal with `knowledge-improvement-lifecycle.mjs`.
4. Deny transcript-only, imported-only, secret-like, or untrusted external candidates with a durable reason.
5. For `global-candidate`, require independent review and replay evidence before promotion.
6. For `harness-meta-project` candidate promotion, require independent review, replay, and targeted self-test evidence.
7. For `harness-meta-project` stable promotion, require independent review, affected-project replay, targeted self-test, rollback, and release manifest evidence.
8. Record the runtime ledger decision before attempting any memory write.
9. Write compact promoted facts only after the lifecycle helper returns `approved_for_promotion` and the ledger decision is `promoted`.

## Hard Rules

- Never promote project-local facts by default.
- Never write directly from a source project into the harness graph.
- Never promote raw project graph dumps, raw logs, or raw transcripts.
- Never treat memory, project knowledge, or a promotion ledger decision as completion authority.
- Denials are durable evidence and must include a denial code and reason.
- Unsafe promotion denial must not block unrelated workflow.
- Live MemoryGraph or account-root promotion is forbidden during planning and staged modernization phases unless a controlled rollout approval is present.
- If MemoryGraph is unavailable, report the promotion write skip or failure; do not treat it as success.
- Preserve provenance tags including source project, proposal id, review id, replay id, and release manifest id when applicable.
- Rollback must use `node scripts/runtime-state.mjs rollback-memory-promotion ...` and preserve the original audit row.