# Technical Content Brief

## 1. Deliverable

- Choose one: technical accuracy audit / reproduced tutorial / engineering case study / evaluation note / three-piece content sprint
- Language: English / Chinese
- Preferred length or format:
- Desired delivery date:

## 2. Audience and action

- Primary reader:
- What should the reader understand or do after reading?
- What does the reader already know?

## 3. Product or workflow

- Product / repository / API / paper:
- Exact version, branch, or release:
- Smallest workflow that should be reproduced:
- Supported operating system or environment:

## 4. Approved evidence

- Official documentation:
- Public repository:
- Approved benchmark or dataset:
- Existing draft, notes, screenshots, or logs:

## 5. Boundaries

- Information that must not appear:
- Claims that require explicit attribution:
- Credentials or production access required? If yes, the scope must be redesigned to avoid them.
- Legal, security, or compliance review needed on your side:

## 6. Acceptance criteria

- Commands or examples that must run:
- Claims that must be verified:
- Required links or references:
- File format: Markdown by default; specify any additional format.

## 7. Contact and payment

- Preferred asynchronous contact channel:
- Contract / platform requirements:
- Currency and payment method supported by your organization:

Do not include passwords, API keys, private customer data, proprietary source code, or regulated personal information in this brief.