# Phase 2: Design Integration Architecture (Weeks 5-8)
### Key Design Decisions:
#### What Goes on Blockchain?
* Purchase order commitments (key terms only)
* Critical status changes (shipped, delivered, verified)
* Authentication events (certification validated)
* Payment triggers (conditions met, funds released)
* Dispute-prone data points (delivery times, quantities)
#### What Stays in EDI?
* Routine confirmations
* Detailed specifications
* High-frequency, low-value transactions
* Internal communications
### Integration Methods:
**Option A: API Integration (Most Common)**
* ERP calls blockchain API to write/query events
* Clean separation, easy to test
**Option B: Middleware Layer**
* Monitors EDI transactions
* Automatically records designated events on blockchain
* No ERP modifications needed
**Option C: Blockchain-Enabled EDI Gateway**
* Processes EDI documents normally
* Creates blockchain records automatically
* Transparent to trading partners
Most organizations start with API integration for proof of concept, then evaluate middleware for production scale.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/the-business-case-for-blockchain-in-supply-chain/blockchain-vs.-traditional-edi/phase-2-design-integration-architecture-weeks-5-8.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.