v28.12 · EXTERNAL EVIDENCE + STANDARD FIELD PILOT

Verify procurement-grade evidence,
not just product features.

External evidence required by public-sector and enterprise buyers is tracked according to what has actually been obtained. Certifications, field outcomes and independent reviews are never shown as complete without real evidence.

External evidence checkpoints

CSAP pathEVIDENCE PENDING

Scope, qualification path and external evidence remain separated from internal controls.

99.5% SLACONTRACT / OBSERVATION PENDING

Monthly availability target, service credits and observed availability evidence are required together.

Independent security reviewEXTERNAL AUDIT PENDING

Provider, report ID, completion date and remediation status are required for verified language.

Processor / Data ExitDOCUMENT EVIDENCE PENDING

Processor, cross-border transfer, retention, deletion and return/export must be formally documented.

8–12 week field pilotFIELD EVIDENCE PENDING

Baseline, consistent KPI definitions, real samples, evidence hashes, buyer confirmation and independent review are all required.

Vision Ground TruthFIELD VERIFICATION PENDING

TP/FP/TN/FN, device health, fail-safe behavior and human review boundaries are verified together.

Procurement packageSTRUCTURE READY

Specification, pricing, support, exit, security summary and AI responsibility principles are packaged for review.

Claim controlFAIL-CLOSED

No unsupported certification, outcome or superiority claim is published.

Current decision: CONDITIONAL PASS
Architecture and automated verification are strong, while CSAP certification, measured SLA evidence, actual 8–12 week field outcomes, Vision ground truth and independent security review remain external evidence gates. Synthetic data cannot support pilot outcome claims.
Unified Release Axis · v28.12

Korean and English, customer desktop/mobile, admin desktop/mobile, homepage desktop/mobile, GitHub source and Render production use the same evidence state.