v0.2.2
·
25 commits
to main
since this release
Fixed
lookupresolves against observed evidence, not justdeclared/.
Cadastre returnedmissing_entityfor infrastructure it had itself observed
from a fresh collector run, and the message told the caller the catalog was
wrong. The observation was retained the whole time, reachable only inside a
driftdump large enough to exceed an MCP tool result limit. Resolution is
now declared, then observed, then containment. An observed-only hit is
labelled as one, carrying its source andas_ofwithdeclared: false, no
declared_atand no relations — reachable, never promoted (DESIGN §1.3).
Themissing_entitymessage is unchanged for the case it was written for,
and now also says that nothing observed the id either. (#19)- A container inside a stack is reachable by the name a human uses.
orchestrator-gitopsemits one entity per compose stack, which is the right
altitude, but the constituent names survived only inside an attribute block
nothing indexed — solookup lokifailed even thoughgrafanalokiwas
known. Anyx-*block listing mappings with anameis now indexed as
member names. No plugin key is special-cased, no value is interpreted, and
the answer is the containing entity marked as a containment hit, never a new
entity. (#19) - An unattributable host is stated rather than left empty. A GitOps repo
does not know its deployment target, soruns_onwas empty for every
observed service — which compares as agreement with a declared host rather
than as a gap, and made "what runs on this host?" unanswerable from
observation.orchestrator-gitopsnow recordshost_attribution: unknown
in itsx-orchestratorblock and warns how many stacks it could not place,
andlookup <host>reports both what collectors attributed to that host and
how many observations could not be attributed at all. Guessing a host from a
directory name stays refused. (#19)