G10: Prove versioned harness-protocol compatibility and deliver the evidenced Responses subset #181
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
Reference
Creatidy/scarcity-router#181
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Product owner: Scarcity Router; G10/G04/G13. Source: Creatidy architecture v1.0 (2026-10-04), sections 1-5, 7-13, 14-18 via #173. Establish an evidence-backed combination matrix and implement the already accepted future Responses adapter only for a supported semantic subset, reusing the authoritative routing core.
Why and Evidence
At develop
8d9d4b04bcb23fe19ff702b6209fbcb1537cdf1b, gateway implements Chat Completions, not/v1/responsesor Anthropic Messages. D-056 explicitly accepts a future Responses surface; no dedicated executable delivery issue was found.CompatibilityCelland provider/Codex evidence exist; worker code negotiates v4/v3/v2/v1, v3 gates client-tool suspension/continuation and v4 preserves reasoning. Names 'OpenAI-compatible' and 'Codex' do not prove arbitrary protocol/harness/version compatibility. Existing Codex PARTIAL continuation includes an owner-accepted lossy success mapping (D-062), not a universal tool contract.Scope
Freeze actual version combinations (harness + harness adapter + ingress protocol + Router adapter/source/runtime) and supported semantic features. Re-evidence official Responses protocol at exact revision and map roles/history, tools/results, continuation, reasoning, stream/usage/cancel, output/context/identity and error semantics. Deliver Router Responses adapter over existing semantic/core seams only after proved mappings and versioned decision. Anthropic Messages coverage is an explicit evidence/unsupported disposition, not automatic commitment to a new endpoint. No fake conversion by flattening history, dropping parameters or claiming all harnesses.
Acceptance Criteria
Dependencies, Reuse, Priority and Authority
After #174/#175/#179 semantics; contract research may run independently. Reuse current wire translators, semantic conversation structures, suspended continuation, typed errors, compatibility cells and worker-version gates. Evaluate selected LiteLLM translators/tests before BUILD, not whole-platform adoption: exact revision/files/license/attribution, semantic refusal tests, security, dependencies/maintenance; separate code license from provider/service/data terms. Kernel/harness adapter consumer counterpart not found at registration.
Priority: integration coverage after exact-route/identity fixes, not an indiscriminate P0. Existing #165 owns concrete cancellation defects; link its evidence rather than duplicate fixes. Refs #173, #146/D-056, #137/D-062, #158/D-064. Future evidence may need running harness/provider/Router, separate inference/effect authority, and owner approval of lossy mappings or incompatible contracts. Registration authorizes none.
Canonical counterpart: Creatidy/creatidy-kernel#47 separately proves harness-control and backend/API compatibility, #53 implements the proved lifecycle and #52 receives gateway routing. MI public execution-surface evidence is Creatidy/model-intelligence#12 plus #14 identity/calibration, not runtime proof. Link exact combination/version evidence rather than borrow a guarantee from protocol names. Router retains ingress/translation/source producer ownership and the already accepted, evidence-gated Responses subset; Kernel owns harness adapters. All counterparts OPEN.
Owner decision 2026-10-05T16:41:45Z in SAME /loop invocation 2026-10-05T12:38:32Z: #179 can close its deterministic Router identity/effort correction after normal gates/review. REAL_HARNESS_IDENTITY_ACCEPTANCE remains a separate OPEN gate linked to #174/#181 for separately authorized version-pinned real-harness acceptance. Preserve honest UNKNOWN/unattested physical identity and requested/resolved/dispatched/observed distinctions; no synthetic or dispatch echo promoted to observation. #180 still gates affected workspace-editing lanes. No live inference or deployment authorized.
Selected under Adrian's resumed /loop after explicit owner pause of209 (2026-10-25T06:21:23Z), not as a waiver of its finding or any unrelated security gate. Full fresh canonical14-issue queue paged to exhaustion; exact wontfix exclusions132/139/140/141/165/166 only.185 is expressly owner-paused;176's activation/admission/compatibility gates remain stage-specific; read-only177 research established actual missing whole-path producer contract fields at Kernel e1aca78 (18801), without inventing185 as its prerequisite.181 is the oldest remaining predecessor-satisfied implementation/proof candidate:179 formal dependency and175 semantics are integrated, and174 producer is now actually integrated at current develop
c38c8ae5390e27b9bfb9ae210b76d6efa89a2d36, with exact tree+postmerge129 tests and separate live Kernel52/#181 gate retained.183 retains140 correctness prerequisite;186 retains139/141/185;199 actual replacement+retirement gates;214 completed offline portion is not repeatedly reimplemented. All unranked candidates use required ordering/age, not guessed priority.Delivery begins with exact official Responses and selected LiteLLM source/version/license/semantic proof, current GatewayRequest/stream/continuation/core capability mapping, then a bounded versioned subset decision before code. Unsupported/lossy/unproven fields and surfaces must refuse, not flatten/erase/claim universal harness support. No private Kernel/MI state, credentials, live models/provider effects, deployment or cross-repo mutation. No new selector/service or tool executor; current174 binding/identity and old Chat/recommendation behavior must survive. Anthropic ingress remains explicit unsupported/evidence disposition.
Scope/threat/expected budget: one ingress codec/wire response path over existing authoritative gateway semantics plus focused producer-shaped synthetic protocol/security/refusal/compatibility tests and in-place docs; no generic gateway/harness framework or new runtime dependency assumed. Default finite10 whole-PR reviews retained, no prior181 review/PR known. New authenticated execution ingress/input semantics is security_critical: normal independent fresh native ordinary review, then the existing owner-manual Daybreak gate remains applicable unless this delivery gets its OWN explicit exception; the204/209-only exception is NOT generalized. Technical preflight/contract consultation is not a formal review. No code before actual source feasibility/contract freeze; a proven unmet preimplementation contract returns to SELECT without speculative code. Branch issue-181-responses-subset from freshly fetched
c38c8ae.Bounded source/semantic proof before implementation: official openai-python3.37.0 at
718aee979a9c334d37302aeff21cee6cbff4d43c, MIT LICENSE blobcbb5bb26e40dd13a02c7874298f70b9d68bab57e; LiteLLM1.108.0 atdddbaa803d6e9fcc862ea7a5412f771cb1ae040e, selected base MIT LICENSE blob3bfef5bae9b48c334acf426d5b7f21bc1913aab9 (enterprise code not selected). Exact source files/typed events/negative tests inspected from private read-only source checkouts only, no dependency install/import/adoption/provider call. Initial clone workdir mistake recovered by verified existing parent, no architecture/tooling issue or owner ask.ADOPT before BUILD outcome: reject whole platform/runtime/dependency and verbatim translator port. Selected transformation.py981-1097 has drop_params/provider-dependent summary/tool behavior;1735-1814 recovers/reconstructs missing calls with guessed empty arguments;3610-3699 emits zero usage/details when absent; session/stream helpers own stored response lifecycle. These conflict with strict refusal, unknown!=0 and Kernel-owned lifecycle. Use original code over already-owned semantic DTO/coordinator/adapter/continuation primitives, based on official wire facts only; no substantial foreign code copied/adapted or new runtime library.
Freeze initial Responses surface1: explicit store=false/stateless full input; str->documented user message or explicit roles/single text part; real ordered function calls/results/call_id; existing effort controls only; max_output_tokens->actual output ceiling; typed text/json_object/json_schema formats; coherent current174 requirement/pin context passed unchanged into existing core. Streaming maps normalized text, complete functions and opaque reasoning into exact typed SDK events (reasoning_text, NOT fabricated summary), sequence IDs/terminal/error before success; no second dispatcher, selector or harness lifecycle. Existing canonical backend RequestBinding.protocol remains its semantic execution protocol, never rewritten in retained context to hide a mismatch. Unknown/unsupported formats fail before inference; current legacy Chat contract unchanged.
Explicit unsupported: server store/retrieve/background/previous_response_id/conversation/item_reference; hosted/native client tools; phase, multi-part/multimodal content, instructions role ambiguity, reasoning summary/encrypted state/reinjection and unimplemented controls. Full concrete IDs are non-authority annotations, not server lookups/call_id aliases. No lossy history flattening, guessing missing tool lineage or stripping context. Full helper/native continuation IDs remain opaque.
Official ResponseUsage requires cache-write/cache-hit/reasoning breakdown unavailable in current semantic accounting, so usage=null rather than invented zero; actual known aggregate/source/accounting retained in explicit x_scarcity_router provenance. Output phase never invented; opaque reasoning response text preserved distinctly but replay unsupported exactly as existing D064. Source-matched synthetic protocol cells are not executed SDK/live Kernel/physical/billing proof. Anthropic ingress stays unsupported.
D080 will record this selected bounded additive contract/version/compatibility and refusal/upgrade semantics before code. New authenticated ingress is security_critical: default10 ordinary invocations and existing owner-manual Daybreak remain, no204/209 exception generalized. No activation/deployment/live data/effects. Owner-controlled incompatible/lossy choices are avoided by explicit refusal, not silently decided.
Original bounded Responses implementation is now in progress on issue-181-responses-subset (basec38c8ae), D080 frozen before code. No external code/dependency imported/adopted. New wire normalizer/payload/event codec reuses owned strict semantic parser and one actual coordinator/adapters/continuation/audit path, not an HTTP Chat proxy/second selector or harness. Existing client-facing wire/body semantics remain separate from canonical backend binding protocol; hard retained mismatches refuse, not rewrite.
Implemented stateless store=false request/refusal boundary; explicit roles/single parts, real complete function lineage, strict functions, generation/format/control mappings and UTF-8 finite JSON; explicit model/context/catalog-effort preparation plus final require_bound verification through reused D079 helper (initial manual test field-copy failed precisely because it lost effort, so production path automates instead). Response text/reasoning_text/functions/statuses and typed SSE sequences/items/final/error outcomes, never summary/phase invention, fake success or usage-detail zeros. Known accounting remains scoped in x_sr; standardusage null. x-should-retry:false on Responses errors, SDKmax_retries0 advised for preheader loss. Decoded-string credential guard handles escaping and keys without logging values. Wire-output refusal propagates existing cancellation with distinct failed-delivery audit reason. No server executes client functions or stores/retrieves response history.
Actual focused result:186 tests PASS across new codec/real loopback JSON+SSE/auth, legacy gateway, existing continuation,174 executable and frozen-interface cohorts; standalone basedpyright0errors/warnings/notes, whitespace PASS. New25 cases include real disconnect via bounded event handshake, no false completed stream on mapping/loss/cancel, unknown/partial accounting, exact binding/effort, malformed/state/phase/reasoning/multimodal/history/input/UTF/refusal and no adapter calls on unsupported input. Synthetic source facts only, no account/credentials/live inference/deploy/private export. Routine fixture/type mistakes corrected without weakened tests or owner prompts.
Dated source-matched compatibility/ADOPT-vs-owned decision evidence added in existing docs: officialSDK3.37.0@718aee / LiteLLM1.108.0@dddbaa; explicit PARTIAL/UNSUPPORTED/UNKNOWN live/harness/Anthropic/native-replay cells, licensing/reference-only evidence. Full repository/type/package gate next before commit/PR/independent ordinary review. Default10 whole-PR invocations; none dispatched/reserved yet. This new authenticated ingress remains security_critical with separate owner-manual Daybreak after ordinary approval;174/185-only exception is not generalized.209 remains owner-paused unchanged,204accepted tree preserved.
Continuation delivered PR218 through exact ordinary approval, not merge/closure. Current HEAD
bc7bc40647b5284f3c2f22081d384679d28ac4a8, base/merge-basec38c8ae5390e27b9bfb9ae210b76d6efa89a2d36, tree5f069f57ccccb264ff234f8a8c50cc024e3b67b3. Fresh independent completePR #5 APPROVE/findings[]/limitations[], native session ses_e8c149f9affe7Ox1clsQfk8xfA/result18849. #1–4 actual findings corrected with red-green regressions/full gates, outcomes/counters preserved. Current43Responses/full2967tests17skips/zero basedpyright/package/whitespace PASS. Owner-manual official Codex Daybreak #6 reserved PENDING/UNCONSUMED at exactrefs; source/checkout preserved, no automatic invocation or exception transfer. PRopen/unmerged; real installed-harness/provider/physical/billing acceptance remains unclaimed.Fresh FULL canonical repository queue refreshed in bounded pages1–7(14issues),page8empty. Exact wontfix exclusions132/139/140/141/165/166 only. Remaining176/177/181/183/185/186/199/214 bodies/comments/relevant dependency stages rechecked; no open-status-only gate, no new speculative work.
-181: now ordinary-approved; actual owner-manual security action above gates integration, not lack of session infrastructure or test failure.
-185: owner explicitly paused selected209 investigation; canonical209 remains HEAD12e54397/open/unmerged, actual16REQUEST_CHANGES/P2 and17–18unused/max18 unchanged. #174 producer already integrated; no backward downstream gate.
-176: actual MI publication still
d65891668b7e79f7b666c021f02a1b4bf8c4ca9c(fresh public Git remote), not missing. #185 compatibility before activation and issue-required explicit private admission/calibration/freshness approval remain; downstream MI19/Kernel55 do not gate research. Existing source study complete, research not claimed impossible and no unused parser invented merely to sustain loop.-177: actual Kernel still
e1aca78b0e56afffb245005e25ecb7b155a8367a(fresh public Git remote), unchanged from bounded exact source study18801. Thin task/reference/local-outcome exports and doc-only58 acceptance are not implemented full authorized role/route/call/usage/accepted-result lineage. Kernel52/56/58 actual producer fields/rights/conformance still needed for full consumer AC1–3; no fictitious missing174/185 dependency or zero usage.-183: explicit140 state-correctness prerequisite remains excluded; current accepted control_api.py1519–1530/1563–1582 still counts/iterates staticconfigresources (blob6c139024 unchanged inbase/head), so required derived-resource guarantees are not established.179delivered; Console reception is downstream, not an upstream implementation gate; no excluded140 resurrection.
-186: explicit139/141/185 ordering/platform/signing/publication authority remain. Independent public research is not called impossible; no signing/release/deploy/live permission inferred or duplicate counterpart built.
-199: exact accepted Kernel replacement/consumer/installed equivalence and explicit incompatible/destructive retirement authority still required; this issue has no such authorization/comment and current owner scope excludes retirement. Preserve D-063 lane, no crossrepo mutation.
-214: accepted offline217 phase not repeated; actual acquisition/permission/freshness/no-PAYG/native-control/live Pro gate remains separately deferred under U-015/18737. No account/paid fallback/OAuth handling or repeated synthetic-test completion claim.
This is a bounded useful-progress/security handoff, NOT product-complete, global QUEUE_EMPTY or proof that all further contract research is blocked. No additional full implementation is verified eligible without those exact current prerequisites/authority; unproved installed/live conditions stay unproved. Owner attention is required for181 security invocation, not routine tool repair.
Accepted Router Implementation Integrated
PR #218 merged through the authorized Forgejo operation as
8799899ea22c3c131cfbb8953d8461a9cb3ec9df, parents approved basec38c8ae5390e27b9bfb9ae210b76d6efa89a2d36and approved HEADbc7bc40647b5284f3c2f22081d384679d28ac4a8. Fresh Git fetch verifies ancestry and integration tree5f069f57ccccb264ff234f8a8c50cc024e3b67b3, byte-identical to the validated/reviewed HEAD; no runtime implementation was changed and no duplicate validation/review was needed.Acceptance: D-080 source-pinned, versioned, stateless Responses subset and explicit compatibility/refusal/migration matrix; one existing selection/admission/execution core; deterministic roles/history/tools/reasoning/format/stream/cancel/failure/unknown-accounting/exact-binding proofs; no new tool executor or private dependency. Native independent whole-PR #5 APPROVE/findings[]/limitations[] includes adequate correctness/security/UX coverage. Exact-head full gate2967tests/17skips,43Responses,type/package/whitespace and canonical CI3202 SUCCESS retained. #1–4 REQUEST_CHANGES remain historical consumed outcomes.
Direct owner USER2026-10-25T18:46:24Z in native session
ses_e8b9d5991ffeHiYz2c7oRH9BA2supersedes mandatory per-PR Daybreak immediately; provenance, exact #5 verification and unused #6 retirement are at PR218 comment18858. #6 is SUPERSEDED/UNCONSUMED, not security approval or another invocation. Ordinary independent PR security remains required; a final comprehensive frozen-release-candidate Daybreak audit must pass before first production release. Policy correction follows separately without modifying approved runtime code.Close #181 only for the accepted Router implementation/source-shaped synthetic conformance scope authorized by the owner. Still OPEN separately: REAL_HARNESS_IDENTITY_ACCEPTANCE linked to #174/#181, actual installed Kernel/harness consumer reception (Kernel #52), SDK runtime, live provider/account/billing/physical identity and deployment/platform evidence. These require their own authorization and exact-version receipts; closure is not a live-provider or production-readiness claim. Existing matrix UNKNOWN/PARTIAL/UNSUPPORTED cells remain honest.
PR #209 remains owner-paused/open/unmerged; its unresolved review16 SQLite transition-race finding is not deferred to the final audit or waived. No main, release, deployment or cross-repository mutation.
kilo referenced this issue2026-10-25 19:10:32 +00:00