ObneyAI/orc / orc-skills/orc-model-sio
orc-model-sio
VerifiedConfigure 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.2 KB |
| references/complex-model-portability.md | markdown | 8.8 KB |
| references/configured-model-fallback.md | markdown | 8.9 KB |
| references/contract-preflight.md | markdown | 2.9 KB |
| references/input-field-guide.md | markdown | 4.4 KB |
| references/live-findings.md | markdown | 11.6 KB |
| references/model-portability.md | markdown | 30.9 KB |
| references/paired-function-profiles.md | markdown | 5.1 KB |
| references/portability-proof-boundaries.md | markdown | 6.1 KB |
| references/reasoning-and-completion-budgets.md | markdown | 11.7 KB |
| references/retained-fallback-profiles.md | markdown | 9.8 KB |
| references/scoped-model-alternatives.md | markdown | 11.2 KB |
| references/structured-contract-repairs.md | markdown | 22.3 KB |
| references/structured-output-boundaries.md | markdown | 6.9 KB |
references/contract-preflight.md
View on GitHub# Preflight the actual generation contract
Use this before the first paid run of a new authored tree, especially when a deterministic test replaces the AI executor. That replacement bypasses module building, provider schema compilation, parsing and adapter options. Passing it does not prove those boundaries.
Run the actual public workflow builder against the owned datastore before taking that inventory. Replacing `build-workflow!` with an ID-returning fake can let strict schemas compile while registration still fails. At the4966c8e pin, an explicit retry record needs both fields, for example `{:max-attempts 1 :backoff-ms [0]}`, and node names must be unique within a sheet. A later fresh-author transfer exposed both omissions before any provider call. Keep registration, strict compilation and live execution as distinct proofs; do not call a captured definition a registered node.
First inventory every registered generation node, its sheet/node identity, configured provider alias, effective requested model, and effective output mode after node/provider configuration. Check that the inventory matches the intended tree; a zero-node scan or a scan filtered only to explicitly strict nodes can hide omitted configuration. Record why a non-strict mode is intentional when using one. This does not make strict mode mandatory for every provider.
On a checkout containing the documented structured-contract repairs, compile every distinct registered strict generation node's actual module with `sio.structured-output/compile-contract`. Build the module with `executor/build-module` from that node and its actual sheet blackboard (`get-blackboard-by-key`). These are source-pinned diagnostic APIs; inspect the consuming revision rather than assuming public stable support on mainline. Retain the compiled schema and node identity. This is a zero-provider-call check.
Strict mode rejects an open nested object. A vector of edit records needs a concrete item schema such as `[:map {:closed true} [:path ...] [:version ...] [:content ...]]`; naming/describing the fields does not close the object. Close authored fixed-field objects recursively when strict output is intended. Do not strip unknown output, invent required fields or duplicate the schema in task prose to conceal an invalid contract. An intentionally open dictionary requires a supported representation/mode, not an automatic closure that changes its meaning.
If the compiler seam is unavailable, exercise the real request-building and response-parsing boundary against a controlled transport. Do not replace the executor again and call that provider validation. Keep this check focused on the current tree's contracts. It establishes request compatibility, not semantic correctness, model availability, or complete context. The live run must still verify exact serialized field meanings, actual responses, projected outputs and task achievement.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |