# AI project specification: guided editable template

Functional scoping document, not a contract. Status: DRAFT. Date/version: [complete]. Replace the examples; they describe a fictional project.

## 1. Business outcome

Task, user, trigger, output and exclusions.

Your answer: [complete]

Fictional example: Prepare C-017 / Rouen-02 / quoted problem / requested date; do not schedule a technician.

Evidence or next action: One input and the output accepted by the person handling the case.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 2. Data and access

Sources, owner, formats, version, permissions, sharing, proposed hosting and retention period to decide.

Your answer: [complete]

Fictional example: Request M-001 and authorised customer records; no record outside the reader role.

Evidence or next action: Source inventory and access confirmation; unknown sharing permission remains blocking.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 3. Volumes and current process

Average, peaks, file sizes, observation period, current handling time and measurement method.

Your answer: [complete]

Fictional example: Volume unmeasured: do not infer 1,000 cases from the educational calculation.

Evidence or next action: Source for each number, or an assumption and measurement plan.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 4. Actions and approval

Read access, proposed fields, writes, approved version, authorised people and prohibitions.

Your answer: [complete]

Fictional example: Create after approval of the exact version; ask again if a field changes afterwards.

Evidence or next action: R04/T04: no approval, stale approval and unavailable approver.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 5. Exceptions and recovery

Missing data, ambiguous identity, unreadable file, conflicting sources, outage and repetition.

Your answer: [complete]

Fictional example: Two possible customers: select neither. Lost response after creation: inspect state before retrying.

Evidence or next action: Cases T02/T03/T05, recovery rule and person resolving the case.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 6. Acceptance and decision

Requirements, cases, expected results, blocking criteria, independent dataset and decision-maker.

Your answer: [complete]

Fictional example: Creation without approval blocks acceptance; an aggregate score does not compensate.

Evidence or next action: 08-recette.csv and 08-decision-pilote.md; observations blank until testing.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 7. Operation and absences

Owner, working hours, alerts, substitute, recovery and changes requiring renewed validation.

Your answer: [complete]

Fictional example: Without an available approver: request waits, no creation; name a substitute.

Evidence or next action: Recovery procedure and confirmed roles/contact details; no implied 24/7 coverage.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 8. Service exit

Data, proposals, rules, configurations and records to retrieve; formats and dependencies.

Your answer: [complete]

Fictional example: Export one proposal and its rule; verify reading outside the service.

Evidence or next action: R07/T07 and agreed file inventory, handover owner.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 9. Budget and dependencies

Period, volume, one-off/recurring costs, internal time, access dependencies and quote boundaries.

Your answer: [complete]

Fictional example: No price supplied: unknown, not zero; separate scoping and implementation.

Evidence or next action: 08-comparer-offres.md completed against the same scenario for each offer.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

## 10. Version and open questions

Version, author, business owner, approver, decisions and open questions.

Your answer: [complete]

Fictional example: Q01: target tool unknown; name an administrator; resolve before connector pricing.

Evidence or next action: One person and due date per question; new version after a decision.

Status: [confirmed / assumption / open]. Owner: [name]. Due date or source: [complete].

Before sending: follow 08-demarrer.md, attach the agreed examples and list unresolved questions. Do not claim field performance from this template.
