Repository navigation
Description
Goal and acceptance
Contribute English, source-grounded operating guidance for lithos-ai/lithos-metal using the AREX-Skill create-repo-skill and verify-repo-skill workflow, adapted to InferRSI's knowledge ownership and candidate-state contract.
Completion criteria:
- Pin the inspected upstream revision and preserve readsets, source license/notices and mechanism limits.
- Cover Metal task compilation/fusion, GPU-resident generation and DSpark state, and serving/cache validation in a reviewable skill graph.
- Integrate navigation, catalog discovery and both knowledge matrices; verify packaged access and applicable CPU/static checks.
- Preserve native-backend/model verification gaps, and obtain independent revision-scoped review before proposing readiness.
Scope and constraints
Source-derived candidate guidance only. No performance claims, campaign PASS, model downloads, runtime engine integration, new CI lanes or default numeric acceptance gates. No changes to existing experiment evidence. Metal and full-model qualification remain explicit if not run.
Source: https://github.com/lithos-ai/lithos-metal at 6653b7df5f2c4392ec7b038960f2796b1499923f.
Method: https://github.com/VectorSpaceLab/AREX-Skill at ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6, create-repo-skill / verify-repo-skill.
Ownership and authorization
The human requester explicitly asked in the Codex chat to distill this repository and contribute the result to InferRSI, and identified AREX-Skill as the workflow source. This authorizes preparation and a contribution PR. The accountable parent is the Codex agent in that chat. The requester subsequently confirmed the three-part scope and candidate-only delivery, explicitly accepted unrun Metal/full-model verification as a stated limitation, declined automatic large-model downloads, and delegated remaining details. The scope is accepted for implementation and a contribution PR. Merge and Issue closure are reserved for the authorized owner; proposal of this Issue grants no additional authority.
Completion and closure
Use non-closing Refs from the delivery PR. Report PR readiness separately from goal acceptance. The Issue remains open for owner acceptance; native performance/quality validation is not a criterion of this knowledge-only contribution unless explicitly added by the requester.
Activity
Dong1017 commentedon Oct 23, 2026
Issue-owner takeover: complete the existing Lithos Metal contribution
The requester explicitly delegated takeover of Issue115 and its existing PR #117 to this Codex parent on 2026-10-29, through source-scope acceptance and evidence-based closure. I am the accountable Issue owner for this continuation. The original contributor's work and revision-bound evidence will be preserved; the stopped local overlapping draft remains inactive.
The accepted scope remains the pinned Lithos Metal candidate graph: compiler/fusion, GPU-resident generation and DSpark state, and serving/cache guidance. Native full-model, numerical, quality or performance qualification is outside this source-only acceptance.
6653b7df5f2c4392ec7b038960f2796b1499923f, retained licenses/readsets, the four-node graph, existing consumers and the original source review. Keep earlier CPU and synthetic Metal reports attributed to their original author and tested revisions.7d1d82f55cda89842bd23ee2da91b521ee60eb08, preserving all accepted canonical owners, registry/matrix additions and resource contracts. Commit the combined canonical source before regenerating native projections from that actual source. Resolve real inventory-test changes without relaxing per-record checks.Refs #115, and publish truthful final-head author/declaration and verification records. New material/integration authorship uses an actual fresh Sol/max instance; the original Sol/xhigh authorship remains historical and is not relabeled. The PR enables maintainer edits; the branch-specific publication path will be checked before updating it.This continuation uses PR #117 and creates no duplicate delivery PR. No model downloads, dependency upgrades, new Metal/GPU/model/provider experiments, engine integration or evidence promotion are included. Existing incomplete or unrun claims retain their actual limits.
Original claim and duplicate-avoidance update (retained)
Update (2026-10-23): PR #117 now covers this accepted source-distillation scope. Following the requester's duplicate-avoidance rule, we have stopped our local overlapping draft and will not open a second contribution PR for this target. The PR author's verification reports have not been independently rerun in this task. The Issue remains open for owner acceptance.
Claiming this source-distillation contribution at the requester's direction. I will deliver an independent PR using lithos-ai/lithos-metal@6653b7d and AREX-Skill@ac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6, covering the three accepted areas: Metal task compilation/fusion; GPU-resident generation and DSpark state; serving/cache validation.
The deliverable will retain English candidate guidance, pinned readsets and license/notices, integrate the existing owners/catalog/matrices, and include applicable CPU/static and packaged-resource checks plus independent revision-scoped review. Unrun Metal/full-model checks will remain explicit; no model downloads or performance qualification are included. The contribution PR will use a non-closing reference, and this issue will remain open for owner acceptance.
Dong1017 commentedon Oct 29, 2026
Accepted: Lithos Metal source-grounded candidate knowledge
flowchart LR A["Pinned Lithos source + AREX method"] --> B["Compiler / fusion"] A --> C["Generation / DSpark state"] A --> D["Serving / cache lifecycle"] B --> E["Owner-local candidate graph + packaged discovery"] C --> E D --> E E --> F["Source, CPU and package checks verified"]ab03f3ff. One registered Lithos owner and three local subskills preserve pinned readsets, licenses/notices, navigation, both matrices and a bounded diagnostic.Full acceptance record
The delegated Issue owner accepts all four completion criteria in the current Issue's source-only scope, under the published takeover plan.
6653b7df5f2c4392ec7b038960f2796b1499923f, AREX methodac3fe1afa80fb9a09775ecfb2b6cc3ba850a2db6. The independent reviewer matched the license/notice blobs and inspected the source contracts.Revision binding: assessed main
7d1d82f55cda89842bd23ee2da91b521ee60eb08; real canonical source M26743abcfae48cd6223bd757e74f193d97e3e5a7; native generated Geebd09469ca9a28fd50dc6da7c4dd90485ce17b1; final reviewed/public head T2709a51bee9f5e27328d24b0a07dc30c6e13fe27; actual squashab03f3ffb8f2e5bc02c304828c5c41890eef673e. The squash tree76830cf6f5686d6800b85afcf1a2164ecbbdf3c0equals T's reviewed tree and has the assessed main as its parent. All 540 committed source inputs match the native projection; all 76 prior discovery records retain their semantics.Execution boundaries: the local wheel and 27 focused tests ran on G; T only removed three inherited test-module descriptions, with independently verified executable-AST equality and identical package/source/generated bytes. The final T has its own complete Ready checks and clean-wheel runs. Local private validation reused the existing real PyYAML 6.0.3 distribution with byte equality; it installed no upstream runtime or new model dependencies.
The current Skill evaluation advisory reports zero comparisons, zero model calls and 111 uncovered paths. Plan/publish succeeded; execute was conditionally skipped and is not counted as a pass. Pricing/budget limitations were not bypassed. These gaps provide no efficacy evidence and do not add a provider/device requirement to the accepted knowledge-only criteria.
The original 153 upstream CPU, nine synthetic M4 Metal and 697-suite numbers are retained historical author reports, not reruns on this integration. Actual material authorship remains original Sol/xhigh plus new Sol/max; review-only Sol/ultra is excluded from material-author declarations. No campaign PASS, production readiness, model quality or performance acceptance is claimed.