29. Supplier performance and scoped response portal
Create deterministic supplier performance evidence and a minimal supplier response boundary without granting portal access to Moduvio or authority over any source record.
Purpose
Create deterministic supplier performance evidence and a minimal supplier response boundary without granting portal access to Moduvio or authority over any source record.
Supplier Quality Engineer, different Procurement Manager, two different QA Head users, external supplier representative, Buyer and Auditor read-only
SSC-… v1 → exact-source approval → UNCLASSIFIED QA release → one-time token redemption → immutable supplier response → separate QA acceptance.
Before you begin
- The supplier and site already exist
- At least one PO schedule, disposed receipt inspection, supplier NCR or issued SCAR exists in the completed period
- Every internal actor is active, same-site scoped and cleared for the highest frozen source
- At least one same-site ACTIVE, CLEAN evidence version exists
- A separate governed channel is available if the operator chooses to deliver the copied link
Exact calculation, public-data minimisation and response separation
SUPPLIER_PERFORMANCE_V1 reads current approved PO schedule lines and cumulative receipts, disposed incoming inspections, supplier-linked NCRs and issued SCAR response/effectiveness history. The UI offers no manual source substitution.
A different Procurement Manager recalculates the source population. Approval requires the deterministic SHA-256 fingerprint to match the immutable author snapshot.
A different QA Head releases only the stored UNCLASSIFIED public summary. Internal source identities, classifications, documents and named-user review history stay inside authenticated Moduvio.
The response link is returned in plaintext once. Only a strong hash is retained; it has expiry, revocation and single-redemption state. Redemption returns a separate short-lived, scorecard-scoped response session whose hash is also stored.
The portal has no tenant navigation, login, other supplier lookup, evidence download or file upload. Public access is rate-limited and generic errors do not reveal token state.
The external response is immutable portal evidence. A QA user different from the author, exact-source reviewer and supplier-facing releaser accepts or rejects it.
Flow 23 copies a link but sends no email, creates zero notification deliveries and records no delivery acknowledgement. Governed delivery, retries and secure acknowledgement belong to Flow 25.
Flow 23 never changes vendor approval, PO/award/amendment/schedule/expediting, receipt/inspection, NCR/SCAR, current_stock or stock_ledger records.
Procedure
- 1
Create and submit the exact-source scorecard as Supplier Quality Engineer.
- 2
Approve the unchanged source fingerprint as a different Procurement Manager.
- 3
Release the UNCLASSIFIED summary and copy the once-returned expiring link as a different QA Head; do not claim Moduvio delivered it.
- 4
Redeem and respond once through the isolated supplier page.
- 5
Accept or reject the response as a second QA Head and reconcile zero source/module side effects as Auditor.
Expected result
- Lifecycle follows DRAFT → SOURCE_REVIEW → RELEASE_REVIEW → RELEASED → RESPONSE_REVIEW → CLOSED
- Author, exact-source reviewer, releaser and response reviewer are four different named internal users
- Score calculations retain exact immutable source snapshots and deterministic fingerprint
- Only an approved UNCLASSIFIED summary reaches the portal
- Plaintext credentials are returned once and only strong hashes are stored
- Public access is expiring, revocable, rate-limited, single-use and scoped to one supplier/scorecard
- The portal exposes no tenant navigation, internal evidence, classified detail or named-user history
- Flow 23 creates zero notification deliveries and never changes vendor, Procurement, inspection, NCR, SCAR, inventory or ledger records
- Buyer and Auditor mutation attempts are rejected