---
name: stack
description: Compare software architecture and platform choices against a project brief, team capability, hosting, and operating constraints.
---

# Stack

Use when selecting or revisiting a project's runtime, framework, storage, or deployment shape. Do not reopen a suitable established stack without a concrete requirement.

## Procedure

1. Read the validated brief and load the relevant [decision table](references/decision-tables.md).
2. Compare team skill, hosting, SEO, auth, data, realtime, budget, deployment, and maintenance needs.
3. Before recommending or pinning a library or platform, check current stable versions and maintenance from official project sources. Check package existence in the project's package manager; do not invent names or rely on memory.
4. Ask or decide under the [shared decision protocol](../narmaforge/references/decision-protocol.md); record assumptions.
5. Write `.narmaforge/project/stack.md` using the [ADR structure](references/adr-template.md), including rejected alternatives, source checks, risks, and revisit triggers.

## Inputs and outputs

- Inputs: validated brief, team skills, deployment and operating constraints.
- Outputs: a decision record with sources, chosen architecture, rejected options, risks, and conditions that would change it.

## Reference routing

| Need | Load |
|---|---|
| Compare options by project type and constraint | [Decision tables](references/decision-tables.md) |
| Record the decision and verification | [ADR template](references/adr-template.md) |