Repository navigation
chore(OMN-20837): omnidash names the renamed public repository knowledge_base - #383
Conversation
…dge_base Ticket: OMN-20837. Repoint live references at OmniNode-ai/knowledge_base after the repository rename; history documents keep the old name.
|
OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required. Considered 7 changed file(s):
This verdict is occ-autobind's, derived from this head and its merge base alone. A second producer, the occ-companion-effect backstop, consumes its own command on the lab bus and may still mint a companion under the generic binding. Whether it does depends on that consumer running, not on this diff (OMN-18876). |
|
Lab: head=b7c82e5b51697778d051c71bdadb6649f730148b Base update
Lab proof
|
|
OCC autobind rebound this PR's evidence-source stamp line to The receipt gate's own eligibility validator, run against the change-control tree the gate pins for Reported by |
Summary
The public repository OmniNode-ai/knowledge-base was renamed to OmniNode-ai/knowledge_base on 2026-10-09 (operator instruction, OMN-20837). GitHub redirects the old URL, so nothing breaks before this lands. This change points every live reference in this repository at the new name.
Dated history (ledger rows, handoffs, evidence, captured fixtures, recorded receipts) keeps the old name.
Changes
Test plan
Lab: this is a documentation and configuration rename with no runtime effect on any lane; the old repository URL keeps redirecting.
Ticket: OMN-20837
Evidence-Ticket: OMN-20837
Evidence-Source: OCC#13509