docs: qbit-edi design spec #4

Merged
KofTwentyTwo merged 1 commits from feature/design-spec into develop 2026-10-14 00:43:50 +00:00
KofTwentyTwo commented 2026-10-14 00:41:49 +00:00 (Migrated from github.com)

Summary

The design spec for qbit-edi in docs/DESIGN.md (replaces the placeholder). Stacked on #1 (the scaffold); the diff is the spec only once #1 merges.

Covers:

  • Trading partners, identities, agreements, agreement documents, control numbers (ISA13/GS06/ST02), duplicate detection, ack expectations and overdue alerts via core QAlerts.
  • Transports as data with a plugin SPI: AS2 (as2-lib), SFTP inbound via the qbit-file-gateway api (contract settled with that agent), SFTP push and VAN polling via core's SFTP client, gateway OUTBOX, HTTPS, email via qbit-email.
  • StAEDI parsing; implementation guides as data (segments, elements, R/S/N usage, syntax and situational rules, code lists) with versioned partner overrides; licensing approach for X12/TR3 content.
  • Versioned data-driven maps with transforms; sandbox as a record action now, mapper UI in phase f.
  • Inbound and outbound flows, durable inbox, apply as a service session, resend/reprocess, business-key search, timeline, exception queue.
  • HIPAA: PHI classification, SNIP 1-7 support table, canary egress tests; payloads encrypted in object storage (database fallback), no local files (owner rule).
  • App home (typed widgets), permissions, partner locks, demo in qqq-sample-project, phases a-g with acceptance.

Owner decisions (2026-10-12): all recommendations accepted; the 2026-10-13 decisions are recorded.

🤖 Generated with Claude Code

## Summary The design spec for qbit-edi in `docs/DESIGN.md` (replaces the placeholder). Stacked on #1 (the scaffold); the diff is the spec only once #1 merges. Covers: - Trading partners, identities, agreements, agreement documents, control numbers (ISA13/GS06/ST02), duplicate detection, ack expectations and overdue alerts via core `QAlerts`. - Transports as data with a plugin SPI: AS2 (as2-lib), SFTP inbound via the qbit-file-gateway `api` (contract settled with that agent), SFTP push and VAN polling via core's SFTP client, gateway OUTBOX, HTTPS, email via qbit-email. - StAEDI parsing; implementation guides as data (segments, elements, R/S/N usage, syntax and situational rules, code lists) with versioned partner overrides; licensing approach for X12/TR3 content. - Versioned data-driven maps with transforms; sandbox as a record action now, mapper UI in phase f. - Inbound and outbound flows, durable inbox, apply as a service session, resend/reprocess, business-key search, timeline, exception queue. - HIPAA: PHI classification, SNIP 1-7 support table, canary egress tests; payloads encrypted in object storage (database fallback), no local files (owner rule). - App home (typed widgets), permissions, partner locks, demo in qqq-sample-project, phases a-g with acceptance. Owner decisions (2026-10-12): all recommendations accepted; the 2026-10-13 decisions are recorded. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.