{"_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-profile","title":"OIP system: PROFILE","body":"## PROFILE\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: `4`. Machine system map: [/api/dispatch?map=PROFILE&format=markdown](https://miscsubjects.com/api/dispatch?map=PROFILE&format=markdown). Root: [/a/oip](https://miscsubjects.com/a/oip).\n\n## Operations\n\n### PROFILE_NEW\nCreate a profile: the one durable object for a human, a model actor, a service, a device or a workflow. Customers, browser-model sessions and API agents live in this same table.\nUse when: a new human or actor needs a durable identity that capabilities, devices, identifiers and events can bind to.\nArguments: `$1 = kind|display|attrs_json (kind: human, model, service, device, workflow). Or JSON {kind, display, attrs, tags}.`.\nHuman article: [/a/oip-capability-profile-new](https://miscsubjects.com/a/oip-capability-profile-new). Machine doc: [?key=PROFILE_NEW&format=markdown](https://miscsubjects.com/api/dispatch?key=PROFILE_NEW&format=markdown). Invocation history: [/api/invocations?object_id=PROFILE_NEW](https://miscsubjects.com/api/invocations?object_id=PROFILE_NEW).\n\n### PROFILE_360\nOne profile, everything joined to it: devices and their trust, identifiers (masked), recent events, capability contexts bound to it, recent access decisions, and browser-model sessions acting as it.\nUse when: an agent authorised for a human asks about that human, or the owner inspects an actor; one call instead of five unrelated lookups.\nArguments: `$1 = profile_id, optionally profile_id|how_many_events.`.\nHuman article: [/a/oip-capability-profile-360](https://miscsubjects.com/a/oip-capability-profile-360). Machine doc: [?key=PROFILE_360&format=markdown](https://miscsubjects.com/api/dispatch?key=PROFILE_360&format=markdown). Invocation history: [/api/invocations?object_id=PROFILE_360](https://miscsubjects.com/api/invocations?object_id=PROFILE_360).\n\n### PROFILE_IDENTIFY\nJoin an identifier (phone, email, Stripe customer, BigCommerce customer, Klaviyo profile, Blooio contact) to a profile. Stored as a keyed hash plus a masked form; the raw value is never written anywhere.\nUse when: an SMS verification completes, a checkout identifies a customer, or a support thread resolves to a person.\nArguments: `$1 = profile_id|kind|value|source.`.\nHuman article: [/a/oip-capability-profile-identify](https://miscsubjects.com/a/oip-capability-profile-identify). Machine doc: [?key=PROFILE_IDENTIFY&format=markdown](https://miscsubjects.com/api/dispatch?key=PROFILE_IDENTIFY&format=markdown). Invocation history: [/api/invocations?object_id=PROFILE_IDENTIFY](https://miscsubjects.com/api/invocations?object_id=PROFILE_IDENTIFY).\n\n### PROFILE_EVENT\nAppend a first-party behavioural event to a profile: PAGE_VIEW, PRODUCT_VIEW, ADD_TO_CART, ORDER_CREATED, EXPERIMENT_EXPOSURE, or any named type, with device and session where known. External pixels are downstream of this row, never the source of truth.\nUse when: something happened that the customer graph should remember.\nArguments: `$1 = profile_id|EVENT_TYPE|payload_json. Or JSON {profile_id, device_id, session_id, event_type, payload, url, source}.`.\nHuman article: [/a/oip-capability-profile-event](https://miscsubjects.com/a/oip-capability-profile-event). Machine doc: [?key=PROFILE_EVENT&format=markdown](https://miscsubjects.com/api/dispatch?key=PROFILE_EVENT&format=markdown). Invocation history: [/api/invocations?object_id=PROFILE_EVENT](https://miscsubjects.com/api/invocations?object_id=PROFILE_EVENT).\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"}}