EGXO Household Egocentric Video Evaluation v2.0.0

Technical summary

Status: PASS. Release v2.0.0 contains 89 H.264 video-only files totaling 9.999995 hours. Audio, data streams, chapters, source metadata, source filenames, and contributor identifiers are not distributed.

Source: EGXO v2.0.0 release verificationTable: release_metrics

Select verified release runtime, file, task-family, and checksum metrics.

SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics

Runtime

Verified runtime of the exact replacement release.

Verified runtime of the exact replacement release.Source: EGXO v2.0.0 release verificationTable: release_metrics

Select verified release runtime, file, task-family, and checksum metrics.

SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics

Video files

Video-only files in the verified release.

Video-only files in the verified release.Source: EGXO v2.0.0 release verificationTable: release_metrics

Select verified release runtime, file, task-family, and checksum metrics.

SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics

Task families

Distinct task families represented in the release.

Distinct task families represented in the release.Source: EGXO v2.0.0 release verificationTable: release_metrics

Select verified release runtime, file, task-family, and checksum metrics.

SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics

Checksum matches

Release files whose SHA-256 matches the manifest.

Release files whose SHA-256 matches the manifest.Source: EGXO v2.0.0 release verificationTable: release_metrics

Select verified release runtime, file, task-family, and checksum metrics.

SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics

The released ten hours are the end of a fail-closed curation funnel

The chart compares runtime retained at each review stage. The release is not a raw export: only explicit privacy-approved candidates feed the exact ten-hour package. File counts are available in the chart tooltip because clip duration varies by stage.

Source: EGXO v2.0.0 privacy-review ledgersTable: privacy_funnel

Select the aggregate file count and runtime retained at each privacy-review stage.

SELECT stage, files, hours FROM privacy_funnel ORDER BY review_order

Curation funnel by runtime

Source: EGXO v2.0.0 privacy-review ledgersTable: privacy_funnel

Select the aggregate file count and runtime retained at each privacy-review stage.

SELECT stage, files, hours FROM privacy_funnel ORDER BY review_order

Curation funnel by runtime data
Review stage	Hours	Files
Unique source videos	105.18	1,921
Provisional lower-risk candidates	30.1	398
Dense-clear reserve pool	14.05	158
Privacy-approved candidates	13.01	145
Exact release	10	89

Scope, data, and definitions

The July 31, 2026 source snapshot contained 1921 unique video objects totaling 105.180562 hours across 79 source task families.

Source: EGXO verified source snapshotTable: source_snapshot

Read the verified aggregate source snapshot.

SELECT unique_video_objects, unique_duration_hours, task_families FROM source_snapshot

Review-state definition

A privacy-approved candidate is a source clip with successful media validation, calibrated dense face screening, visible-text and QR screening, independent Vision screening, reviewed alert evidence, reviewed contact sheets, and an explicit approval row.

Source: EGXO v2.0.0 privacy-review ledgersTable: privacy_funnel

Select the aggregate file count and runtime retained at each privacy-review stage.

SELECT stage, files, hours FROM privacy_funnel ORDER BY review_order

Methodology

Byte-verify and probe every unique source object.
Exclude higher-risk task families before automatic selection.
Run dense YuNet proposals with macOS Vision confirmation.
Select a diverse reserve pool from dense-clear candidates and run native-frame YuNet with macOS Vision confirmation.
Run visible-text, QR, and independent Vision screening.
Review every alert frame and interval contact sheets; exclude ambiguous clips.
Select an exact ten hours from approved candidates with task diversity.
Re-encode video only, strip source metadata and non-video streams, then verify checksums, streams, duration, names, and manifest fields.

Face-screen calibration: 5.0 FPS at YuNet threshold 0.65 for the dense pass, followed by native-frame screening at threshold 0.85.

Source: EGXO v2.0.0 privacy-review ledgersTable: privacy_funnel

Select the aggregate file count and runtime retained at each privacy-review stage.

SELECT stage, files, hours FROM privacy_funnel ORDER BY review_order

The release gate has no unresolved verification failures

Every fail-closed check below must be zero before publication. Sorting by count keeps any future failure at the top of the table instead of burying it in a green-looking summary.

Source: EGXO v2.0.0 release verificationTable: release_metrics

Select verified release runtime, file, task-family, and checksum metrics.

SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics

Fail-closed source and release checks

Source: EGXO v2.0.0 fail-closed check summaryTable: source_checks

Select aggregate source, release, and privacy-gate failure counts.

SELECT check, count FROM source_checks ORDER BY count DESC

Fail-closed source and release checks
Check	Count
Download failures	0
Media probe errors	0
Byte-size mismatches	0
Non-single-video-stream files	0
Released files with sensitive metadata keys	0
Release verification failures	0
Privacy-gate failures	0

Limitations and robustness

The procedures reduce privacy risk and found no unresolved face or visible-PII alert in approved release clips. Detector and sampled-review results do not prove the absence of every possible identifier. Suspected issues trigger withdrawal and re-review. Contact-sheet and alert-frame review was AI-assisted visual inspection by Codex, not an independent human privacy review. The package therefore remains controlled-access. A suspected issue triggers withdrawal and re-review rather than silent correction.

Source: EGXO v2.0.0 privacy-review ledgersTable: privacy_funnel

Select the aggregate file count and runtime retained at each privacy-review stage.

SELECT stage, files, hours FROM privacy_funnel ORDER BY review_order

Next steps and further questions

Replace the withdrawn v1 package everywhere only after the v2 bytes and public metadata are verified.
Record recipient/version mappings so an affected release can be recalled.
Re-run the full privacy gate whenever source clips, transformations, or release selections change.
Evaluate whether future releases need task-specific OCR models or jurisdiction-specific identifier rules.

Sources

EGXO verified source snapshotrestricted aggregate source record
Read the verified aggregate source snapshot.
SQL query
```
SELECT unique_video_objects, unique_duration_hours, task_families FROM source_snapshot
```
EGXO v2.0.0 privacy-review ledgersrestricted privacy-review workspace
Select the aggregate file count and runtime retained at each privacy-review stage.
SQL query
```
SELECT stage, files, hours FROM privacy_funnel ORDER BY review_order
```
EGXO v2.0.0 release verificationrelease-verification.json
Select verified release runtime, file, task-family, and checksum metrics.
SQL query
```
SELECT runtime_hours, video_files, task_families, checksum_matches FROM release_metrics
```
EGXO v2.0.0 fail-closed check summaryprivacy-qa.json
Select aggregate source, release, and privacy-gate failure counts.
SQL query
```
SELECT check, count FROM source_checks ORDER BY count DESC
```