Skip to content

ObneyAI/orc / orc-skills/orc-model-sio

orc-model-sio

Verified

Configure ORC models and structured I/O, inspect SIO or native decision-client requests, and diagnose provider or parsing failures. Use when model choice or what was sent to a model matters.

references/paired-function-profiles.md

View on GitHub
# Paired response-function request controls

## Source status

This describes a private, unreleased ORC/SIO campaign candidate. It is a staged skill reference, not installed or fresh-agent validated. Verify the consuming library and SIO/client revisions before using the API. The new profile is explicitly selected with `:output-mode :function-calling` in normal node options or provider configuration. At this inspected candidate it is implemented for the OpenRouter adapter; switching vendor model names through that adapter differs from switching to a direct vendor adapter. The legacy `:use-function-calling?` preference is a different path and has different conversion behavior. Do not equate the two.

## Keep one typed contract

The new paired function profile uses the same rich compiled output schema and original-value decoder as the paired strict JSON profile. It retains nested meanings, colliding typed map keys, typed dictionaries and optional nullable presence. Exactly one named response function with a string argument body is required locally. Missing, wrong-name, multiple, malformed, refused, truncated or schema-invalid output fails with typed evidence; plain text and wrapper strings are not alternate success paths. Do not add application unwrapping or per-model coercion.

The private candidate requests automatic tool selection by default and supports explicit named forcing as a separate caller choice. Endpoints may advertise tools while rejecting required or named selection. Check the advertised choice subtypes and actual admission response, not just a tools capability boolean. A missing automatic response call is a parsing failure; a missing explicitly forced call has its distinct forced-call failure.

The shared candidate also sends `function.strict:true`. Call obligation and argument constraint are separate: automatic selection does not force a call, and tool support alone does not establish schema enforcement. Local paired validation remains mandatory even when the request asks for strict arguments. In a later fixed-route contrast, an endpoint still returned an undeclared argument wrapper despite that flag. The flag requests a constraint; it does not establish that the hosted endpoint honored it. A conforming draw also cannot prove every future response will conform. Do not silently drop a rejected constraint, switch to markers, or reinterpret an invalid response. Generated guidance must describe function arguments; strict JSON guidance instead describes a JSON response. Preserve authored meanings and the identical compiled schema in each presentation.

## Interpret observed differences

Common source-copy probes sent identical requests apart from model name. The nonstrict function round had an undeclared string wrapper rejected locally; the strict round observed valid schemas in all eight responses, while some answers still changed the permitted source string `"null"` to permitted null. A pinned strict-JSON observation on the same reported provider/fingerprint preserved that string correctly. These are narrow observations, not universal enforcement, model rankings or proof of a specific hidden parser defect. Requested route, resolved provider and response mode matter.

Trace native input -> actual serialized request -> upstream argument/content string -> paired decoder -> canonical producer and consumer values. When the upstream answer already contains the wrong allowed value, decoding fidelity and task fidelity differ. Preserve the failure and use a controlled same-contract response-mode or pinned-route contrast. A schema cannot enforce input-dependent copying merely by permitting several valid types. Never replace nullable values with gold-value enums or remove legal null/absent cases to manufacture a pass.

The inspected private ordinary path now retains the effective fallback plan and has independent SQLite/request/restart evidence. Researcher paths remain separate: a real recursive prime fixture completed successfully while its backup silently switched from inherited paired function mode to markers. Read [retained fallback profiles](retained-fallback-profiles.md) before relying on registry changes or recovery. Ordinary acceptance does not establish researcher or all-role recovery.

## Proof scope

Independent focused predictor/SQLite verification passed fifteen tests and 226 assertions for the strict-tool request change. It covers ordinary explicit/inherited profile selection, exact projected values, streaming refusal and envelope/schema rejection controls. Common model probes are one packet/draw each; they do not cover every condition/decision/researcher role, multi-step tools, concurrent users or general-agent outcomes. The broad role/model/fallback obligations remain open.

A completed minimal two-route/two-mode contrast preserved all required/optional nullable controls under strict JSON on both requested routes. Function mode on one route changed permitted source strings to null; another route returned an undeclared wrapper. Exact backend generation/template/parser cause remains unresolved. This supports choosing and verifying a common standard profile, not introducing per-provider unwrapping or claiming a universal successful mode.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall