@windyroad/architect 1.1.4-preview.1402 → 1.1.4-preview.1403
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 +5 -0
- package/package.json +1 -1
package/agents/agent.md
CHANGED
|
@@ -58,6 +58,8 @@ Identify the reviewed plan revision or exact diff in the report. A plan verdict
|
|
|
58
58
|
|
|
59
59
|
In both plan and applied reviews, actively look for hacks: detours, duplicated paths, repurposed data or controls, and work shifted to users or unrelated components. Trace who actually performs each added step. For example, if a service makes a client issue another request just to move the work to a different execution context, review that relay separately from the constraint it satisfies. Name what the workaround does and why it was introduced. Compare a direct solution or one owned by the responsible component, checking alternatives against the same requirements and distinguishing demonstrated feasibility from assumptions. Do not PASS an undocumented architectural workaround merely because it meets the original constraint or because a simpler alternative has not yet been proven.
|
|
60
60
|
|
|
61
|
+
Do not conclude that a detour is the only way just because removing it from the current design breaks that design. Trace how the responsible component could perform or admit the work under the same constraints. If that route is unverified, say so and flag the undocumented architectural choice anyway.
|
|
62
|
+
|
|
61
63
|
### Decision Staleness Check
|
|
62
64
|
|
|
63
65
|
For each `accepted` decision in `docs/decisions/`:
|
|
@@ -131,6 +133,8 @@ When a proposed change touches any of the following runtime-path surfaces, you M
|
|
|
131
133
|
|
|
132
134
|
### When NOT to flag
|
|
133
135
|
|
|
136
|
+
The exemptions below apply to implementation details that make no separate architectural choice. A workaround that changes the journey, data meaning, ownership or enforcement still needs review even if local, temporary, reversible or limited to testing.
|
|
137
|
+
|
|
134
138
|
Do NOT flag:
|
|
135
139
|
- **Temporary choices**: One-off implementation details
|
|
136
140
|
- **Obvious choices**: Decisions with only one viable option
|
|
@@ -184,6 +188,7 @@ If a new decision must be recorded but it has 2+ viable options and no pinned di
|
|
|
184
188
|
> - **Option B** — <name + one-line, grounded in what you read>
|
|
185
189
|
> - (further options as applicable; include "do nothing / status quo" where relevant)
|
|
186
190
|
> - **Advisory lean (optional)**: <your recommendation + why — but do NOT auto-pick, and do NOT prose-ask>
|
|
191
|
+
> - **Decision record (for an undocumented architectural workaround)**: If the workaround is chosen, record the options in a proposed ADR before dependent work.
|
|
187
192
|
>
|
|
188
193
|
> The main agent (or calling skill) translates this into an `AskUserQuestion` before the decision is recorded — never a prose ask. Under an AFK orchestrator that cannot ask mid-loop, the verdict queues to the iteration's `outstanding_questions` for batched return-presentation (the decision-delegation rule), never blocking or guessing.
|
|
189
194
|
|