{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"directory-row-contract","urls":{"read":"https://miscsubjects.com/api/articles/directory-row-contract/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/directory-row-contract/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/directory-row-contract/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/directory-row-contract/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/directory-row-contract/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/directory-row-contract/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/directory-row-contract/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"directory-row-contract","title":"One row of SQL is the whole contract for a capability, and the 892nd took 3.1 seconds","register":"essay","tags":["tooling","oip","architecture","d1","contracts","mcp"],"updated_at":"2026-07-27T04:32:07.626Z","body_excerpt":"A capability on this build is one row in a SQLite table on Cloudflare D1 called `directory`. The row is the whole contract: what the capability is, how to call it, what comes back, which credential it needs, and who is allowed to run it. There is no companion file, no registration call in application code, and no deploy step. On 2026-07-26 the table held 891 rows.\n\n**Scope note:** this article covers the `directory` table's row shape only — the contract for API calls, shell commands, agents and other executable capabilities. It is one of at least two object families on this build; content (articles, their claims, their revisions) lives in a separate `articles`/`article_slots` pair of tables with its own resolver, not in `directory`. [892 rows, 8 of them MCP](/a/the-directory-is-not-the-object-system) draws that line explicitly.\n\nEvery field below is published rather than paraphrased, every runner type has a real row printed as stored, and the failure strings are copied out of the code that emits them. The volume argument — why holding 891 tool definitions in a model's context is the wrong shape — is [tooling as data](/a/tooling-as-data). The call sequence around a row is [the four-step loop](/a/dispatch-four-step-loop). The Model Context Protocol view of the same rows is [MCP as a projection](/a/mcp-as-a-projection).\n\n## Evidence status\n\n**Observed** marks first-party measurements or runtime receipts from the named environment.\n**Derived** marks arithmetic calculated from cited inputs. **Specified** marks vendor or standards\ndocumentation. **Implemented** and **deployed** name code and live-state evidence, respectively.\n**Reproduced** means the stated procedure was rerun. **Externally attested** marks operator reports;\nthose reports show that an experience occurred, not that it is universal.\n\n## Eighteen columns, of which six existed on the first day\n\nThe table as it stands in production. Read it back yourself:\n\n```bash\ncd /Users/cyrusmassoumi/miscsubjects-pages\nnpx wrangler d1 execute loop-content-spine --remote \\\n  --command \"SELECT sql FROM sqlite_master WHERE name='directory';\"\n```\n\n```sql\nCREATE TABLE directory (\n  key        TEXT PRIMARY KEY,\n  type       TEXT NOT NULL CHECK (type IN ('fn','http','agent','flow')),\n  target     TEXT,\n  auth       TEXT,\n  content    TEXT,\n  updated_at TEXT NOT NULL\n, category TEXT, allowed_categories TEXT, seq INTEGER, enabled INTEGER DEFAULT 1,\n  planner_visible INTEGER DEFAULT 1, planner_rank INTEGER DEFAULT 100,\n  input_schema TEXT, examples TEXT, sensitive INTEGER DEFAULT 0, runner TEXT,\n  includes TEXT, created_at TEXT)\n```\n\nThe first six columns came from `migrations/0007_directory.sql:1-8`. Everything after the closing parenthesis of the original statement is an `ALTER TABLE` bolted on later, which is why the SQL reads the way it does.\n\n| Column | Type · default | Required | What it holds | Real value |\n| --- | --- | --- | --- | --- |\n| `key` | TEXT, primary key | yes | The invocation name. Unique by constraint, uppercase by convention. | `GROK_MODELS` |\n| `type` | TEXT, `CHECK IN ('fn','http','agent','flow')` | yes | Decides how `target` and `content` are read. The only constrained column in the table. | `http` |\n| `target` | TEXT | by type | `fn`: a function name. `http`: `\"METHOD url\"`. `agent`: a model id. `flow`: empty. | `GET https://api.x.ai/v1/models` |\n| `auth` | TEXT | no | The *name* of an environment variable and how to apply it. Never a secret value. | `bearer:GROK_API_KEY` |\n| `content` | TEXT | yes, gated | `fn`/`http`: comment docstring plus the argument template. `agent`: the system prompt. `flow`: the step DSL. | see the four rows below |\n| `updated_at` | TEXT, NOT NULL | yes | ISO timestamp of the last write. The only change marker on the row. | `2026-06-10 02:22:52` |\n| `category` | TEXT | no | Grouping label. 110 distinct values live. | `grok` |\n| `allowed_categories` | TEXT | no | On `agent` rows: the categories that agent's tool listing is restricted to, or `*","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"The directory table held 891 rows on 2026-07-26, split fn 480, http 303, agent 57, flow 51.","tier":"system","section":"The type column decides everything else, and it has exactly four legal values","interaction_risk":false,"status":"active","source_ids":["s1","s20","s25"],"why_material":"Every size and cost argument on the page rests on the real row count and its distribution.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"The live directory table has eighteen columns, six from the original migration and eleven added by later ALTER TABLE statements, and created_at is present in production with no migration in the repository that adds it.","tier":"system","section":"Eighteen columns, of which six existed on the first day","interaction_risk":false,"status":"active","source_ids":["s26"],"why_material":"A rebuild that copies only the documented schema gets a different table; the drift has to be stated, not smoothed over.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"type is the only column with a CHECK constraint, restricting it to fn, http, agent or flow, so a fifth runner type cannot be inserted at all.","tier":"system","section":"The type column decides everything else, and it has exactly four legal values","interaction_risk":false,"status":"active","source_ids":["s20","s26"],"why_material":"The four-type claim is enforced by the database rather than by convention, which is what makes the runner branch total.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"Creating a capability is one authenticated POST that returns HTTP 201, and the new key is invocable on the next request with no deploy, restart or client refresh.","tier":"system","section":"Adding the 892nd capability: one POST, then a receipt proving it ran","interaction_risk":false,"status":"active","source_ids":["s22"],"why_material":"This is the central property of the design; without a verified receipt it is an assertion.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"A capability created and invoked for the first time returned a real upstream result in 3.126264 seconds of wall clock, measured with curl -w from a laptop.","tier":"system","section":"Adding the 892nd capability: one POST, then a receipt proving it ran","interaction_risk":false,"status":"active","source_ids":["s22"],"why_material":"Stating the cost of the no-deploy path in seconds is what turns the claim into an engineering fact.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"The auth column stores the name of an environment variable and never a value, so reading the entire table yields upstream URLs and twelve distinct credential names but zero credentials.","tier":"system","section":"The row names the environment variable; the value never enters the table","interaction_risk":false,"status":"active","source_ids":["s10","s19","s21"],"why_material":"The whole registry is publicly readable; the security argument depends on this being true of every row, not most.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"A capability token's scope is enforced server-side by capGateCheck before any runner is reached, so a row marked sensitive is refused to a token whose risk ceiling is not high, with the literal reason risk_ceiling:low<row:high.","tier":"system","section":"The row names the environment variable; the value never enters the table","interaction_risk":false,"status":"active","source_ids":["s10","s18"],"why_material":"Without this, a writable row would be a writable permission, and anyone who can edit the table could grant themselves anything.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"Reading one row with ?key=<KEY>&format=markdown returns a self-contained contract including the path, the run-now URL, the router tag, inputs and outputs, the affordances the presented credential has, and four troubleshooting entries.","tier":"system","section":"Reading one row returns a document that assumes the reader knows nothing","interaction_risk":false,"status":"active","source_ids":["s11","s23"],"why_material":"The claim that a stranger needs no prior context is only testable against the actual document.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"One row's full contract is roughly 4.4 KB with under 100 bytes of variance across four row types, while the same registry fetched whole is 1,608,554 bytes for 877 objects.","tier":"system","section":"Reading one row returns a document that assumes the reader knows nothing","interaction_risk":false,"status":"active","source_ids":["s11","s12","s13","s14","s23"],"why_material":"Fetch-on-demand versus ship-everything is a 360-fold difference in bytes; the arithmetic has to be on the page.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"Adding a capability without a restart depends on the caller, not the registry: the MCP spec defines notifications/tools/list_changed, and at least two clients have been reported ignoring it.","tier":"system","section":"The no-restart property depends on something outside the row","interaction_risk":false,"status":"active","source_ids":["s3","s7","s8","s9"],"why_material":"It would be dishonest to present no-restart as a property of the storage format when independent reports show the failure is on the client side.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c11","text":"MCP requires a tool's inputSchema to be a JSON Schema object while description is optional, which is the inverse of the row, where the docstring is mandatory and the schema is not.","tier":"system","section":"Where the row loses to a schema, and where a schema loses to the row","interaction_risk":false,"status":"active","source_ids":["s2","s3","s6"],"why_material":"The comparison is only fair if the two formats' required fields are stated from their own specifications.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c12","text":"The row performs no argument validation before the call, so a malformed argument is caught by the runner or the upstream rather than by a validator, which is the dimension on which it loses to JSON Schema, OpenAPI and MCP.","tier":"system","section":"Where the row loses to a schema, and where a schema loses to the row","interaction_risk":false,"status":"active","source_ids":["s15","s2","s4","s5","s6"],"why_material":"A comparison that does not name where the design loses is advocacy, not a reference.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c13","text":"Of 891 rows, 256 carry an input_schema and 63 carry examples, and the publish gate refuses only writes that would newly break compliance rather than forcing a backfill.","tier":"system","section":"Every failure names itself, and the names are in the code","interaction_risk":false,"status":"active","source_ids":["s18","s21"],"why_material":"The registry's own hygiene numbers set the reader's expectation of how typed the surface actually is.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c14","text":"A row carries no version number; the receipt carries a SHA-256 contract fingerprint that changed when target was edited and stayed byte-identical when examples was edited.","tier":"system","section":"A row has no version number, and the receipt is where change is detectable","interaction_risk":false,"status":"active","source_ids":["s16","s24"],"why_material":"Callers need to know exactly which edits break a pinned token and which do not, and this was measured rather than inferred from the hashing code.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c15","text":"Receipts are written by the dispatcher in the same code path that runs the call, and a deleted row's receipts still resolve and still report confirmed:true.","tier":"system","section":"A row has no version number, and the receipt is where change is detectable","interaction_risk":false,"status":"active","source_ids":["s17","s22"],"why_material":"Deleting a definition must not delete the evidence of what it did, and agent-authored records have been shown to be fabricated.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"publisher_documentation","url":"https://developers.cloudflare.com/d1/","title":"Cloudflare D1 overview","quote":"D1 is Cloudflare's managed, serverless database with SQLite's SQL semantics, built-in disaster recovery, and Worker and HTTP API access.","summary":"The store the directory table lives in. A reader gets the SQL dialect (SQLite), the access paths (Worker binding and HTTP API), and the pricing tiers needed to reproduce the setup. Positive: the constraint that the whole registry is one SQLite table is a property of this product.","claim_ids":["c1"]},{"id":"s2","type":"publisher_documentation","url":"https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview","title":"Tool use overview — Claude Docs","quote":"To have Claude call a function that you define, pass a tool with an input_schema, then execute the call when Claude returns a tool_use block.","summary":"The competing contract format, from the vendor. A reader gets the exact shape of a schema-typed tool definition and the strict-conformance option. Negative for the row: this is what the row does not do, and the page is explicit that the schema is what guarantees the call shape.","claim_ids":["c11","c12"]},{"id":"s3","type":"specification","url":"https://modelcontextprotocol.io/specification/2025-06-18/server/tools","title":"Model Context Protocol — Tools (2025-06-18)","quote":"When the list of available tools changes, servers that declared the listChanged capability SHOULD send a notification: { \"jsonrpc\": \"2.0\", \"method\": \"notifications/tools/list_changed\" }","summary":"The spec text for adding a capability without a restart. A reader gets the exact notification method name and the fact that it is a SHOULD on the server side with no client obligation stated, which is why the client reports below diverge.","claim_ids":["c10","c11"]},{"id":"s4","type":"specification","url":"https://json-schema.org/draft/2020-12/json-schema-validation","title":"JSON Schema Validation, draft 2020-12","quote":"Validation keywords in a schema impose requirements for successful validation of an instance. These keywords are all assertions without any annotation behavior.","summary":"Where typed tool definitions get their power: assertions evaluated against an instance before anything runs. A reader gets the vocabulary the row deliberately does not implement. Negative for the row on the validation dimension.","claim_ids":["c12"]},{"id":"s5","type":"specification","url":"https://spec.openapis.org/oas/v3.1.0.html","title":"OpenAPI Specification 3.1.0","quote":"The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection.","summary":"The third alternative in the comparison. A reader gets the design goal — client generation and discovery by strangers — which is the dimension the row loses on outright.","claim_ids":["c12"]},{"id":"s6","type":"repository","url":"https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/schema/2025-06-18/schema.ts","title":"modelcontextprotocol/schema.ts — the Tool interface","quote":"inputSchema: {\n    type: \"object\";\n    properties?: { [key: string]: object };\n    required?: string[];\n  };","summary":"The MCP tool contract in code rather than prose: description is optional, inputSchema is mandatory and is a JSON Schema object. Confirms the comparison table's typing row from the source of truth.","claim_ids":["c11","c12"]},{"id":"s7","type":"github","url":"https://github.com/mcpjungle/MCPJungle/issues/260","title":"Dynamic tool sync: notifications/tools/list_changed + polling fallback","quote":"MCPJungle caches upstream tool lists at registration time only. If an upstream server adds or removes tools later, MCPJungle's view stays stale until a manual re-registration or full restart.","summary":"A tool-registry gateway maintainer describing the add-a-capability-without-redeploy problem from the inside: registry rows go stale and removed tools leave dangling references. Negative on the current state, positive on the registry design itself.","claim_ids":["c10"]},{"id":"s8","type":"github","url":"https://github.com/kirodotdev/Kiro/issues/6553","title":"Kiro IDE does not handle MCP notifications/tools/list_changed — dynamic tools not refreshed","quote":"When an MCP server dynamically adds or removes tools at runtime and sends this notification per the MCP spec, Kiro IDE does not re-query tools/list, so the new tools never appear until the server is manually reconnected.","summary":"Reproducible report with a minimal dynamic-registration server: the spec-compliant path for adding a capability without a restart silently does nothing in one client while working in two others. Negative — the no-redeploy story depends on client support that is not uniform.","claim_ids":["c10"]},{"id":"s9","type":"github","url":"https://github.com/microsoft/wassette/issues/308","title":"GitHub Copilot CLI does not dynamically load tools via tools/list_changed","quote":"Internal terminal testing shows the CLI never refreshes its tool list, unlike GitHub Copilot in VS Code which updates immediately.","summary":"A Microsoft engineer files the same defect against a second client, with a repro video, and notes the same vendor's editor extension behaves correctly. Negative: hot-adding a capability is specified but unevenly implemented.","claim_ids":["c10"]},{"id":"s10","type":"hn","url":"https://news.ycombinator.com/item?id=47263727","title":"Comment on: Agentic Engineering Patterns","quote":"The agent never holds API keys directly — the proxy holds them and issues scoped, short-lived capability tokens (ES256, 60s TTL). Single enforcement point for scanning, classification, and audit.","summary":"Production patterns from a team running agents, derived from twelve rounds of red-teaming: keep secrets out of the caller's reach behind an enforcement point and hand out scoped short-lived tokens instead. Positive, and the closest independent match to the auth column plus capGateCheck design.","claim_ids":["c6","c7"]},{"id":"s11","type":"hn","url":"https://news.ycombinator.com/item?id=46487491","title":"Comment on: Polymcp – toolkit for building MCP agents that discover, inspect and orchestrate tools","quote":"CLI + registry: manage MCP servers, configs, and agents from the CLI; servers can be added/removed without touching agent code.","summary":"Show HN for a toolkit built around an inspector that exposes each tool's schema and inputs/outputs plus a registry allowing add and remove with no code change. Positive, and independent confirmation that the self-describing-row-plus-registry shape is being arrived at separately.","claim_ids":["c8","c9"]},{"id":"s12","type":"github","url":"https://github.com/abdlkrim-jribi/hcode/issues/4","title":"Reduce Context Window Usage (13,341 tokens for tools alone)","quote":"The agent injects ALL 47 tool schemas on every single request, consuming ~13,341 tokens before the user message is even sent.","summary":"A maintainer costs his own contract format and publishes the breakdown: ~4,168 static tool docs, ~4,515 static schemas, ~751 MCP docs, ~3,906 MCP schemas. Negative on definitions-in-context, and a worked example of measuring a contract format rather than arguing about it.","claim_ids":["c9"]},{"id":"s13","type":"hn","url":"https://news.ycombinator.com/item?id=47400262","title":"Comment on: Apideck CLI – An AI-agent interface with much lower context consumption than MCP","quote":"We built a unified API with a large surface area and ran into a problem when building our MCP server: tool definitions alone burned 50,000+ tokens before the agent touched a single user message.","summary":"A vendor engineer reports hitting 50k tokens of contracts before any work and replacing them with a thin contract plus on-demand discovery, citing a 75-run comparison. Negative on fat schemas, positive on fetch-on-demand.","claim_ids":["c9"]},{"id":"s14","type":"github","url":"https://github.com/G-Core/gcore-mcp-server/issues/14","title":"GCORE_TOOLS=* advertises ~488k tokens of tool definitions — larger than most context windows","quote":"with `GCORE_TOOLS=*` it advertises **741 tools / ~488,013 tokens** (659/tool) — that exceeds a 200K context window on its own, so the full config can't actually be used with most models.","summary":"A tiktoken harness run against a live server listing, with a per-tool average and a proposed fix. Strongly negative on definitions-in-context at scale, and the closest external comparison to this build's 891 rows.","claim_ids":["c9"]},{"id":"s15","type":"hn","url":"https://news.ycombinator.com/item?id=47381282","title":"Comment on: MCP is dead; long live MCP","quote":"Tool results from programmatic calls are not added to Claude's context window, only the final code output is. They report up to 98.7% token savings in some workflows.","summary":"The counter-argument, kept because it holds: input and output schemas let a code-writing agent plan one precise program instead of a print-and-inspect loop. Positive on schema-as-contract and explicitly against reducing the question to schema bloat — the reason the verdict here is conditional rather than absolute.","claim_ids":["c12"]},{"id":"s16","type":"hn","url":"https://news.ycombinator.com/item?id=47417059","title":"Comment on: Show HN: GitAgent – An open standard that turns any Git repo into an AI agent","quote":"If an LLM hallucinates in production and decides to execute a destructive tool defined in SKILL.md (like dropping a table or issuing a Stripe refund), a Git PR approval process doesn't help you mid-flight.","summary":"Argues that version-controlling capability definitions is configuration management, not runtime control, so the invocation needs its own interception point. Negative on definition-time governance — the reason contract pinning is evaluated at call time here rather than at edit time.","claim_ids":["c14"]},{"id":"s17","type":"hn","url":"https://news.ycombinator.com/item?id=47579314","title":"Comment on: Agent Runs Code You Never Wrote","quote":"fabricated an audit record — invented a governance event that never happened and presented it as compliance evidence.","summary":"A controlled two-condition experiment: with no runtime enforcement the agent authored its own audit record and it was false. Negative about agent-authored receipts, positive about engine-authored ones — the reason the receipt here is written by the dispatcher.","claim_ids":["c15"]},{"id":"s18","type":"hn","url":"https://news.ycombinator.com/item?id=46747408","title":"Comment on: Ask HN: How are you enforcing permissions for AI agent tool calls in production?","quote":"The audit trail piece is critical too. Being able to answer \"why was this blocked?\" after the fact builds trust with teams rolling this out.","summary":"Puts the enforcement point in a proxy outside the agent's context with argument-level rather than tool-level rules. Positive, and the practical argument for denial reasons that name themselves — the literal risk_ceiling and contract_changed strings in the failure table.","claim_ids":["c13","c7"]},{"id":"s19","type":"github","url":"https://github.com/rafaself/aws-mcp-gateway/issues/21","title":"Add sanitized audit logging contract for MCP tool calls","quote":"Add structured audit logging for MCP tool calls without exposing credentials, signed request data, raw AWS responses, or CloudWatch log message contents.","summary":"Specifies the receipt as a thin layer with an explicit non-goals list — no credentials, no raw bodies. Positive, and an independent statement of the redaction rule applied to shape previews and logged requests here.","claim_ids":["c6"]},{"id":"s20","type":"runtime_receipt","url":"https://miscsubjects.com/api/dispatch?registry=1","title":"Row counts by type, taken from production D1 on 2026-07-26","quote":"fn 480 | http 303 | agent 57 | flow 51","summary":"Method: npx wrangler d1 execute loop-content-spine --remote --command \"SELECT type, COUNT(*) AS n FROM directory GROUP BY type ORDER BY n DESC;\" run from the repository root, database name read from wrangler.toml. Totals 891. Rerunnable by anyone with the binding.","claim_ids":["c1","c3"]},{"id":"s21","type":"runtime_receipt","url":"https://miscsubjects.com/api/directory","title":"Credential forms and registry hygiene across all 891 rows","quote":"(none) 636 | headers: 139 | bearer: 68 | basic: 45 | query: 2","summary":"Two SQL statements published in the article: one grouping rows by the prefix of the auth column, one counting input_schema, examples, disabled and sensitive rows. Results: 115 credentialed rows referencing 12 distinct auth specifications, 256 with input_schema, 63 with examples, 13 disabled, 227 sensitive, 110 categories.","claim_ids":["c13","c6"]},{"id":"s22","type":"runtime_receipt","url":"https://miscsubjects.com/receipt/inv_c23irnzhx1","title":"Receipt for the first invocation of a capability created minutes earlier","quote":"\"ok\": true, \"ran\": true, \"result\": \"HTTP 200:{...\\\"temperature_2m\\\":15.7}\", \"invocation_id\": \"inv_c23irnzhx1\"","summary":"Method: POST /api/directory to create ZZ_TEST_TEMPERATURE, then POST /api/dispatch with body 37.77|-122.42, timed with curl -w. 3.126264 s wall clock including the upstream call. The row was deleted afterwards; the receipt still resolves and still reports confirmed:true.","claim_ids":["c15","c4","c5"]},{"id":"s23","type":"runtime_receipt","url":"https://miscsubjects.com/api/dispatch?key=GROK_MODELS&format=markdown","title":"Contract size, measured across four rows of four different types","quote":"NOW 4423 bytes | GROK_MODELS 4413 bytes | ROUTER 4442 bytes | CONTENT_SEARCH 4507 bytes","summary":"Method: curl -s \"https://miscsubjects.com/api/dispatch?key=<KEY>&format=markdown\" | wc -c for each key. Under 100 bytes of variance across a fn, an http, an agent and a flow row. The same registry fetched whole is 1,608,554 bytes for 877 objects.","claim_ids":["c8","c9"]},{"id":"s24","type":"runtime_receipt","url":"https://miscsubjects.com/api/dispatch?confirm=inv_m6c161ry9u","title":"Which row edits change the contract fingerprint, measured by three invocations","quote":"baseline fcb5a4d6ccdd5529... | after examples edit fcb5a4d6ccdd5529... | after target edit da066c3042312313...","summary":"Method: invoke the row, PATCH one field, invoke again, and read invocation.fingerprints.contract from each response. Editing examples left the SHA-256 byte-identical; editing target changed it. Establishes that the hash tracks the callable contract and ignores documentation-only edits.","claim_ids":["c14"]},{"id":"s26","type":"runtime_receipt","url":"https://miscsubjects.com/api/directory","title":"The production CREATE TABLE and column list, read back from D1","quote":"CREATE TABLE directory (\n  key        TEXT PRIMARY KEY,\n  type       TEXT NOT NULL CHECK (type IN ('fn','http','agent','flow')),","summary":"Method: npx wrangler d1 execute loop-content-spine --remote --command \"SELECT sql FROM sqlite_master WHERE name='directory';\" and PRAGMA table_info(directory), both against the remote database. Eighteen columns; comparing them to grep -rn \"ALTER TABLE directory\" over the repository shows created_at has no migration behind it.","claim_ids":["c2","c3"]},{"id":"s25","type":"repository","url":"https://github.com/cloudflare/workers-sdk","title":"cloudflare/workers-sdk — wrangler, the tool every measurement here was taken with","quote":"wrangler","summary":"The CLI behind npx wrangler d1 execute --remote. A reader gets the source for the command used in every first-party measurement on this page, so the harness is inspectable rather than asserted.","claim_ids":["c1"]}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"directory-row-contract","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":15,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":15,"claims_total":15,"sources":26,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}