# DenQAI: purchasing pilot charter

File-specific companion · 2026-09-10

## Purpose

What governance would a hypothetical purchasing pilot need before accepting members, funds, or data?

**Who:** Planning group with independent governance and specialist reviewers

**Records:** Proposed authority map; funding model; clinical exception rules; data map; complaint, portability, and exit design.

## Complete the file

1. Review Purpose and define the precise purchasing job the hypothetical pilot would serve.
2. Assign proposed owners and records to member-control, clinical, commercial, data, value, complaint, and exit principles.
3. Document evidence for every Launch boundary item and keep unimplemented items explicitly open.

## Definitions

- **Member control:** Written authority over governance, material changes, records, and exit.
- **Clinical autonomy:** Preserved treating-clinician judgment and documented exceptions.
- **Launch boundary:** Conditions that must be implemented and reviewed before operating the proposed pilot.

## Fictional example

Fictional example: A draft pilot limits scope to common consumables but has no complaint owner or tested data export; those launch items remain open.

## Review and next action

Prepare a reviewed implementation decision only after each launch boundary has supporting evidence.

This Markdown charter is hypothetical educational design, not bylaws, an operating cooperative, or authority to exchange competitive information.

[Related DenQAI guide](https://denqai.com/independent/governance)

## AI coach prompt

Help me use DenQAI’s purchasing pilot charter. My question is: What governance would a hypothetical purchasing pilot need before accepting members, funds, or data? Explain these terms in plain language: Member control, Clinical autonomy, Launch boundary. Ask one question at a time about the required records: Proposed authority map; funding model; clinical exception rules; data map; complaint, portability, and exit design. Walk through the supplied fictional example before asking me for inputs. Treat every missing value as unknown, not zero. Do not invent source records, contract terms, legal conclusions, or clinical facts. Use only permitted fictional or aggregate, non-identifying information. Follow this boundary: This Markdown charter is hypothetical educational design, not bylaws, an operating cooperative, or authority to exchange competitive information. End with the missing evidence and this next step: Prepare a reviewed implementation decision only after each launch boundary has supporting evidence.

## AI review prompt

Review my permitted fictional or aggregate draft of DenQAI’s purchasing pilot charter against the file instructions. Check each required field and period, units, evidence locator, assumptions, arithmetic where formulas are actually supplied, and unresolved contradictions. Check the sequence: Review Purpose and define the precise purchasing job the hypothetical pilot would serve. Assign proposed owners and records to member-control, clinical, commercial, data, value, complaint, and exit principles. Document evidence for every Launch boundary item and keep unimplemented items explicitly open. Separate facts from assumptions and missing records. Do not supply unsupported numbers or make a professional decision for me. Apply this limitation: This Markdown charter is hypothetical educational design, not bylaws, an operating cooperative, or authority to exchange competitive information. Return corrections, questions for the responsible reviewer, and the next action.