# EcoKure enterprise sales and trust pack

## One-sentence position

EcoKure is a customer-boundary assurance runtime that turns AI or operational
proposals into governed verdicts, human review and independently inspectable
EvidencePacks.

## What a buyer can see now

- A bounded adoption path from readiness evaluation to shadow pilot,
  change-impact review and go/no-go decision.
- Control Pack catalogue and MIT AI Risk Repository mapping workflow.
- Authenticated enterprise workspace with roles, review queue, Control Packs,
  change events and EvidencePack links.
- AWS target-representative evidence: 117,290 completed verifications, zero
  performance errors, KMS-backed signing, PostgreSQL persistence and controlled
  recovery with no lost acknowledgements.
- A machine-readable AWS EvidencePack and a standalone verification guide.

## Trust boundary

Customer data, evidence stores, signing keys, identity and deployment controls
belong inside the customer-approved boundary. EcoKure records digests and
governed metadata according to the agreed pilot scope. Customer reviewers retain
decision authority; recommendations remain proposed until approved.

## Standards and regulation

EcoKure maps a regulation or standard to a customer-owned control and then to
customer evidence. It does not claim legal certification, regulatory approval,
ISO certification or compliance merely because a crosswalk exists.

## Pilot stages

1. Choose one bounded workflow.
2. Baseline the process and evidence burden.
3. Define and review the Control Pack.
4. Run in shadow mode.
5. Introduce one controlled change event.
6. Selectively replay affected work and route uncertainty to a human.
7. Produce and independently inspect the EvidencePack.
8. Make a documented go/no-go decision.

## Procurement answers

| Question | Current answer |
|---|---|
| Where does it run? | Customer-owned AWS, private cloud or other agreed boundary; target states are labelled explicitly. |
| Does it use an LLM to decide? | The assurance lane is deterministic; customer AI may propose, EcoKure checks declared controls and evidence. |
| Who approves? | Named customer control/risk owners and qualified reviewers. |
| Is the AWS result production validation? | No. It is target-environment evidence, not customer production validation or certification. |
| Can evidence be checked independently? | Yes, using the supplied manifest/verifier instructions; customer-controlled signing is required for production packs. |
| What is out of scope? | Clinical diagnosis, credit approval, payment movement, safety-system replacement and physical actuation. |

## Documents

- `docs/outreach/DANIEL_BUYER_BRIEF.md` (one-page buyer explanation)
- `docs/outreach/DESIGN_PARTNER_PILOT_BRIEF.md` (flagship pilot offer and acceptance criteria)
- `docs/ADVISORY_BOARD_DISCUSSION.md` (proposed roles and decision questions)
- Buyer route: `/enterprise/handoff` (architecture, security, pilot and evidence in one review path)
- `docs/AWS_CUSTOMER_HANDOFF_RUNBOOK.md`
- `docs/ENTERPRISE_INTEGRATION_RUNBOOK.md`
- `docs/DPA_OUTLINE.md`
- `docs/PENETRATION_TEST_BRIEF.md`
- `docs/SLO_POSITION.md`
- `/trust`, `/deployment`, `/adoption` and `/standards-crosswalk`