{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"slug":"oip-system-bridge","title":"OIP system: BRIDGE","body":"## BRIDGE\n\nA generated article for one OIP shelf. It lists every operation in this API/CLI/MCP/device/model/core subsystem, links each leaf article, and gives the ledger path for proof.\n\nThis page is the operating article for one build subsystem. It is generated from live directory rows. If a task belongs to this subsystem, scan the operations below, open the matching capability article, run only the exact object named there, and verify by receipt.\n\nKind: `core`. Capabilities: `5`. Machine system map: [/api/dispatch?map=BRIDGE&format=markdown](https://miscsubjects.com/api/dispatch?map=BRIDGE&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### BRIDGE_REGISTER\nTurn any controllable surface into a durable, dispatchable object. controller = browser (a site or web app, driven by Playwright over a persistent session) | surface (any of the 8,764 Apple-surface verbs: apps, clicks, the phone) | adspower (your own AdsPower profile) | phone. Then drive it with its act door and record/compile flows into BRIDGE_* capabilities.\nUse when: you want a site/app/session/device to become one callable capability\nArguments: `$1 = name | $2 = controller (browser|surface|adspower|phone) | $3 = surface (site or app)`.\nHuman article: [/a/oip-capability-bridge-register](https://miscsubjects.com/a/oip-capability-bridge-register). Machine doc: [?key=BRIDGE_REGISTER&format=markdown](https://miscsubjects.com/api/dispatch?key=BRIDGE_REGISTER&format=markdown). Invocation history: [/api/invocations?object_id=BRIDGE_REGISTER](https://miscsubjects.com/api/invocations?object_id=BRIDGE_REGISTER).\n\n### BRIDGE_CONTROLLERS\nMeasured live: browser (Playwright), adspower (your AdsPower app), surface (the Apple-surface executor), phone. Read before registering a bridge that needs a particular controller.\nUse when: check what can be driven before you build a bridge\nArguments: `none`.\nHuman article: [/a/oip-capability-bridge-controllers](https://miscsubjects.com/a/oip-capability-bridge-controllers). Machine doc: [?key=BRIDGE_CONTROLLERS&format=markdown](https://miscsubjects.com/api/dispatch?key=BRIDGE_CONTROLLERS&format=markdown). Invocation history: [/api/invocations?object_id=BRIDGE_CONTROLLERS](https://miscsubjects.com/api/invocations?object_id=BRIDGE_CONTROLLERS).\n\n### BRIDGE_DEMO_FORM\nFill the demo form with a name — replays a recorded flow (2 steps) on bridge br_0l312x461k4s (browser, httpbin.org) through POST /api/bridges/br_0l312x461k4s/flows/flw_6s321c611c1n/replay.\nUse when: you need to fill the demo form with a name\nArguments: `$1 = params JSON (name)`.\nHuman article: [/a/oip-capability-bridge-demo-form](https://miscsubjects.com/a/oip-capability-bridge-demo-form). Machine doc: [?key=BRIDGE_DEMO_FORM&format=markdown](https://miscsubjects.com/api/dispatch?key=BRIDGE_DEMO_FORM&format=markdown). Invocation history: [/api/invocations?object_id=BRIDGE_DEMO_FORM](https://miscsubjects.com/api/invocations?object_id=BRIDGE_DEMO_FORM).\n\n### BRIDGE_WIKI_LOOKUP\nLook up any topic on Wikipedia and return the page — replays a recorded flow (5 steps) on bridge br_62442s1v6p66 (browser, en.wikipedia.org) through POST /api/bridges/br_62442s1v6p66/flows/flw_3t584l374n1a/replay.\nUse when: you need to look up any topic on wikipedia and return the page\nArguments: `$1 = params JSON (topic)`.\nHuman article: [/a/oip-capability-bridge-wiki-lookup](https://miscsubjects.com/a/oip-capability-bridge-wiki-lookup). Machine doc: [?key=BRIDGE_WIKI_LOOKUP&format=markdown](https://miscsubjects.com/api/dispatch?key=BRIDGE_WIKI_LOOKUP&format=markdown). Invocation history: [/api/invocations?object_id=BRIDGE_WIKI_LOOKUP](https://miscsubjects.com/api/invocations?object_id=BRIDGE_WIKI_LOOKUP).\n\n### BRIDGE_ACT\nRuns one step on a bridge's controller. Browser steps: goto (url), click (selector or text), fill (selector, value), type (selector, text), press (text = the key), wait (selector), screenshot, snapshot (title, visible text, links, form fields). The bridge id comes from BRIDGE_REGISTER. Runs on the tenant's own device when one is registered, otherwise on the build's endpoint. Receipted.\nUse when: you want to look at or act on a site or app through a bridge right now (record→compile for anything you will repeat)\nArguments: `$1 = bridge id (br_…), $2 = action, $3 = url (goto), $4 = selector, $5 = value (fill), $6 = text (click text, type text, press key)`.\nHuman article: [/a/oip-capability-bridge-act](https://miscsubjects.com/a/oip-capability-bridge-act). Machine doc: [?key=BRIDGE_ACT&format=markdown](https://miscsubjects.com/api/dispatch?key=BRIDGE_ACT&format=markdown). Invocation history: [/api/invocations?object_id=BRIDGE_ACT](https://miscsubjects.com/api/invocations?object_id=BRIDGE_ACT).\n","register":"oip_protocol","tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","system"],"style":{"accent":"#16324f","measure":860},"claims":[{"id":"oip-c1","tier":"system","text":"The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.","who_claims":"system/oip_articles","source_ids":["oip-s3","oip-s4"]},{"id":"oip-c2","tier":"system","text":"The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.","who_claims":"system/oip_articles","source_ids":["oip-s1"]},{"id":"oip-c3","tier":"system","text":"Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s3"]},{"id":"oip-c4","tier":"system","text":"Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.","who_claims":"system/oip_articles","source_ids":["oip-s2"]},{"id":"oip-c5","tier":"system","text":"OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.","who_claims":"system/oip_articles","source_ids":["oip-s2","oip-s5"]}],"sources":[{"id":"oip-s1","type":"protocol","title":"BUILD_SPEC object invocation path","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","summary":"Defines directory rows, dispatch, ledger, and the escalation path for changing the build.","quote":"Run anything: POST https://miscsubjects.com/api/dispatch {key, body}","claim_ids":["oip-c2"],"link_status":"ok","hash":"oipbuildspec0001"},{"id":"oip-s2","type":"protocol","title":"Object Invocation Protocol spec","url":"https://miscsubjects.com/api/file/docs/OIP.md","summary":"Defines OIP surfaces, invariant loop, receipt/replay/repair, and invocation envelopes.","quote":"identify, explain, invoke, ledger, yield","claim_ids":["oip-c3","oip-c4","oip-c5"],"link_status":"ok","hash":"oipspec00000002"},{"id":"oip-s3","type":"protocol","title":"Live OIP capability tree","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","summary":"Public recursive capability tree.","quote":"root > shelf > system article > capability article > receipt","claim_ids":["oip-c1","oip-c3"],"link_status":"ok","hash":"oipmap0000000002"},{"id":"oip-s4","type":"protocol","title":"Directory row documentation","url":"https://miscsubjects.com/api/dispatch?key=OIP_TREE&format=markdown","summary":"Capability articles are generated from live rows.","quote":"Machine Contract","claim_ids":["oip-c1"],"link_status":"ok","hash":"oiprow0000000003"},{"id":"oip-s5","type":"protocol","title":"Invocation ledger","url":"https://miscsubjects.com/api/invocations","summary":"Append-only invocation records and receipt links.","quote":"invocations","claim_ids":["oip-c5"],"link_status":"ok","hash":"oipinvocations0005"}],"prov":{"model":"system/oip_articles","action":"generate"}}