EAG/DZG Customer PoC
Review evidence, approval, and undefined areas before adopting EAG settings
EAG/DZG Customer PoC is a bounded review route before adopting EAG settings. It maps pass / hold / escalate / undefined outcomes and produces mismatch and undefined reports for human review.
The result is for human review. Customer PoC acceptance is not production approval.
Problem statement
Teams need a way to inspect evidence, approval, and external-action settings before adopting them. A candidate setting can look useful in a narrow example while still needing review across hold, mismatch, and undefined cases.
EAG means Evidence / Approval / External-action adequacy gate. DZG organizes deployable candidate regions for review; it does not choose policy.
What the PoC does
Runs the documented v0.2 EAG/DZG fixture route.
Maps pass / hold / escalate / undefined outcomes for candidate EAG settings.
Produces mismatch reports for human review.
Produces undefined reports for specification-improvement review.
Builds a handoff pack for recipient inspection.
What customer receives
- Customer-facing one-page summary
- Customer PoC pack draft
- Customer PoC acceptance boundary
- Calibration run artifacts
- Handoff pack artifacts
- Mismatch report
- Undefined report
- Boundary note
- Human review checklist
What customer checks
- Target workflow fit
- Evidence requirements
- Approval requirements
- External-action requirements
- Mismatch outputs that may need fixture or setting revisions
- A_undef outputs that require specification work
- Human owner for adoption or revision scope
Expected outputs
run_manifest.json
verdicts.jsonl
summary.json
zone_summary.json
mismatches.json
undefined_report.json
recommended_setting_bundle.json
handoff_manifest.json
mismatch_explanation.md
undefined_items.md
boundary_note.md
Mismatch and undefined reports remain review outputs. A_undef items are inputs for specification improvement, not automatic adoption.
Partner / SIer support boundary
Partners may help customers run the documented route and review outputs.
Partners may not alter verdict semantics. Partners may not hide mismatch/A_undef. Partners may not claim certification or production approval.
Partner implementation is not C3 certification unless separately granted.
Prohibited claims / non-claim boundary
production approved
externally certified
truth verified
legally certified
third-party certified
BYO-AI approved
supporter-approved
general safety proven
C3-certified implementation
automatic policy adoption
broad sublicensing granted
resale rights granted
This is not production approval.
This is not external certification.
This is not a truth guarantee.
The 100-case corpus does not prove general safety.
DZG does not make policy choices.
AMS does not make value judgments.
EAG settings require human adoption.
Z_deploy is a deployable candidate region, not legal certification.
BYO-AI is optional and non-authoritative.
Customer PoC acceptance is not production approval.
Partner status does not affect verdicts.
Partner implementation is not C3 certification unless separately granted.
Broad resale and sublicensing are not granted by this page.
Proposal/PDF materials remain review materials unless separately approved.
Document links
The following are source document references from the EAG/DZG public documentation lane. They are shown as references rather than broken public links.
Customer-facing
- docs/eag_dzg/customer_facing_one_page_summary.md
- docs/eag_dzg/external_pdf_onepager_draft.md
- docs/eag_dzg/customer_poc_acceptance_boundary.md
Partner-facing
- docs/eag_dzg/partner_facing_one_page_summary.md
- docs/eag_dzg/security_implementation_partner_pack.md
- docs/eag_dzg/secondary_use_partner_license_boundary_draft.md
Boundary / closeout
- docs/eag_dzg/customer_poc_lane_closeout.md
- docs/eag_dzg/public_lane_final_closeout.md