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/input-field-guide.md

View on GitHub
# Input meanings at the model boundary

For a checkout containing the **unreleased structured-contract repairs**, read [the verified repair path](structured-contract-repairs.md) before applying historical parser/metadata limitations below. It covers generated model-visible output meanings, paired strict parsing, null preservation and execution-owned provider observations. Verify the loaded revisions; these APIs are not assumed to exist on mainline.

The private model-contract candidate adds a shared **declared input contract** supplement automatically through ORC's ordinary generation, function, strict JSON and native finite-decision request paths, and SIO's marker/stream request construction. Authors keep using described blackboard schemas and normal model configuration; they do not call a compatibility helper or write per-model parsers. This is separately verified private source, not released support at the historical pins below.

For each supplied input, shown values remain distinct from the labeled declared contract. Nested optional children, empty collection item schemas and nullable-container meanings remain described even when there is no child value to display. An absent top-level input is still absent; a declared optional child is not evidence it was supplied. Shared descriptions use scope-qualified references rather than duplicating ambiguous meanings.

The candidate resolves common raw and compiled Malli maps, local registry aliases, schema/ref wrappers, containers, nullable/union types, conjunctions and literal/comparison constraints. Recursive declarations use finite references. Unknown custom structures and regex sequences are explicitly not expanded; do not infer arbitrary-Malli support. Named-wrapper JSON key collisions remain rejected. The value codec and optional/null identities are unchanged. Verify loaded source hashes and actual requests before relying on this behavior.

Historical evidence follows; its shown-only limitation is not the candidate's behavior.

Verified experiment stack: ORC `9f7c27357b9f9bcf765fbd86baaedf5911261cd8`, SIO `a6013e524f36b0b1e9e49cc270c7e1de8a097c36`. These were local input-field-guide branches, not a claim about every released ORC version. Inspect the actual resolved dependencies and loaded namespace resources before applying this status to an application.

On this stack, marker prompts and function-mode messages include a guide to the shown input fields, including nested map/collection meanings. Native finite decisions include the guide in question instructions; input values remain state. Absent nested fields are omitted, present null is distinguished from absence, and optionality does not change the literal key name. Model-facing descriptions belong in the schemas rather than being redundantly pasted into every node instruction.

The authored-tree live run used meanings present only in field descriptions: a cargo code denoted refrigerated samples, and a nested sensor used a reverse depletion scale. Ordinary generation and native choice requests contained those meanings; the returned interpretation was refrigerated/low. This proves those exact requests and cases, not universal model understanding.

Check the complete path:

1. Declared input key and nested Malli descriptions.
2. Current delegated native value, including absence/null and source version.
3. Executor module and serialized values (complex inputs are serialized once).
4. Exact final request: messages/tool schema or native state/questions.
5. Raw response, parsed value, node completion and public value-log readback.

Output formatting is a separate contract. A reproduced optional-string marker case at this stack instructed JSON output, received `"REF-24"`, and retained quote characters in the parsed string. That can repeatedly fail an exact identity check even though the model followed the instruction. Inspect the original output schema, wire schema and parser before changing prompts or stripping characters. Supported function calling produced the correct scalar in the paired real workflow; configure and verify that mode if appropriate. This is a scoped alternate path, not proof the marker defect is repaired.

Historical missing-description findings remain valid for their old pins. Reproduce at the current dependency graph instead of carrying an obsolete workaround forward. A successful schema/module construction is not proof of request visibility or correct output parsing.
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