meta.json
Fields, identifier, type, state and commits of each Work Item's durable record.
Location
Each Work Item lives in .rei/specs/<work-item-id>/ and contains a single meta.json. The folder name is the Work Item's immutable id and must match .rei/progress/work-items/<work-item-id>/.
.rei/specs/
└── <work-item-id>/
├── meta.json
└── ...Fields
| Field | Content |
|---|---|
id | Immutable identifier. It matches the folder in .rei/specs/ and in .rei/progress/work-items/. |
title | Short, descriptive name of the Work Item. |
description | Technical description of the agreement reached with the user; it does not copy the conversation. |
type | feature or task. |
status | Current stage of the workflow. The valid values and their transitions are in the states reference. |
created_at | Creation date and time in ISO 8601, with time zone. It matches the id prefix. |
base_commit | SHA of the commit that marks the start of the implementation. Empty if the project does not use git. |
last_review_commit | SHA of the point already reviewed. Empty if not applicable. |
The identifier
The id is built from the creation date and time and a kebab-case slug. It does not change even if the work is resumed or the title changes.
YYYY-MM-DD_HH-mm__slug-en-kebab-caseIf an identical identifier already exists, a numeric suffix is added to the slug (-2, -3, ...) without changing the original date and time. The id is generated when the Work Item is created; it is not rewritten afterwards.
type and status
type decides the planning that is generated and whether the GitHub Issues integration opens an issue and a branch. A feature produces requirements.md, design.md and tasks.md; a task produces plan.md and generates no issue or branch.
status records the workflow stage and accepts the harness's seven states. Their meaning and transitions are documented in the states reference, which is the single source; they are not repeated here.
base_commit and last_review_commit
Both fields are written by the CLI with the current git commit. base_commit is recorded by the Leader when approving the Work Item; last_review_commit is recorded by the Reviewer when rejecting the implementation.
rei commit set <work-item-id> base_commit
rei commit set <work-item-id> last_review_commitrei review-diffusesbase_commitas the base point of the review package.- If
last_review_commitis present,review-diffcomputes the diff from that point and the review sees only the requested changes. - For the diff to stay bounded, the implementation must be committed before requesting the review; if it is not, the diff covers everything pending since
base_commit. - In a project without
gitboth fields stay empty.
meta.json and current.md
meta.json is the durable record of each Work Item and the reference for diagnosing the set with rei items status. current.md is the live context of the active session: it lets you resume exactly where it was left if the conversation is interrupted.
| File | What it records | Scope |
|---|---|---|
meta.json | Type, state, dates and commits. | Durable; it survives the end of the session. |
current.md | State, plan, log and next step. | Active session; archived when the Work Item is closed. |
Both files are maintained and complement each other. The state in meta.json is not inferred from the conversation or from the agent's memory.
A human sign-off releases the sheet. Silence is not approval.