{"slug":"oip-system-github","title":"OIP system: GitHub","body":"## GitHub\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: `api`. Capabilities: `6`. Machine system map: [/api/dispatch?map=GITHUB&format=markdown](https://miscsubjects.com/api/dispatch?map=GITHUB&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### GITHUB\nInvokable OIP capability.\nHuman article: [/a/oip-capability-github](https://miscsubjects.com/a/oip-capability-github). Machine doc: [?key=GITHUB&format=markdown](https://miscsubjects.com/api/dispatch?key=GITHUB&format=markdown). Invocation history: [/api/invocations?object_id=GITHUB](https://miscsubjects.com/api/invocations?object_id=GITHUB).\n\n### GITHUB_LIST_ISSUES\nList GitHub issues in massoumicyrus/miscsubjects-pages through the GitHub API.\nUse when: list/show open GitHub issues, audit the issue backlog, inspect Grok-created issues.\nArguments: `state | labels | limit`.\nHuman article: [/a/oip-capability-github-list-issues](https://miscsubjects.com/a/oip-capability-github-list-issues). Machine doc: [?key=GITHUB_LIST_ISSUES&format=markdown](https://miscsubjects.com/api/dispatch?key=GITHUB_LIST_ISSUES&format=markdown). Invocation history: [/api/invocations?object_id=GITHUB_LIST_ISSUES](https://miscsubjects.com/api/invocations?object_id=GITHUB_LIST_ISSUES).\n\n### GITHUB_GET_ISSUE\nRead one GitHub issue by number from massoumicyrus/miscsubjects-pages.\nUse when: inspect an issue body, labels, title, state, and URL before acting.\nArguments: `issue_number`.\nHuman article: [/a/oip-capability-github-get-issue](https://miscsubjects.com/a/oip-capability-github-get-issue). Machine doc: [?key=GITHUB_GET_ISSUE&format=markdown](https://miscsubjects.com/api/dispatch?key=GITHUB_GET_ISSUE&format=markdown). Invocation history: [/api/invocations?object_id=GITHUB_GET_ISSUE](https://miscsubjects.com/api/invocations?object_id=GITHUB_GET_ISSUE).\n\n### GITHUB_ADD_ISSUE_COMMENT\nPost a comment to a GitHub issue through the GitHub API. This is the canonical URL-only comment path.\nUse when: comment on GitHub, reply to an issue, post proof/receipt on an issue.\nArguments: `issue_number | comment_body`.\nHuman article: [/a/oip-capability-github-add-issue-comment](https://miscsubjects.com/a/oip-capability-github-add-issue-comment). Machine doc: [?key=GITHUB_ADD_ISSUE_COMMENT&format=markdown](https://miscsubjects.com/api/dispatch?key=GITHUB_ADD_ISSUE_COMMENT&format=markdown). Invocation history: [/api/invocations?object_id=GITHUB_ADD_ISSUE_COMMENT](https://miscsubjects.com/api/invocations?object_id=GITHUB_ADD_ISSUE_COMMENT).\n\n### GITHUB_CREATE_ISSUE\nCreate a GitHub issue through the GitHub API.\nUse when: file a build work item, proposal, bug, or proof ticket from OIP.\nArguments: `title | body | labels_csv`.\nHuman article: [/a/oip-capability-github-create-issue](https://miscsubjects.com/a/oip-capability-github-create-issue). Machine doc: [?key=GITHUB_CREATE_ISSUE&format=markdown](https://miscsubjects.com/api/dispatch?key=GITHUB_CREATE_ISSUE&format=markdown). Invocation history: [/api/invocations?object_id=GITHUB_CREATE_ISSUE](https://miscsubjects.com/api/invocations?object_id=GITHUB_CREATE_ISSUE).\n\n### GITHUB_CLOSE_ISSUE\nClose a GitHub issue and add a closing comment.\nUse when: finish/resolve/close a GitHub issue from the build.\nArguments: `number | reason`.\nHuman article: [/a/oip-capability-github-close-issue](https://miscsubjects.com/a/oip-capability-github-close-issue). Machine doc: [?key=GITHUB_CLOSE_ISSUE&format=markdown](https://miscsubjects.com/api/dispatch?key=GITHUB_CLOSE_ISSUE&format=markdown). Invocation history: [/api/invocations?object_id=GITHUB_CLOSE_ISSUE](https://miscsubjects.com/api/invocations?object_id=GITHUB_CLOSE_ISSUE).\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"}}