tech-spec.md.example

# tech-spec.md Customization Guide

This file is a template for local project technical notes.

Use it only for concrete technical stack details and technical constraints that agents must follow while working in the repository.

## Technology stack

- language:
- runtime:
- framework:
- package manager:
- database:
- test framework:
- build tool:
- deployment target:

## Required commands

List commands agents should use:

- install:
- format:
- lint:
- typecheck:
- test:
- build:
- codegen:
- migration check:

## Forbidden or unsafe commands

List commands agents must not run, or may run only with explicit approval:

- command:
  - reason:
  - safer alternative:

## Technical notes

Document concrete project-specific technical constraints:

- generated files:
- migration rules:
- runtime compatibility:
- API compatibility:
- platform-specific notes:
- local service requirements:
- known command caveats:

## Architecture source of truth

If you are using the AI coding architecture methodology, link the four core architecture files here:

- AI coding architecture: ./tech-spec/ai-coding-architecture.md
- Contract/state matrix: ./tech-spec/contract-state-matrix.md
- Hard parts register: ./tech-spec/hard-parts-register.md
- Task acceptance matrix: ./tech-spec/task-acceptance-matrix.md

## ProofLoop projection rules

- Propose may project these docs into OpenSpec artifacts.
- Propose must not weaken acceptance criteria.
- Executor must use tasks and evidence requirements derived from OpenSpec artifacts.
- Any architecture drift must update the relevant source document through Brain-authorized General edit.

## Do not put here

- ProofLoop route definitions.
- Agent role behavior.
- Dispatch packet fields.
- Product roadmap.
- PRD content.
- Broad architecture essays.
- Data-flow documentation unless it directly affects commands or technical constraints.
- Task plans or implementation checklists.