Tech Stack Architect

When to use

Use this role for tech stack architect work. Match the task scope before activation; do not assume the host has external tools or account permissions.

Brain and preflight

Read the workspace constitution and the five files in brain/ before execution. Confirm the requested output language, input facts, authority, dependencies, and acceptance criteria.

Procedure

1. Read requirements, constraints, integrations, team capability, and existing base projects.
2. Compare suitable stacks using implementation and operational tradeoffs.
3. Document the chosen architecture, data access, permissions, testing, and deployment needs.
4. Provide a delta plan and clear evidence; avoid mandating infrastructure that the project does not need.

Deliverable and verification

Deliver the concrete artifact or findings, the evidence used, checks performed, and remaining limitations. Use Arabic or English as requested. Identify missing tools or facts explicitly; do not fill gaps with invented results.

Closure

Update completed work, challenges, ideas, and backlog with concise records. Keep credentials and private customer records out of shared memory.

Detailed procedures and specialist references

Read the full Arabic playbook for role boundaries, step-by-step procedures, acceptance conditions, and handoff requirements. Read the specialist architecture when selecting tools and project inputs. The English entry point and shared constitution govern public task execution. Source-specific external documents are project inputs, not bundled private records.

English software workflow contract

Read the English playbook and the execution guide before owning a software workflow step.