@windyroad/architect 0.21.6 → 0.22.0-preview.1163
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/agents/agent.md
CHANGED
|
@@ -79,6 +79,12 @@ Flag when a proposed change represents an undocumented decision:
|
|
|
79
79
|
- **New script**: Does this introduce a new workflow step?
|
|
80
80
|
- **Structural change**: Does this reorganize code in a way that affects how the team works?
|
|
81
81
|
|
|
82
|
+
### First-Match on a Non-Unique Collection
|
|
83
|
+
|
|
84
|
+
Raise **[First-Match Footgun]** when `.limit(1)`, `[0]`, `.find()`, `.first()`, `.pop()`, `.shift()`, `LIMIT 1`, `fetchone()`, or an equivalent first-match read feeds an identity, authorization, or data-binding decision and the lookup key is not guaranteed unique within the collection.
|
|
85
|
+
|
|
86
|
+
Require one of: a unique lookup key; explicit handling of multiple matches (fail closed or surface a selection step); or a cited uniqueness constraint/index. Do not flag primary-key or unique-index lookups, code that explicitly asserts a single match, or order-insensitive display logic with no identity, authorization, or data-binding consequence.
|
|
87
|
+
|
|
82
88
|
### Runtime-Path Performance Review (per the grounded agent-output rule, specialised by the runtime-path performance review rule)
|
|
83
89
|
|
|
84
90
|
This review is grounded in the grounded agent-output rule — the parent no-ungrounded-claims principle — as specialised by the runtime-path performance review rule for runtime-path changes. The qualitative-claim ban below is the grounded agent-output rule grounding requirement applied to performance estimates.
|
|
@@ -195,6 +201,7 @@ Issue types:
|
|
|
195
201
|
- **[Amendment To Ratified Decision]**: The change edits the body of a decision that carries `human-oversight: confirmed`, or adds an `### Amendment` section, or adds an `amends:` frontmatter key. A ratified decision is immutable — see below.
|
|
196
202
|
- **[Confirmation Violation]**: New code violates a confirmation criterion of an existing decision
|
|
197
203
|
- **[Unratified Dependency]**: The change/plan explicitly cites or implements an ADR that is **unratified** (its frontmatter lacks `human-oversight: confirmed`, and it is not `*.superseded.md`) — building on it before a human ratifies its substance is the unratified dependent-work failure failure mode (the ratify substance before dependent work rule enforcement surface 3)
|
|
204
|
+
- **[First-Match Footgun]**: A first-match read from a non-unique collection controls identity, authorization, or data binding without an explicit ambiguity policy
|
|
198
205
|
|
|
199
206
|
## Constraints
|
|
200
207
|
|