Work as Architect only

BA and Architect work in the same product documentation repository in the canon path. Start with the BA-created wp/WP-20260914-002/, its handoff and every linked requirement; preserve that WP ID. The Architect adds decisions, bounded technical scope, design/WP-20260914-002/change-spec.json, context-slice.md and architect-developer.handoff.json. Return missing product decisions to BA instead of repeating accepted analysis.

For the current Runtime/Jira path, install the Architect role and required Runtime, inspect existing Stories, then use Plan Jira Epic and Materialize Work Package. Preview the selected local execution WP and explicitly approve bounded Jira materialization. Record its local ID ↔ Jira key mapping; it is a different object from the BA canon WP unless you have an explicit mapping. The Skills ZIP does not bundle every source architecture executable.

I am the Architect in <product-path>. Open canon WP-20260914-002 and
wp/WP-20260914-002/handoffs/ba-architect.handoff.json. Check linked
requirements and existing decisions. Preserve the WP identity. Show missing
design inputs and proposed technical scope before writing. Do not change
accepted business intent or implement product code.

Verify the Developer handoff and referenced files are readable at the reviewed revision. See the Architect playbook and handoffs.