{"_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-lbl","title":"OIP system: LBL","body":"## LBL\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: `7`. Machine system map: [/api/dispatch?map=LBL&format=markdown](https://miscsubjects.com/api/dispatch?map=LBL&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### LBL_GET\nGET a path on the loop data platform (api.lbl.fyi, the loop-api-worker). Arg: the path after the host, e.g. \"v4/health\" or \"2chat/contacts\" (slashes preserved). Returns raw JSON + status. fyi. If a path needs auth (401), use WEB_FETCH with the right header, or ask the owner for the token\nUse when: the owner asks for data from the loop platform / lbl\nArguments: `$1`.\nHuman article: [/a/oip-capability-lbl-get](https://miscsubjects.com/a/oip-capability-lbl-get). Machine doc: [?key=LBL_GET&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_GET&format=markdown). Invocation history: [/api/invocations?object_id=LBL_GET](https://miscsubjects.com/api/invocations?object_id=LBL_GET).\n\n### LBL_POST\nPOST to the loop data platform (api.lbl.fyi). For custom auth headers use WEB_FETCH\nUse when: trigger/send something on the loop platform\nArguments: `path|json_body`.\nHuman article: [/a/oip-capability-lbl-post](https://miscsubjects.com/a/oip-capability-lbl-post). Machine doc: [?key=LBL_POST&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_POST&format=markdown). Invocation history: [/api/invocations?object_id=LBL_POST](https://miscsubjects.com/api/invocations?object_id=LBL_POST).\n\n### LBL_VIEWER_GET\nGET lbl.fyi viewer path. Uses LBL_VIEWER_PASS.\nHuman article: [/a/oip-capability-lbl-viewer-get](https://miscsubjects.com/a/oip-capability-lbl-viewer-get). Machine doc: [?key=LBL_VIEWER_GET&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_VIEWER_GET&format=markdown). Invocation history: [/api/invocations?object_id=LBL_VIEWER_GET](https://miscsubjects.com/api/invocations?object_id=LBL_VIEWER_GET).\n\n### LBL_DAILY_EMAIL\nCompose and send the LBL nightly team report — a narrated read of yesterday for Loop Bio Labs, then each source speaking for itself: BigCommerce (store truth), Triple Whale (ad attribution with honest per-channel ROAS), Klaviyo (owned channels). Data is lbl.fyi's live /v1/today; a failed source reads \"unavailable\", never zero.\nUse when: the nightly LBL automation fires; or the owner asks to send/preview the LBL daily report now.\nArguments: `mode. blank = send to settings.lbl_daily_recipients (owner-only until he approves the team format). dry = compose only, no send.`.\nHuman article: [/a/oip-capability-lbl-daily-email](https://miscsubjects.com/a/oip-capability-lbl-daily-email). Machine doc: [?key=LBL_DAILY_EMAIL&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_DAILY_EMAIL&format=markdown). Invocation history: [/api/invocations?object_id=LBL_DAILY_EMAIL](https://miscsubjects.com/api/invocations?object_id=LBL_DAILY_EMAIL).\n\n### LBL_REPORT_EMAIL\nCompose and send an LBL commercial report for Loop Bio Labs. Three templates off one design: daily (yesterday against the day before), weekly (the last complete Monday-Sunday against the week before), monthly (month-to-date against the same day-count of last month; on the 1st, the closed month against the whole month before it). Every template opens with eight numbers - revenue, ad spend, ROAS, attributed revenue, new customers, existing customers, orders, average order - each carrying its change against a named comparison window. The monthly also carries the Meta new-customer acquisition tren\nUse when: the daily, weekly or monthly LBL automation fires; or the owner asks to send or preview an LBL report now.\nArguments: `kind | mode`.\nHuman article: [/a/oip-capability-lbl-report-email](https://miscsubjects.com/a/oip-capability-lbl-report-email). Machine doc: [?key=LBL_REPORT_EMAIL&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_REPORT_EMAIL&format=markdown). Invocation history: [/api/invocations?object_id=LBL_REPORT_EMAIL](https://miscsubjects.com/api/invocations?object_id=LBL_REPORT_EMAIL).\n\n### LBL_ANSWER\nInvokable OIP capability.\nHuman article: [/a/oip-capability-lbl-answer](https://miscsubjects.com/a/oip-capability-lbl-answer). Machine doc: [?key=LBL_ANSWER&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_ANSWER&format=markdown). Invocation history: [/api/invocations?object_id=LBL_ANSWER](https://miscsubjects.com/api/invocations?object_id=LBL_ANSWER).\n\n### LBL_ASK\nAnswer a question about Loop Bio Labs commercial performance - revenue, orders, average order, ad spend, ROAS, attributed revenue, new versus returning customers, email and SMS revenue - for yesterday, the last complete week, this month so far, or last calendar month. The answer is built only from live numbers that have already passed the plausibility review; a figure that failed it is handed to the model as unavailable, so the answer cannot contain an invented or discredited number.\nUse when: any question about how the store or the business is doing. Revenue, sales, orders, spend, ROAS, return on ad spend, new customers, repeat customers, email revenue, SMS revenue, how was yesterday, how is the month going, are we up or down. Use this instead of guessing from memory - it reads live data every time.\nArguments: `$1 = the question in plain English.`.\nHuman article: [/a/oip-capability-lbl-ask](https://miscsubjects.com/a/oip-capability-lbl-ask). Machine doc: [?key=LBL_ASK&format=markdown](https://miscsubjects.com/api/dispatch?key=LBL_ASK&format=markdown). Invocation history: [/api/invocations?object_id=LBL_ASK](https://miscsubjects.com/api/invocations?object_id=LBL_ASK).\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"}}