Artifacts

Files that the harness reads and writes during the lifecycle.

State

File	Path	Purpose
AGENTS.md	root	Project rules, entry points
feature_list.json	root	WIP=1 source of truth
STATE.md	.specs/project/	Durable progress, blockers, decisions
session-handoff.md	docs/harness/	Transfer between sessions
sprint-contract.md	docs/harness/	Scope, AC, verification plan
quality-thresholds.json	agent-os/	Metrics, risk routing, and governing keys
learned-rules.json	agent-os/	Project-local ledger of active, conflicting, and retired rules
<run>.json	docs/harness/findings/	Append-only typed-findings window bound to the gate
refine-log.md	docs/harness/	Proposals, rejections, and Refine-cycle decisions

Feature list

Each feature in feature_list.json uses the fields below:

Field	Description
id	Unique identifier
priority	Execution order
area	Project area
title	Short name
user_visible_behavior	What the user/agent sees when it works
dependencies	IDs of features that must be completed first
status	not_started, in_progress, passing or blocked
verification	Command that proves it works
evidence	Real output captured after verification
notes	Additional information

Status rules

• Only ONE feature in_progress at a time.
• passing requires evidence filled with real output.
• blocked requires the exact cause in the evidence field.
• No feature in_progress with unresolved dependencies.

v1.3 artifact ownership

• Reviewers return records; the scheduler validates and writes each findings file once.
• Refine reads findings and the ledger but writes neither.
• Approved rules land after code as a separate change because the rulebook remains inside the gate source hash.
• Governing numbers live in quality-thresholds.json, never in prose.