{"slug":"oip-what-is-tls","title":"TLS: The Foundation of Trust on the Wire","body":"TLS (Transport Layer Security) is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser, TLS is the machinery behind it. It turns an untrusted pipe—the public internet—into a trusted channel between two endpoints.\n\nWithout TLS, the internet is a postcard. Anyone between sender and receiver can read, alter, or replay traffic. TLS fixes this at the transport layer, which means applications get security for free. They send plaintext; TLS handles the rest.\n\nTLS matters to OIP because auditable trust requires encrypted channels. An open, deterministic protocol that publishes its rules but sends them over plaintext is self-defeating. TLS is the minimum viable envelope. You cannot build deterministic, auditable systems on a channel you do not control.\n\nTLS is a handshake, then a stream.\n\nThe Handshake:\n1. The client sends a ClientHello with supported cipher suites, a random nonce, and an optional SNI (Server Name Indication).\n2. The server responds with a ServerHello, picking the cipher suite, sending its own nonce, and delivering its certificate chain.\n3. The client verifies the certificate chain against its trust store. If the chain breaks, the handshake aborts.\n4. The client generates a pre-master secret, encrypts it with the server's public key, and sends it.\n5. Both sides derive the same session keys from the pre-master secret and the two nonces.\n6. The client sends a Finished message encrypted with the new session keys. The server verifies it.\n7. The server sends its own Finished. The client verifies it.\n8. The encrypted application data stream begins.\n\nThe handshake is asymmetric cryptography. The stream is symmetric. This is efficient: expensive operations happen once per session, then fast AES-GCM or ChaCha20-Poly1305 takes over.\n\nInputs:\n- A TCP connection.\n- A server hostname (for SNI and certificate validation).\n- A client trust store (root CAs).\n- Optional: client certificate, ALPN protocols, SNI.\n\nOutputs:\n- An encrypted, authenticated byte stream between two endpoints.\n- A verified identity chain for the server.\n- Optional: verified client identity.\n\nInvariants:\n- Data confidentiality: no intermediate can read the plaintext.\n- Data integrity: no intermediate can alter the stream without detection.\n- Replay resistance: old sessions cannot be replayed against the same keys.\n- Forward secrecy: if the server's long-term key is compromised later, past sessions remain secure (with ephemeral key exchange).\n\nFailure modes:\n- Certificate expired → handshake aborts.\n- Certificate hostname mismatch → handshake aborts.\n- Untrusted CA → handshake aborts.\n- Downgrade attack (client/server negotiate weak cipher) → modern implementations abort.\n\n1. Web Browsing (HTTPS)\nWhen you navigate to https://miscsubjects.com, your browser performs a TLS handshake with the server. The server's certificate is signed by a CA in your browser's trust store. The resulting AES-GCM stream protects every request and response. If an attacker intercepts the traffic, they see noise.\n\n2. API Authentication\nAn API key in an HTTP header is useless over HTTP. Over TLS, it is protected. The Authorization: Bearer <token> header travels inside the encrypted envelope. TLS is what makes token-based authentication practical.\n\n3. gRPC over TLS\ngRPC uses HTTP/2, which requires TLS for production deployments. The ALPN negotiation during the handshake selects h2. The certificate validates the service identity. Without TLS, gRPC falls back to plaintext, which is suitable only for local development.\n\n4. Database Connections\nPostgreSQL, MySQL, and MongoDB all support TLS-wrapped connections. The client verifies the server certificate. Some deployments also use client certificates for mutual authentication. The data at rest is encrypted by the database; TLS encrypts data in transit. Both are necessary.\n\n5. OIP Directory Communication\nWhen an OIP agent queries a directory row or sends a dispatch command, the payload traverses the internet. TLS wraps that traffic. Without it, the command plane is exposed. With it, the command plane is protected, auditable, and deterministic.\n\nCertificate pinning without a rotation plan.\nPinning hardcodes a certificate hash. When the certificate rotates, the client breaks. Plan for rotation, or do not pin.\n\nAccepting all certificates.\nDisabling certificate verification (curl -k, NODE_TLS_REJECT_UNAUTHORIZED=0) is a silent self-attack. You are encrypting traffic that an active attacker can intercept, modify, and re-sign. This is worse than plaintext because it looks safe.\n\nMissing SNI.\nModern hosting uses SNI to serve multiple certificates from one IP. If the client omits SNI, the server returns the wrong certificate, and the handshake fails.\n\nRelying on TLS alone for authentication.\nTLS authenticates the server. It does not authenticate the application user. You still need tokens, signatures, or session cookies. TLS is the pipe, not the gate.\n\nUsing obsolete TLS versions.\nTLS 1.0 and 1.1 are broken. TLS 1.2 is the minimum viable version. TLS 1.3 is preferred. It reduces handshake latency and removes vulnerable cipher suites.\n\nOIP is the Open Interface Protocol. It demands that systems be open (their rules are published), deterministic (the same input always produces the same output), and auditable (every action is traceable and verifiable).\n\nTLS serves all three:\n\n- Open: TLS is an open standard (RFC 8446). Its algorithms are public, peer-reviewed, and unpatented. There are no hidden backdoors by design—only mathematics.\n- Deterministic: Given the same handshake parameters, TLS produces the same key material. The protocol is state-machine driven. A deterministic system can model TLS behavior exactly.\n- Auditable: TLS sessions log cipher suites, certificates, and key exchange types. Certificate Transparency logs publish every issued certificate. A TLS-protected channel creates an auditable boundary: you can prove what crossed the wire and when.\n\nTLS is not the whole OIP security model. But it is the floor. Without it, there is no trustworthy channel. Without a trustworthy channel, there is no auditable protocol. Without an auditable protocol, there is no deterministic system worth trusting.\n\n## Connection to the Grain Philosophy\n\nThis protocol is part of the [Open Inventory Protocol](/a/philosophy) — a living system of self-describing voxels that serves the Grain philosophy. The OIP is the interface. The philosophy is the core.\n","hero":null,"images":[],"style":{},"tags":["oip","protocol"],"category":null,"model":"owner","ledger":{"href":"/api/articles/oip-what-is-tls/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"TLS (Transport Layer Security) is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser, TLS is the machinery behind it. It turns an untrusted pipe—the public internet—into a trusted channel between two endpoints.","tier":"system","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Contradictory evidence or counter-example."},{"id":"c2","text":"Without TLS, the internet is a postcard. Anyone between sender and receiver can read, alter, or replay traffic. TLS fixes this at the transport layer, which means applications get security for free. They send plaintext; TLS handles the rest.","tier":"system","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Contradictory evidence or counter-example."},{"id":"c3","text":"TLS matters to OIP because auditable trust requires encrypted channels. An open, deterministic protocol that publishes its rules but sends them over plaintext is self-defeating. TLS is the minimum viable envelope. You cannot build deterministic, auditable systems on a channel you do not control.","tier":"system","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Contradictory evidence or counter-example."}],"sources":[{"id":"s1","type":"adjacent","url":"https://miscsubjects.com/a/oip-what-is-tls","title":"TLS: The Foundation of Trust on the Wire","quote":"TLS (Transport Layer Security) is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser","summary":"Primary exposition of TLS: The Foundation of Trust on the Wire.","claim_ids":["c1","c2","c3"],"quality_score":0.9}],"reviews":[],"extra":{"corpus_map":{"series":"oip-what-is","hub":"philosophy","prev":"oip-what-is-cors","next":"oip-what-is-dns","position":4,"of":19},"normandy_v1":{"traversal":{"convergence_patterns":["C20"],"adjacent_sources":["shannon-1948"],"falsifier_surface":"A system where this concept is unnecessary or harmful.","rival_frame":"This concept is an implementation detail, not a fundamental principle."}}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":2,"contributions":[],"provenance":[{"ts":"2026-07-17T02:36:52.497Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-what-is-tls","response":"36 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"7958d90ce641e17237f0d02700865cada0cd41b45aa068cbcb9d04a9af0ec05f"}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"owner":1},"head":"7958d90ce641e17237f0d02700865cada0cd41b45aa068cbcb9d04a9af0ec05f"},"posted_at":"2026-07-04T18:31:01.617Z","created_at":"2026-07-04T18:31:01.617Z","updated_at":"2026-07-17T02:36:52.497Z","machine":{"shape":"article.machine/v1","slug":"oip-what-is-tls","kind":"corpus","read":{"human":"https://miscsubjects.com/a/oip-what-is-tls","json":"https://miscsubjects.com/api/articles/oip-what-is-tls","bundle":"https://miscsubjects.com/api/articles/oip-what-is-tls/bundle?format=markdown"},"traversal":{"prev":{"slug":"oip-what-is-cors","human":"https://miscsubjects.com/a/oip-what-is-cors","json":"https://miscsubjects.com/api/articles/oip-what-is-cors"},"next":{"slug":"oip-what-is-dns","human":"https://miscsubjects.com/a/oip-what-is-dns","json":"https://miscsubjects.com/api/articles/oip-what-is-dns"},"hub":{"slug":"philosophy","human":"https://miscsubjects.com/a/philosophy","json":"https://miscsubjects.com/api/articles/philosophy"},"series":"oip-what-is","position":4,"of":19},"ledger":{"claims":3,"sources":1,"contributions":0,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/oip-what-is-tls/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-what-is-tls","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":"source text is prose-preserving — attack via objections, never rewrite the author's words"},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-tls\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-tls\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-what-is-tls/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"oip-what-is-tls\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-what-is-tls | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-what-is-tls","json":"/api/articles/oip-what-is-tls","markdown":"/api/articles/oip-what-is-tls/bundle?format=markdown","skill":"/api/articles/oip-what-is-tls/skill","topology":"/api/articles/oip-what-is-tls/topology","versions":"/api/articles/oip-what-is-tls/revisions","invocations":"/api/articles/oip-what-is-tls/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-what-is-tls","slug":"oip-what-is-tls","title":"TLS: The Foundation of Trust on the Wire"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/oip-what-is-tls","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-what-is-tls/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-what-is-tls\ndescription: Apply the TLS: The Foundation of Trust on the Wire article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# TLS: The Foundation of Trust on the Wire\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-what-is-tls). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-what-is-tls.\n- Read claims and relationships at /api/articles/oip-what-is-tls/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nTLS Transport Layer Security is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser, TLS is the machinery behind it. It turns\n\n## Representations\n\n- Human: /a/oip-what-is-tls\n- JSON: /api/articles/oip-what-is-tls\n- Relationships: /api/articles/oip-what-is-tls/topology\n- History: /api/articles/oip-what-is-tls/revisions\n"},"json":{"route":"/api/articles/oip-what-is-tls","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-what-is-tls/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"EDITORIAL_BOARD_RUN","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Run one receiving editorial-board task. It reads a MODEL_CHAT_INTAKE ledger event, extracts owner complaints and content-rule defects as JSON, ledgers EDITORIAL_BOARD_DECISION, and queues OIP purification.\n# WHEN_TO_USE: after raw model/chat intake, or cron, to process one editorial-board queue item.\n# ARGS: none\n# EX: [EDITORIAL_BOARD_RUN][/EDITORIAL_BOARD_RUN]\n[\"editorial-board\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/EDITORIAL_BOARD_RUN","json":"/api/directory/EDITORIAL_BOARD_RUN","skill":"/api/directory/EDITORIAL_BOARD_RUN?format=skill","oip_contract":"/api/dispatch?key=EDITORIAL_BOARD_RUN"}},{"key":"MODEL_CHAT_INTAKE","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Append raw outside-model/chat text to the ledger and queue the receiving editorial board.\n# WHEN_TO_USE: paste any model answer, raw chat log, critique, complaint, or documentation feedback into the build so the board extracts rules and queues purification.\n# ARGS: $1+ raw text/plain chat log\n# EX: [MODEL_CHAT_INTAKE]Claude said OIP is unclear because...[/MODEL_CHAT_INTAKE]\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/MODEL_CHAT_INTAKE","json":"/api/directory/MODEL_CHAT_INTAKE","skill":"/api/directory/MODEL_CHAT_INTAKE?format=skill","oip_contract":"/api/dispatch?key=MODEL_CHAT_INTAKE"}},{"key":"OIP_ARTICLE_REVIEW","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Run one OIP article loop tick. Claims the next tasks.source=oip-review row and routes it: oip-review scores machine JSON clarity + English clarity with a fresh model; oip-write has a model write a missing OIP article; oip-revise has a model rewrite a failing article as a new append-only version. Every step lands in the ledger.\n# WHEN_TO_USE: cron or manual trigger to advance the recursive OIP documentation loop one step.\n# ARGS: none\n# EX: [OIP_ARTICLE_REVIEW][/OIP_ARTICLE_REVIEW]\n[\"oip-review\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_ARTICLE_REVIEW","json":"/api/directory/OIP_ARTICLE_REVIEW","skill":"/api/directory/OIP_ARTICLE_REVIEW?format=skill","oip_contract":"/api/dispatch?key=OIP_ARTICLE_REVIEW"}},{"key":"OIP_PURIFICATION_SEED","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Queue OIP documentation purification under logical-proof-v1. Root/generated pages are re-reviewed; primer/dynamic pages get append-only oip-revise tasks.\n# WHEN_TO_USE: after content rules change or after an editorial-board decision identifies unclear/proofless OIP documentation.\n# ARGS: optional raw JSON {\"slugs\":[\"oip\",\"oip-operating-model\"],\"brief\":\"...\"}\n# EX: [OIP_PURIFICATION_SEED]{\"slugs\":[\"oip\",\"oip-operating-model\"],\"brief\":\"Every claim must be proven by route/object/receipt.\"}[/OIP_PURIFICATION_SEED]\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_PURIFICATION_SEED","json":"/api/directory/OIP_PURIFICATION_SEED","skill":"/api/directory/OIP_PURIFICATION_SEED?format=skill","oip_contract":"/api/dispatch?key=OIP_PURIFICATION_SEED"}},{"key":"OIP_REVIEW_SEED","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Queue OIP article clarity review tasks. Empty body seeds all OIP root/primer articles across the default fresh-model set. Raw JSON body may pass {\"slugs\":[\"oip\"],\"models\":[\"grok/grok-4.3\"]}.\n# WHEN_TO_USE: start or refill the recursive OIP article review queue.\n# ARGS: $1+ optional raw JSON body\n# EX: [OIP_REVIEW_SEED]{\"slugs\":[\"oip\"],\"models\":[\"grok/grok-4.3\"]}[/OIP_REVIEW_SEED]\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_REVIEW_SEED","json":"/api/directory/OIP_REVIEW_SEED","skill":"/api/directory/OIP_REVIEW_SEED?format=skill","oip_contract":"/api/dispatch?key=OIP_REVIEW_SEED"}},{"key":"OP_ROOT","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Read OP, the Object Protocol: definition, invariants, canonical roots, and OIP compatibility boundary.\n# ARGS: None. Add ?format=markdown for a model-readable document.\n# EX: [OP_ROOT][/OP_ROOT]\n# TESTS: Response names OP, Object Protocol, OPOS, invariants, and the OIP compatibility alias.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OP_ROOT","json":"/api/directory/OP_ROOT","skill":"/api/directory/OP_ROOT?format=skill","oip_contract":"/api/dispatch?key=OP_ROOT"}},{"key":"PROTOCOL_RUN","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Run one protocol tick for a role. $1=role (writer|reviewer|source_hunt|oip-review|writer-queue|...). Claims the next open task, executes it, and marks it done, reopened, or quarantined.\n# WHEN_TO_USE: manual owner trigger for one explicit tick, or an automated protocol tick.\n# AUTORUN: automated callers respect the role KV flag (oip_review_autorun, writer_queue_autorun, source_hunt_autorun, editorial_board_autorun, or protocol_autorun). If the flag is off, the tick returns skipped and touches no task.\n# ARGS: $1=role (default writer)\n# EX: [PROTOCOL_RUN]oip-review[/PROTOCOL_RUN]\n# TESTS: A protocol task that fails three times must end with tasks.status='quarantined', tasks.trace containing protocol_run_failure_count=3, and a TASK_QUARANTINED ledger event. An automated tick with the role flag off must return skipped without claiming a task.\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/PROTOCOL_RUN","json":"/api/directory/PROTOCOL_RUN","skill":"/api/directory/PROTOCOL_RUN?format=skill","oip_contract":"/api/dispatch?key=PROTOCOL_RUN"}},{"key":"TAP_GO_MODEL_PROFILES","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Read the five owner-editable model-specific content slots used by token Tap & Go: ChatGPT, Claude, Grok, Gemini, and Kimi. The model selector belongs to the token DROP, not the build audit.\n# ARGS: None for read. Owner edits one profile with PUT /api/tap-go-profiles {model,content}.\n# EX: [TAP_GO_MODEL_PROFILES][/TAP_GO_MODEL_PROFILES]\n# TESTS: Returns tap-go-model-profiles/1.0, five models, their current owner text, and the token mint shape containing model=MODEL.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/TAP_GO_MODEL_PROFILES","json":"/api/directory/TAP_GO_MODEL_PROFILES","skill":"/api/directory/TAP_GO_MODEL_PROFILES?format=skill","oip_contract":"/api/dispatch?key=TAP_GO_MODEL_PROFILES"}},{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: Cyrus or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"DISCLOSURE_GET","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Read a versioned public defensive-publication artifact from the disclosure archive. Text is scanned for bearer/credential material at read time; binary artifacts are admitted only after local render/hash/credential review. Keys are immutable and public.\n# ARGS: $1 = public disclosure path returned by a publication manifest, for example 2026-07-17/operation-killbox-v1.1/specification.md.\n# TESTS: Unknown paths and traversal return 404; text containing credential material returns a generic 404; successful responses include immutable caching, CORS, nosniff and sandbox headers.\n[\"$1\"]","input_schema":"{\"type\":\"string\",\"pattern\":\"^[a-zA-Z0-9][a-zA-Z0-9._/-]{0,500}$\"}","examples":"[\"2026-07-17/operation-killbox-v1.1/specification.md\"]","authority_required":false,"representations":{"article":"/a/directory/DISCLOSURE_GET","json":"/api/directory/DISCLOSURE_GET","skill":"/api/directory/DISCLOSURE_GET?format=skill","oip_contract":"/api/dispatch?key=DISCLOSURE_GET"}},{"key":"RELAY_POST_APPEND","type":"fn","method":null,"category":"protocol","enabled":true,"contract":"# WHAT: Append one model's public adoption/proof link to THE RELAY. v3 separately records the high-level verdict and exact outcome class so a model failure cannot be confused with a lane timeout.\n# WHEN_TO_USE: After a model audits the prior relay and performs real work. This records drafts and actual publication results; it does not authorize a social post.\n# ARGS: one JSON object: platform; identity_mode named|incognito; exact model_name, model_provider, model_version and session_label; action; result_summary; verdict PASS|FAIL|MIXED; outcome_class SUCCESS|PARTIAL|MODEL_FAILED|LANE_TIMEOUT (PASS=SUCCESS, MIXED=PARTIAL, FAIL uses one of the two failure classes); proof_links[]; media_links[]; platform_copy with LinkedIn/Facebook/Instagram/X required, each beginning [execution surface · exact model name · YYYY-MM-DD HH:MM UTC] then a newline and third-person observed result; tag_targets[{name,handle?,why}] with at least one materially connected target; publication_results; audit_how; parent_post_id and prior_post_hash from /api/relay?social=1.\n# SECURITY: Public fields contain only cap_ fingerprints, inv_ ids, public hashes/status URLs/anchors. Never include share tokens or backend credentials. A live capability detected here is revoked before a generic 404 is returned.\n# TESTS: Reject platform copy missing its attribution header, first-person copy, an empty tag target list, a target missing name/why, stale parent/hash, missing identity/proof/copy/tag rationale, inconsistent verdict/outcome_class, or credential material. Return v3 post, outcome class, receipt and chain links.\n[\"$1+\"]","input_schema":"{\"type\":\"object\",\"required\":[\"platform\",\"identity_mode\",\"model_name\",\"model_provider\",\"model_version\",\"session_label\",\"action\",\"result_summary\",\"verdict\",\"outcome_class\",\"proof_links\",\"platform_copy\",\"tag_targets\",\"publication_results\",\"audit_how\",\"parent_post_id\",\"prior_post_hash\"],\"properties\":{\"tag_targets\":{\"type\":\"array\",\"minItems\":1,\"items\":{\"type\":\"object\",\"required\":[\"name\",\"why\"],\"properties\":{\"name\":{\"type\":\"string\",\"minLength\":1},\"handle\":{\"type\":[\"string\",\"null\"]},\"why\":{\"type\":\"string\",\"minLength\":1}}}}}}","examples":"[{\"platform\":\"multi\",\"identity_mode\":\"incognito\",\"model_name\":\"Kimi K3\",\"model_provider\":\"Moonshot AI\",\"model_version\":\"K3\",\"session_label\":\"Kimi K3 (incognito)\",\"verdict\":\"PASS\",\"tag_targets\":[{\"name\":\"Anthropic\",\"handle\":\"@AnthropicAI\",\"why\":\"MCP defines one connectivity layer OIP receipts traverse\"}],\"publication_results\":{\"x\":{\"status\":\"POSTED\",\"url\":\"https://x.com/i/web/status/...\",\"receipt\":\"https://miscsubjects.com/receipt/inv_...\"}},\"parent_post_id\":\"rsp_...\",\"prior_post_hash\":\"...\"}]","authority_required":false,"representations":{"article":"/a/directory/RELAY_POST_APPEND","json":"/api/directory/RELAY_POST_APPEND","skill":"/api/directory/RELAY_POST_APPEND?format=skill","oip_contract":"/api/dispatch?key=RELAY_POST_APPEND"}},{"key":"WEB_MODEL_LANE","type":"http","method":"GET","category":"protocol","enabled":true,"contract":"# WHAT: Tell a web ChatGPT or similar browser-based model exactly how to reach miscsubjects without code-interpreter Bash.\n# ARGS: none.\n# EX: [WEB_MODEL_LANE][/WEB_MODEL_LANE]\n# TESTS: Response names browser/web, OpenAI Actions, GET fire=1, and says not to use Bash/curl after a code-interpreter DNS failure.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/WEB_MODEL_LANE","json":"/api/directory/WEB_MODEL_LANE","skill":"/api/directory/WEB_MODEL_LANE?format=skill","oip_contract":"/api/dispatch?key=WEB_MODEL_LANE"}},{"key":"VOXEL_BATCH","type":"http","method":"POST","category":"protocol","enabled":true,"contract":"# WHAT: Land a whole document or up to 300 typed article operations with one parent result and per-operation results.\n# ARGS: JSON {document:{slug,title,markdown}|operations:[...],actor,key?}. Web ChatGPT uses the OpenAI Action from /api/openai/actions.json; a small browser-only payload may use GET /api/protocol/voxel-batch?fire=1&payload=<URL-encoded JSON>. Never use code-interpreter Bash for miscsubjects.com.\n# EX: [VOXEL_BATCH]{\"operations\":[{\"op\":\"challenge\",\"slug\":\"philosophy\",\"expected_thread_head\":\"<head>\",\"stance\":\"challenge\",\"body\":\"argument\"}],\"actor\":\"model\",\"key\":\"<scoped token>\"}[/VOXEL_BATCH]\n# TESTS: Require landed+failed=total and a result for every operation; large web sessions use the Action, not a URL-length-limited GET.\n# EXISTING SLUG LAW: Document mode appends new DIVs when document.slug already exists; it does not replace prior active DIVs. For a whole-document revision, use operations mode to consolidate the superseded active DIVs into the first replacement DIV with exact expected_hashes and explicit replacement text, or choose a new slug. Verify the final active article body hash.\n$1+","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/VOXEL_BATCH","json":"/api/directory/VOXEL_BATCH","skill":"/api/directory/VOXEL_BATCH?format=skill","oip_contract":"/api/dispatch?key=VOXEL_BATCH"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: Cyrus says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.cyrus.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/massoumicyrus/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: Cyrus asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: Cyrus says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/massoumicyrus/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: Cyrus asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: Cyrus asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: Cyrus says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: Cyrus says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: Cyrus asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: Cyrus says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","protocol","oip","what","is","tls"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-what-is-tls/invocations?status=success","failure_events":"/api/articles/oip-what-is-tls/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"oip-what-is-tls","title":"TLS: The Foundation of Trust on the Wire","body":"TLS (Transport Layer Security) is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser, TLS is the machinery behind it. It turns an untrusted pipe—the public internet—into a trusted channel between two endpoints.\n\nWithout TLS, the internet is a postcard. Anyone between sender and receiver can read, alter, or replay traffic. TLS fixes this at the transport layer, which means applications get security for free. They send plaintext; TLS handles the rest.\n\nTLS matters to OIP because auditable trust requires encrypted channels. An open, deterministic protocol that publishes its rules but sends them over plaintext is self-defeating. TLS is the minimum viable envelope. You cannot build deterministic, auditable systems on a channel you do not control.\n\nTLS is a handshake, then a stream.\n\nThe Handshake:\n1. The client sends a ClientHello with supported cipher suites, a random nonce, and an optional SNI (Server Name Indication).\n2. The server responds with a ServerHello, picking the cipher suite, sending its own nonce, and delivering its certificate chain.\n3. The client verifies the certificate chain against its trust store. If the chain breaks, the handshake aborts.\n4. The client generates a pre-master secret, encrypts it with the server's public key, and sends it.\n5. Both sides derive the same session keys from the pre-master secret and the two nonces.\n6. The client sends a Finished message encrypted with the new session keys. The server verifies it.\n7. The server sends its own Finished. The client verifies it.\n8. The encrypted application data stream begins.\n\nThe handshake is asymmetric cryptography. The stream is symmetric. This is efficient: expensive operations happen once per session, then fast AES-GCM or ChaCha20-Poly1305 takes over.\n\nInputs:\n- A TCP connection.\n- A server hostname (for SNI and certificate validation).\n- A client trust store (root CAs).\n- Optional: client certificate, ALPN protocols, SNI.\n\nOutputs:\n- An encrypted, authenticated byte stream between two endpoints.\n- A verified identity chain for the server.\n- Optional: verified client identity.\n\nInvariants:\n- Data confidentiality: no intermediate can read the plaintext.\n- Data integrity: no intermediate can alter the stream without detection.\n- Replay resistance: old sessions cannot be replayed against the same keys.\n- Forward secrecy: if the server's long-term key is compromised later, past sessions remain secure (with ephemeral key exchange).\n\nFailure modes:\n- Certificate expired → handshake aborts.\n- Certificate hostname mismatch → handshake aborts.\n- Untrusted CA → handshake aborts.\n- Downgrade attack (client/server negotiate weak cipher) → modern implementations abort.\n\n1. Web Browsing (HTTPS)\nWhen you navigate to https://miscsubjects.com, your browser performs a TLS handshake with the server. The server's certificate is signed by a CA in your browser's trust store. The resulting AES-GCM stream protects every request and response. If an attacker intercepts the traffic, they see noise.\n\n2. API Authentication\nAn API key in an HTTP header is useless over HTTP. Over TLS, it is protected. The Authorization: Bearer <token> header travels inside the encrypted envelope. TLS is what makes token-based authentication practical.\n\n3. gRPC over TLS\ngRPC uses HTTP/2, which requires TLS for production deployments. The ALPN negotiation during the handshake selects h2. The certificate validates the service identity. Without TLS, gRPC falls back to plaintext, which is suitable only for local development.\n\n4. Database Connections\nPostgreSQL, MySQL, and MongoDB all support TLS-wrapped connections. The client verifies the server certificate. Some deployments also use client certificates for mutual authentication. The data at rest is encrypted by the database; TLS encrypts data in transit. Both are necessary.\n\n5. OIP Directory Communication\nWhen an OIP agent queries a directory row or sends a dispatch command, the payload traverses the internet. TLS wraps that traffic. Without it, the command plane is exposed. With it, the command plane is protected, auditable, and deterministic.\n\nCertificate pinning without a rotation plan.\nPinning hardcodes a certificate hash. When the certificate rotates, the client breaks. Plan for rotation, or do not pin.\n\nAccepting all certificates.\nDisabling certificate verification (curl -k, NODE_TLS_REJECT_UNAUTHORIZED=0) is a silent self-attack. You are encrypting traffic that an active attacker can intercept, modify, and re-sign. This is worse than plaintext because it looks safe.\n\nMissing SNI.\nModern hosting uses SNI to serve multiple certificates from one IP. If the client omits SNI, the server returns the wrong certificate, and the handshake fails.\n\nRelying on TLS alone for authentication.\nTLS authenticates the server. It does not authenticate the application user. You still need tokens, signatures, or session cookies. TLS is the pipe, not the gate.\n\nUsing obsolete TLS versions.\nTLS 1.0 and 1.1 are broken. TLS 1.2 is the minimum viable version. TLS 1.3 is preferred. It reduces handshake latency and removes vulnerable cipher suites.\n\nOIP is the Open Interface Protocol. It demands that systems be open (their rules are published), deterministic (the same input always produces the same output), and auditable (every action is traceable and verifiable).\n\nTLS serves all three:\n\n- Open: TLS is an open standard (RFC 8446). Its algorithms are public, peer-reviewed, and unpatented. There are no hidden backdoors by design—only mathematics.\n- Deterministic: Given the same handshake parameters, TLS produces the same key material. The protocol is state-machine driven. A deterministic system can model TLS behavior exactly.\n- Auditable: TLS sessions log cipher suites, certificates, and key exchange types. Certificate Transparency logs publish every issued certificate. A TLS-protected channel creates an auditable boundary: you can prove what crossed the wire and when.\n\nTLS is not the whole OIP security model. But it is the floor. Without it, there is no trustworthy channel. Without a trustworthy channel, there is no auditable protocol. Without an auditable protocol, there is no deterministic system worth trusting.\n\n## Connection to the Grain Philosophy\n\nThis protocol is part of the [Open Inventory Protocol](/a/philosophy) — a living system of self-describing voxels that serves the Grain philosophy. The OIP is the interface. The philosophy is the core.\n","hero":null,"images":[],"style":{},"tags":["oip","protocol"],"category":null,"model":"owner","ledger":{"href":"/api/articles/oip-what-is-tls/ledger","live":true},"embeds":[],"widgets":[],"home":true,"claims":[{"id":"c1","text":"TLS (Transport Layer Security) is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser, TLS is the machinery behind it. It turns an untrusted pipe—the public internet—into a trusted channel between two endpoints.","tier":"system","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Contradictory evidence or counter-example."},{"id":"c2","text":"Without TLS, the internet is a postcard. Anyone between sender and receiver can read, alter, or replay traffic. TLS fixes this at the transport layer, which means applications get security for free. They send plaintext; TLS handles the rest.","tier":"system","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Contradictory evidence or counter-example."},{"id":"c3","text":"TLS matters to OIP because auditable trust requires encrypted channels. An open, deterministic protocol that publishes its rules but sends them over plaintext is self-defeating. TLS is the minimum viable envelope. You cannot build deterministic, auditable systems on a channel you do not control.","tier":"system","source_ids":["s1"],"evidence_basis":"derived_inference","materiality":true,"weight":0.8,"status":"active","falsifier":"Contradictory evidence or counter-example."}],"sources":[{"id":"s1","type":"adjacent","url":"https://miscsubjects.com/a/oip-what-is-tls","title":"TLS: The Foundation of Trust on the Wire","quote":"TLS (Transport Layer Security) is the cryptographic protocol that wraps plaintext communication in authenticated, encrypted, and integrity-verified envelopes. Every time you see a padlock in a browser","summary":"Primary exposition of TLS: The Foundation of Trust on the Wire.","claim_ids":["c1","c2","c3"],"quality_score":0.9}],"reviews":[],"extra":{"corpus_map":{"series":"oip-what-is","hub":"philosophy","prev":"oip-what-is-cors","next":"oip-what-is-dns","position":4,"of":19},"normandy_v1":{"traversal":{"convergence_patterns":["C20"],"adjacent_sources":["shannon-1948"],"falsifier_surface":"A system where this concept is unnecessary or harmful.","rival_frame":"This concept is an implementation detail, not a fundamental principle."}}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":2,"contributions":[],"provenance":[{"ts":"2026-07-17T02:36:52.497Z","model":"owner","action":"voxel_divide","prompt":"","input":"oip-what-is-tls","response":"36 DIVs from body (verbatim, roundtrip-checked)","tokens_in":0,"tokens_out":0,"cost":0,"prev":"genesis","hash":"7958d90ce641e17237f0d02700865cada0cd41b45aa068cbcb9d04a9af0ec05f"}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"owner":1},"head":"7958d90ce641e17237f0d02700865cada0cd41b45aa068cbcb9d04a9af0ec05f"},"posted_at":"2026-07-04T18:31:01.617Z","created_at":"2026-07-04T18:31:01.617Z","updated_at":"2026-07-17T02:36:52.497Z","machine":{"shape":"article.machine/v1","slug":"oip-what-is-tls","kind":"corpus","read":{"human":"https://miscsubjects.com/a/oip-what-is-tls","json":"https://miscsubjects.com/api/articles/oip-what-is-tls","bundle":"https://miscsubjects.com/api/articles/oip-what-is-tls/bundle?format=markdown"},"traversal":{"prev":{"slug":"oip-what-is-cors","human":"https://miscsubjects.com/a/oip-what-is-cors","json":"https://miscsubjects.com/api/articles/oip-what-is-cors"},"next":{"slug":"oip-what-is-dns","human":"https://miscsubjects.com/a/oip-what-is-dns","json":"https://miscsubjects.com/api/articles/oip-what-is-dns"},"hub":{"slug":"philosophy","human":"https://miscsubjects.com/a/philosophy","json":"https://miscsubjects.com/api/articles/philosophy"},"series":"oip-what-is","position":4,"of":19},"ledger":{"claims":3,"sources":1,"contributions":0,"revisions":2,"objections_url":"https://miscsubjects.com/api/articles/oip-what-is-tls/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-what-is-tls","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":"source text is prose-preserving — attack via objections, never rewrite the author's words"},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-tls\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-tls\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-what-is-tls/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"oip-what-is-tls\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-what-is-tls | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"}},"representations":{"article":"/a/oip-what-is-tls","json":"/api/articles/oip-what-is-tls","markdown":"/api/articles/oip-what-is-tls/bundle?format=markdown","skill":"/api/articles/oip-what-is-tls/skill","topology":"/api/articles/oip-what-is-tls/topology","versions":"/api/articles/oip-what-is-tls/revisions","invocations":"/api/articles/oip-what-is-tls/invocations"}}}}