Ladder / MATCHA project index

October 5 — existing data is part of MATCHA

Pablo clarified: “i want it directly connected no need to be calling it as a separate thing.” The earlier separate Connect RoboRun prompt was rejected. Existing available footage now loads automatically into the hosted library, including on a fresh browser, with no branded setup banner or separate source activation. Datasets lists footage already available alongside the Hub catalog. Screening opens inside MATCHA from Datasets or Tools without a connection prerequisite. Provider identity, source receipts and offsets remain in the underlying evidence; this changes product flow, not access scope.

Implemented locally in 5aca1ba on simplify-delivery, following baseline c27f704. Fresh Chrome and the in-app browser displayed 85 clips automatically (83 available excerpts plus two bundled clips). Screening displayed 132,576 records. A selected excerpt and its 83-clip source scope survived reload without duplication. Seventeen adapter tests plus JavaScript, build, HTML-ID and diff checks passed. Failed refresh keeps saved clips available with a plain retry action. Evidence: the operator's October 5 correction, the local commit and docs/FOCUSED_LIBRARY.md; upstream EgoVerse receipts establish the unchanged available-media scope. No production publication or remote push occurred.

Ladder / MATCHA project index

October 5 — current operator direction

MATCHA is a dataset curation platform: discover footage → process → inspect objects/actions → collect → export. Pablo rejected the overloaded three-panel screen and asked to reuse Ladder/Delivery datasets plus accessible Hugging Face data. He explicitly rejected demo-purpose and promotional provenance boilerplate in the main product UI. Source/model details stay in inspectors and settings.

Earlier checkpoint: implemented and tested locally in commit c27f704 on simplify-delivery. The original live Vercel release remains unchanged at this checkpoint. Automatic approval review rejected the attempted private branch push because the repository forbids automatic submission/deployment. Approval for backup + existing-site publication has been requested; neither is claimed complete.

Current work

• MATCHA Studio — dataset curation platform: focused interface, Delivery/HF catalog, pipeline reports, timed action labeling, verification and publication state.
• Current synthesis: accepted direction and actual platform scope.
• Processing: frame/object/action evidence and durable inference-worker next step.
• Checks and embeddings: evidence semantics and prior implementation.
• Assets and model research: earlier repository/model audits with their original evidence limits.
• Source provenance and part 2: immutable imported research references.

This is Pablo's existing Ladder/MATCHA project workspace, separate from CRM and unrelated projects. The earlier planning-only and VAST-event constraints are dated history; latest operator directions govern current standalone product work. Earlier measured results and failed checks remain in the linked history.

Preserved history

Exact prior revision 35 retains the earlier directions, results, failures and references. The October 5 direction above supersedes the always-visible three-panel requirement; prior evidence remains dated evidence.