@@ -8,7 +8,7 @@
 
 **What counts as done**: an application built on the protocol is done only once it has passed verification — the checklist items its metadata maps to pass in one run, and `objectstack verify` is green on it. A delivery that has not passed verification does not count as done.
 
-**The one measure: the road**: a new AI developer (a human accepting alongside) starts from `npm create objectstack`: write metadata → run it locally and see it → verification loudly rejects what is wrong and lets through what is right → publish and install into an environment → connect an agent (MCP in the community edition) and have it complete one real business operation in the application → iterate once on a one-sentence customer request. Walk it for real every week, and the result lands as a run record. The first step that breaks is the current P0; one that runs through but gives a wrong result is P2. The four promises are each kept by a step: ① AI can write it · ②③ it executes · ④ you own it · ⑤ agents can operate it · ⑥ it closes the loop.
+**The one measure: the road**: a new AI developer (a human accepting alongside) starts from `npm create objectstack`: write metadata → run it locally and see it → verification loudly rejects what is wrong and lets through what is right → publish and install into an environment → connect an agent (MCP in the community edition) and have it complete one real business operation in the application → iterate once on a one-sentence customer request. Walk it for real every week, and the result lands as a run record. The first step that breaks is the current P0; one that runs through but gives a wrong result is P2. The four promises are each kept by a step: ① AI can write it · ②③ it executes · ④ you own it · ⑤ agents can operate it; the sixth step, ⑥, closes the loop.
 
 **Features on the road**: the features the platform has to deliver, one per line, arranged by the steps of that road; top to bottom is the order — this table is the roadmap, and editing it is editing priority. Each row reads `axis · feature (in business language) · checklist area · item ids`, and one feature is a whole strip from protocol through runtime to the frontend; every item in `docs/qa/platform-checklist/` belongs to exactly one row here (an item not yet written is marked "checklist item to be written"). An id without a prefix belongs to the checklist area before it; one from another area is written in full.