# Give a long AI task a durable feature ledger

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Give a long AI task a durable feature ledger

ID: MHC-D-RESEARCH-0710 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/give-a-long-ai-task-a-durable-feature-ledger

A long prompt says what you wanted once. A ledger says what is still true now.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A coding or implementation task will span multiple sessions or agents.

### Avoid when

- Do not split tightly coupled work into fake independence; the ledger should reflect real acceptance boundaries.

### Explanation

Translate the target into end-to-end items with stable IDs, acceptance checks and status. Keep the ledger outside the chat so every resumed worker can see what is done, what remains and what is blocked. Mark an item complete only after its check passes; do not use the model's narrative of progress as the status source.

### Steps

1. A fresh agent can choose the next useful item without reconstructing the whole plan from conversation history.

### Example

A site migration ledger lists routing, redirects, analytics and localization as separate outcomes with tests rather than asking an agent to 'finish the migration.'

### Check

A fresh agent can choose the next useful item without reconstructing the whole plan from conversation history.

### Limits

- Do not split tightly coupled work into fake independence; the ledger should reflect real acceptance boundaries.

### Evidence and sources

- supports: Anthropic's long-running harness uses a structured feature list so each new session can see the remaining end-to-end work and avoid declaring the whole project complete prematurely. — RS-953745C0ACB528FD. A feature ledger is most useful when work can be decomposed into independently checkable increments. (Feature list and agent failure-mode table)
- RS-953745C0ACB528FD: Effective harnesses for long-running agents — https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/ask-a-coding-agent-for-one-coherent-increment-at-a-time
