Evidence review · protocol
OP — Object Protocol
OP — Object Protocol
OP is the common object grammar for discovery, bounded authority, invocation, receipts, replay, repair, provenance, and feedback.
OP was previously named OIP, Object Invocation Protocol. Existing OIP route names, code symbols, directory keys, receipt ids, and federation identifiers remain compatibility aliases. New human and machine roots use OP.
Six invariants
- A capability is an object with a readable contract.
- Authority is an object scope enforced at the dispatch boundary.
- Execution is an object invocation.
- Proof is an invocation receipt.
- Correction is replay or repair linked to the original receipt.
- Feedback is a typed contribution linked to the object it evaluates.
Roots
Human OP root: https://miscsubjects.com/op
Machine OP root: https://miscsubjects.com/api/op
OPOS root: https://miscsubjects.com/opos
Dispatch: https://miscsubjects.com/api/dispatch
Registry: https://miscsubjects.com/api/dispatch?registry=1
Ask this article · 2 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.
For my medical situation, what can you answer from your catalogue about OP — Object Protocol — and what would you need me to tell you first?
ask op condition gaps · paste includes §SELF
What good and bad outcomes are documented for OP — Object Protocol (studies vs anecdotes)?
ask op good bad experiences · paste includes §SELF