C4. Monitoring & Flags
(applies to Trade and Tokens; EDSD = platform stable, EDM = fee/burn token; PoV, EMT, Locked/Unlocked EDSD as defined)
What this section is for
The rail watches the things that matter—evidence, money, clocks, and conduct—and raises clear, actionable flags. Small issues get nudges; real issues pause only what’s affected. Every flag carries the proof you need to fix it. No noise, no surprises, no early payouts.
How monitoring works (in plain words)
EDMA streams signals from orders, listings, attestors, custody, and treasury. Each signal is evaluated against the contract (MPA) or the listing checklist. We classify outcomes into three severities:
Info — something to note (e.g., “top-up due T-24h”).
Warning — attention required, but the flow can continue (e.g., “temperature trend nearing limit”).
Blocker / Freeze — the rail halts a specific slice/listing until the record is clean (e.g., “seal mismatch,” “duplicate serial,” “Pending Funds”).
The UI shows a short sentence and a fix path; your systems get the same message via webhook. Once the fix lands, the flag clears and the timeline resumes.
Trade rail
Milestone clocks & money
We track the review window, gate SLA, and top-up deadlines. You’ll see Pending Funds if the next milestone isn’t funded (no release even with perfect proof), Review Window: Blocked if the buyer paused within their window, and Gate SLA at Risk if an attestor is late.
Evidence & integrity
Pre-Ship expects PSI/COA/lot+pack; On-Board expects BL + seal number & photo that match; Arrival expects DC receipt + QA (and temperature in range for cold chain). Typical flags are Seal mismatch, Lot list mismatch, QA variance over tolerance, Temp out of range. Each shows exactly what failed and how to fix it (upload corrected file, re-inspect, apply variance rule).
Route & identity hygiene
We check lane consistency (origin/destination, container IDs), brand authorization for branded goods, and sanctions/AML updates on the parties. Flags read Brand authorization missing, Container route deviates, or Sanctions hit (auto-hold).
Assignments & cash-out
Suppliers can assign Locked EDSD to whitelisted partners as funded-on-proof credits; we monitor spikes, duplicate recipients, and cap usage. Flags include Assignment cap reached and Anomalous assignment pattern. Off-platform cash-out is flagged if attempted before schedule completion (Cash-out blocked: schedule not complete).
Auto-actions
pauses only the affected slice of Locked EDSD (and dependent future slices),
opens a case with the Dispute Pack (checklist, files+hashes, timeline),
offers re-inspection booking and applies the variance math from the MPA,
resumes automatically on pass or applies a partial-pay/replacement per the contract.
Tokens rail
PoV freshness & revocation
Listings carry a PoV badge; we watch attestor feeds for withdrawal or expiry. Flags are Listing frozen: revocation and clear on update. One-Claim blocks duplicate serials across categories (Duplicate claim blocked).
Market conduct
We detect spoofing and wash patterns on order books; suspicious bursts raise Conduct anomaly (rate-limited) and, if repeated, temporary listing suspension.
Proof-linked settlement
A settlement without valid proof never appears; attempts raise Settlement blocked: PoV mismatch and show the missing element.
Treasury & reserves (what keeps the rail safe)
While Locked EDSD sits on the rail, ~75% is placed in short-dated T-bills and ~25% stays as cash. We publish Proof-of-Reserves, a daily summary, and a simple ladder view (maturities, coverage by order, liquidity buffer). Flags are Reserve mismatch (should never occur), Ladder drift (duration too long), and Buffer low (cash share below the policy). These are platform-facing; you still see the totals and the interest line in your ledger.
What you act on (and where)
Dashboard — a single lane shows green checks and any flags. Click a flag to see the required proof, the fix steps, and the SLA clock.
Webhooks — you already subscribed in C3; the key ones here are trade.milestone.passed, trade.milestone.blocked, trade.milestone.pending_funds, trade.slice.frozen/unfrozen, tokens.listing.frozen/unfrozen, fee.burn.posted, and treasury.interest.accrued.
Explorer — public proof pages show freeze/unfreeze history, file hashes, burn hashes, and the final outcome for that stage/listing.
How flags connect to tiers and governance
Monitoring isn’t just alarms; it feeds improvement. Buyer flags (missed top-ups, false blocks) and seller flags (late docs, temperature variance, revocations) roll into tier scores (see C2) and can promote or downgrade automatically. Attestor latency and accuracy drive SLA rewards/penalties and rotation. Governance (EDM holders) can tune the review window, top-up deadlines, tolerance bands, and attestor SLAs inside safe bounds when data shows a better setting.
Data, privacy, and retention
Evidence files live off-chain with signed URLs; the chain holds hashes. We keep audit logs per order/listing, including who uploaded what and when, for at least the statutory period in relevant jurisdictions. Sensitive documents are never put in webhooks; recipients pull them via expiring links with role-based access.
Plain recap
Last updated