| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
First slice of the il product CLI: the ontology-registry verbs. Ontologies live in a Helm-style registry (inputlayer/ontology-registry); il is the installer and deployment rides the existing WebSocket API. il search [term] browse the registry index il fetch <name>[@Version] download + sha256-verify into ~/.inputlayer/ontologies il install <name>[@ver] --kg X fetch, deploy as ONE atomic execute program, pin pack_meta(name, version, digest) in the KG il list --kg X show pinned installs via pack_meta Design decisions carried from the registry design doc: - Deployment is a single multi-statement execute message, so pack loads are atomic (phase-1 parse rejects the whole program) and immune to the per-message WS rate limit that statement-by-statement .load hits (#92). - A digest mismatch between index.json and the downloaded tarball is a hard refusal: rule packs are trusted laws, so integrity is not optional. - Private registries authenticate via IL_REGISTRY_TOKEN/GITHUB_TOKEN; GitHub release assets on private repos resolve through the API asset endpoint when the browser URL 404s. - pack_meta pinning makes every finding attributable to an exact, verified rule set and gives il list its data. Verified end-to-end against a local server: search/install/list against the live registry, then conflicting claims deriving a functional conflict with quoted spans through the installed pack. No server changes; new deps (tar, flate2, clap env feature) are confined to the client side of the crate.
#98 branch) (#109) PR #98 was merged while its branch kept receiving work; these are the orphaned improvements, re-applied onto main as one change: - il migration generate/apply/revert/status: il owns the migration vocabulary (helm repo pattern); the delegation layer translates each verb to the Python tool's subcommand, so 'il migrate migrate' never exists. Leaf commands pass --help and flags through. Integration tests pin translation, passthrough, exit-code propagation, and the missing-tool hint (7 tests). - Review hardening (adversarial review findings): install scans deploy and pin results for the engine's soft errors ('Insert rejected', 'Failed to register schema', ...) and verifies the pack_meta pin with a read-back query; cache writes are staged and renamed with digest files, cache hits digest-checked (republished versions refetch); auth token only sent to GitHub hosts or the index host; registry names/versions charset-validated; HTTP timeout; unsolicited WS error frames skipped; scheme-less --server defaults to ws://; il list only reports 'no managed installs' for unknown-relation errors.
| Back | FazBrowse Home | New Git URL |
What
First slice of the il product CLI. Ontologies live in a Helm-style registry (inputlayer/ontology-registry); il is the installer, and deployment rides the engine's existing WebSocket API. Zero server changes. il is the single CLI: everything is a subcommand, including migrations.
How
Tested
Not in this PR
The gateway milestones (#83/#84) and il verify / il demo; this PR is deliberately the smallest registry-consuming slice.
Notes for review