Independent implementations will determine whether OJCP provides a practical interoperable alternative to career-page scraping and browser automation for job-search agents.

state: expiredheat: lowuncertainty: highknownscott: lowagent-protocols browser-agents structured-dataOJCP

What is this?

OJCP is presented as an open protocol for agent-consumable job feeds, with a repository whose initial commit published a v0.1 proposal titled “A Standard for Agent-Consumable Job Feeds.” The supplied material does not identify its creators or establish any independent implementations, adoption, or interoperability testing. The broader snippets describe scraping and browser automation as existing job-data approaches with tradeoffs in reliability, scale, sessions, authentication, and maintenance, but they do not show that OJCP is yet a practical alternative to either.

Why it matters to Scott

Agent Addressability already argues for machine-readable delegation surfaces instead of scraping or UI impersonation, while Scott’s browser-automation work treats agentic scraping as a costly fallback. OJCP v0.1 is another instance of that established position, but without independent implementations or adoption it does not yet affect his builds or add evidence that the proposed job-feed standard is practical.

ip:framework.agent-addressabilitydev:concept.agentic-browser-scrapingradar:concept.agent-interoperabilityradar:concept.browser-agentsradar:microsoft-agent-host-protocol-adoption

queries asked of Scott's wikis

structured job feeds vs browser automation
open protocols for agent-consumable data
agent interoperability and protocol adoption
structured data replacing web scraping
MCP and domain-specific agent protocols
cold-start strategy for two-sided data standards

Measured heat

no measured readings yet — the hourly heat pass fills this in

How the heat travelled

no chain yet — the hourly chain pass fills this in

Evidence (3) — ⭐ canonical anchor

source	object	author	score	comments
🟧 hn	Show HN: OJCP – an open protocol for agent-consumable job data	fraywing	37	10
🟧 echo.github ⭐	The repository’s initial commit published the OJCP v0.1 proposal. It identifies itself as “A Standard for Agent-Consumable Job Feeds,” credi	Austin Anderson	—	—
🟧 hn	Show HN: Job listings scraped daily from 8k company career pages	omar_bouaziz	1	0

Interpretation history

2026-08-22T17:27:39Z
Repeated checks have produced no independent implementation, provider adoption, or interoperability result, so OJCP no longer merits active monitoring. This is dormancy rather than disproof and can be reopened by a concrete deployment or compatibility test.
2026-08-20T16:39:28Z
Minor score increases without new discussion are passive amplification, not evidence of implementation or adoption. OJCP remains an unvalidated creator-controlled proposal and should be revisited only on an independent deployment or interoperability result.
2026-08-18T15:41:15Z
The staleness check found no independent implementation, provider adoption, or interoperability result, so the evidence remains unchanged rather than weakened. OJCP is still an unvalidated creator-controlled proposal best revisited on an adoption event, not a short cadence.
2026-08-16T15:36:26Z
The 8,000-page scraper makes the incumbent workaround’s scale concrete and underscores OJCP’s potential value, but it also sharpens the adoption hurdle rather than validating the protocol. No independent OJCP implementation, provider adoption, or interoperability result has emerged.
2026-08-16T15:22:57Z
evidence attached: hn.story.49320835 — A live scraper covering 8,000 career pages provides concrete baseline context for judging whether OJCP can replace browser automation and scraping.
2026-08-15T20:30:37Z
The added discussion is repetitive amplification around standardization and recruiting rather than evidence of independent implementation, provider adoption, or interoperability. OJCP remains a creator-controlled proposal whose practicality against scraping and browser automation is untested.
2026-08-13T19:44:33Z
The refreshed discussion adds only generic reactions to standardization and recruiting, not an independent implementation, provider adoption, or interoperability result. OJCP therefore remains a plausible creator-controlled proposal rather than evidence of a practical alternative to scraping.
2026-08-12T16:50:59Z
No independent implementation, provider adoption, or interoperability result has appeared; the evidence remains limited to the creator-controlled v0.1 artifact. The case still merits slow monitoring but has not advanced beyond a plausible protocol proposal.
2026-08-12T16:44:07Z
grounded: known/low — Agent Addressability already argues for machine-readable delegation surfaces instead of scraping or UI impersonation, while Scott’s browser-automation work trea
2026-08-12T16:41:01Z
origin walked (codex/luna, conf 0.97): anchor hn.story.49273922 -> echo.github.f7dd3d5f9f by Austin Anderson
2026-08-12T16:39:50Z
case created — OJCP is a usable first-party protocol artifact with schemas, discovery machinery, MCP tools, and a live endpoint.

Decision trace

08-23 03:27expireRepeated checks have produced no independent implementation, provider adoption, or interoperability result, so OJCP no longer merits active monitoring. This is dormancy rather than disproof and can be
08-23 03:27alert_silentThe only trigger is another staleness check, with no consequential new evidence; Scott should not be interrupted unless an independent implementation, provider deployment, or interoperability result a
08-23 03:27alert_routeThe only trigger is another staleness check, with no consequential new evidence; Scott should not be interrupted unless an independent implementation, provider deployment, or interoperability result a
08-21 02:39repriceMinor score increases without new discussion are passive amplification, not evidence of implementation or adoption. OJCP remains an unvalidated creator-controlled proposal and should be revisited only
08-21 02:39alert_silentNo consequential new fact occurred; engagement-only movement does not justify interrupting Scott before a normal briefing.
08-21 02:39alert_routeNo consequential new fact occurred; engagement-only movement does not justify interrupting Scott before a normal briefing.
08-19 01:41repriceThe staleness check found no independent implementation, provider adoption, or interoperability result, so the evidence remains unchanged rather than weakened. OJCP is still an unvalidated creator-con
08-19 01:41alert_silentNo consequential new fact occurred; elapsed silence does not warrant an alert, and Scott can wait for an independent implementation, provider deployment, or interoperability test.
08-19 01:41alert_routeNo consequential new fact occurred; elapsed silence does not warrant an alert, and Scott can wait for an independent implementation, provider deployment, or interoperability test.
08-17 01:36repriceThe 8,000-page scraper makes the incumbent workaround’s scale concrete and underscores OJCP’s potential value, but it also sharpens the adoption hurdle rather than validating the protocol. No independ
08-17 01:36alert_silentThe scraper is useful baseline context, not evidence that OJCP works or is being adopted; Scott can wait for an independent implementation, provider deployment, or interoperability test.
08-17 01:36alert_routeThe scraper is useful baseline context, not evidence that OJCP works or is being adopted; Scott can wait for an independent implementation, provider deployment, or interoperability test.
08-17 01:23alert_silentA project scraping 8,000 career pages illustrates the scale of the fallback OJCP seeks to replace, but it is not an independent OJCP implementation or adoption signal and provides no new evidence that
08-17 01:23alert_routeA project scraping 8,000 career pages illustrates the scale of the fallback OJCP seeks to replace, but it is not an independent OJCP implementation or adoption signal and provides no new evidence that
08-17 01:22attachA live scraper covering 8,000 career pages provides concrete baseline context for judging whether OJCP can replace browser automation and scraping.
08-17 01:22propose_attachA live scraper covering 8,000 career pages provides concrete baseline context for judging whether OJCP can replace browser automation and scraping.
08-16 06:30repriceThe added discussion is repetitive amplification around standardization and recruiting rather than evidence of independent implementation, provider adoption, or interoperability. OJCP remains a creato
08-16 06:30alert_silentEngagement increased, but no consequential new fact changed the case or Scott’s decisions; it can wait for an independent implementation, provider deployment, or interoperability result.
08-16 06:30alert_routeEngagement increased, but no consequential new fact changed the case or Scott’s decisions; it can wait for an independent implementation, provider deployment, or interoperability result.
08-14 05:44repriceThe refreshed discussion adds only generic reactions to standardization and recruiting, not an independent implementation, provider adoption, or interoperability result. OJCP therefore remains a plaus
08-14 05:44alert_silentNo consequential new fact emerged; refreshed comments do not change the protocol’s maturity or implications for Scott, so this can wait for evidence of independent adoption or testing.
08-14 05:44alert_routeNo consequential new fact emerged; refreshed comments do not change the protocol’s maturity or implications for Scott, so this can wait for evidence of independent adoption or testing.
08-14 05:21sensor_dirtycomment_update
08-13 02:50repriceNo independent implementation, provider adoption, or interoperability result has appeared; the evidence remains limited to the creator-controlled v0.1 artifact. The case still merits slow monitoring b
08-13 02:50alert_silentThis reobservation adds no consequential evidence beyond the already-assessed launch artifact, so the next briefing would not be late.
08-13 02:50alert_routeThis reobservation adds no consequential evidence beyond the already-assessed launch artifact, so the next briefing would not be late.
08-13 02:45alert_silentOJCP v0.1 and its live MCP playground establish that the proposal exists, but this is still a creator-controlled implementation with no independent provider, agent integration, or adoption evidence. I
08-13 02:45alert_routeOJCP v0.1 and its live MCP playground establish that the proposal exists, but this is still a creator-controlled implementation with no independent provider, agent integration, or adoption evidence. I
08-13 02:44groundAgent Addressability already argues for machine-readable delegation surfaces instead of scraping or UI impersonation, while Scott’s browser-automation work treats agentic scraping as a costly fallback
08-13 02:41promote_anchororigin walk conf 0.97
08-13 02:39createOJCP is a usable first-party protocol artifact with schemas, discovery machinery, MCP tools, and a live endpoint.