Development record
2026-10-31 — The ideate verdict payload gains current_state as a required top-level field while staying schema_version 2 (iss-2610310815034547). Grounds: the version number exists to stop a host composing against an old page from being misread in silence, and a payload without the field cannot be misread: it is refused with a message naming current_state and both modes, so the host that sent it learns exactly what to add. A version bump would refuse every old payload with a message about the version rather than the field, and would churn every fixture for no extra protection. The field sits at the top level rather than on the adversarial leg because it is the person's choice for the run, stated before the legs start. Reverse by bumping SchemaVersion to 3 in internal/core/ideate and teaching olderSchemaError that version 3 adds current_state.
2026-10-31 — The ideate verdict payload gains current_state as a required top-level field while staying schema_version 2 (iss-2610310815034547). Grounds: the version number exists to stop a host composing against an old page from being misread in silence, and a payload without the field cannot be misread: it is refused with a message naming current_state and both modes, so the host that sent it learns exactly what to add. A version bump would refuse every old payload with a message about the version rather than the field, and would churn every fixture for no extra protection. The field sits at the top level rather than on the adversarial leg because it is the person's choice for the run, stated before the legs start. Reverse by bumping SchemaVersion to 3 in internal/core/ideate and teaching olderSchemaError that version 3 adds current_state.
Frontmatter
| id | dcn-2610311344529366 |
|---|---|
| type | decision |
| date | 2026-10-31 |
.abcd/work/decisions/dcn-2610311344529366-the-ideate-verdict-payload-gains-current.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610310815034547The ideate protocol's adversarial leg gives reviewers no way to tell an ambition from a present-tense claim, so an idea about where a repository's product should go is killed because the product does not deliver it yet. On a 2026-10-31 run on a positioning idea (in abcd's own repository, where abcd is the product), both reviewers marked it fatal on current delivery gaps. The product thinker ruled that not yet built is never a reason to kill an ambition: the gap is the roadmap the exercise exists to find.