The clashes a reader reads: the hard clashes and dilemmas of every placed nogood as reports, each with the declarations it convicts through, and the disjointness clashes no single writer could see. Nothing here writes belief. See docs/nmtms.md, "The clash reports".
The clashes a reader reads: the hard clashes and dilemmas of every placed nogood as reports, each with the declarations it convicts through, and the disjointness clashes no single writer could see. Nothing here writes belief. See docs/nmtms.md, "The clash reports".
(believed-memberships kb x)The believed positive unary memberships of x, as [type context handle] triples,
in content order.
The believed positive unary memberships of `x`, as `[type context handle]` triples, in content order.
(clash-grounds kb r)The declarations report r convicts through, as {:handle :sentence :context} maps in
content order: the believed supporters of the flat-cache entries its conviction reads
(ground-keys) that one of its vantages sees, or the whole KB for a report weighed at
none; for an arity clash, the grounds it is placed through at each vantage
(placed-grounds). No genl edge is named; an edge an argument declaration minted is
named by the sentence it was minted from. Empty for a rebuttal and an :inherited
clash, whose reasons are members (docs/nmtms.md, "The clash reports").
The declarations report `r` convicts through, as `{:handle :sentence :context}` maps in
content order: the believed supporters of the flat-cache entries its conviction reads
(`ground-keys`) that one of its vantages sees, or the whole KB for a report weighed at
none; for an arity clash, the grounds it is placed through at each vantage
(`placed-grounds`). No `genl` edge is named; an edge an argument declaration minted is
named by the sentence it was minted from. Empty for a rebuttal and an `:inherited`
clash, whose reasons are members (docs/nmtms.md, "The clash reports").(conflicts-of kb)The conflict reports (read-clashes), unordered: ranked orders them.
The conflict reports (`read-clashes`), unordered: `ranked` orders them.
(contradictions-at kb ctx)The dilemma reports a reader at ctx reads, unordered: one per placed nogood whose
(contradicts …) ctx believes and sees at some placement (exc/hidden-fn), whose
verdict at ctx is a tie (exc/verdict-at-reader), and every member of which ctx
believes and sees. Each report's vantages are the most general of those placements,
with {context handle} where they defeat different members (reports-over).
The dilemma reports a reader at `ctx` reads, unordered: one per placed nogood whose
`(contradicts …)` `ctx` believes and sees at some placement (`exc/hidden-fn`), whose
verdict at `ctx` is a tie (`exc/verdict-at-reader`), and every member of which `ctx`
believes and sees. Each report's vantages are the most general of those placements,
with `{context handle}` where they defeat different members (`reports-over`).(contradictions-of kb)The dilemma reports (read-clashes), unordered: ranked orders them.
The dilemma reports (`read-clashes`), unordered: `ranked` orders them.
(defeat-grounds kb ds)The grounds (clash-grounds) of the placed nogoods behind the defeat and
(contradicts …) handles ds (exc/defeats-of), each read at the context it is
placed in, in content order: what why-not names beside a placed defeat.
The grounds (`clash-grounds`) of the placed nogoods behind the `defeat` and `(contradicts …)` handles `ds` (`exc/defeats-of`), each read at the context it is placed in, in content order: what `why-not` names beside a placed defeat.
(exposed-clashes kb)core/exposed-clashes' body: every jointly-visible disjointness clash the KB holds,
in violations' entry shape, filed nowhere. A term is a candidate iff it holds two
believed memberships, so the walk over every stored sentex finds each candidate and
takes no instance budget. The separations? gate answers [] with no record fetched
for a KB that separates nothing.
`core/exposed-clashes`' body: every jointly-visible disjointness clash the KB holds, in `violations`' entry shape, filed nowhere. A term is a candidate iff it holds two believed memberships, so the walk over every stored sentex finds each candidate and takes no instance budget. The `separations?` gate answers `[]` with no record fetched for a KB that separates nothing.
(opened kb window)The dilemma reports of the KB as a batch left it, for standing-removed to subtract
the standing ones from after the rollback, read on the KB with the batch in force.
window is every handle the batch relabelled, stored or suspended. The reports are
those of the nogoods a placed (contradicts …) in window belongs to, each over every
placement of its sentence (placements-of), in content order with its :grounds.
The dilemma reports of the KB as a batch left it, for `standing-removed` to subtract the standing ones from after the rollback, read on the KB with the batch in force. `window` is every handle the batch relabelled, stored or suspended. The reports are those of the nogoods a placed `(contradicts …)` in `window` belongs to, each over every placement of its sentence (`placements-of`), in content order with its `:grounds`.
(ranked reports)reports in content order (report-order). Every reader of conflicts-of or
contradictions-of owes this call, since those hold the order the candidate index
answered in.
`reports` in content order (`report-order`). Every reader of `conflicts-of` or `contradictions-of` owes this call, since those hold the order the candidate index answered in.
(read-clashes kb)The hard clashes and the dilemmas of every placed nogood, as {:conflicts [report] :contradictions [report]} in clash-report's shape, each report's vantages the most
general placement contexts that read it so (reports-over).
The hard clashes and the dilemmas of every placed nogood, as `{:conflicts [report]
:contradictions [report]}` in `clash-report`'s shape, each report's vantages the most
general placement contexts that read it so (`reports-over`).(report-vantages r)The placement contexts report r was read at (reports-over, contradictions-at), or
nil for a report built elsewhere. clash-grounds reads the declarations each of them
sees.
The placement contexts report `r` was read at (`reports-over`, `contradictions-at`), or nil for a report built elsewhere. `clash-grounds` reads the declarations each of them sees.
(separations? tax)Does the KB separate any two types, by a disjoint pair, a disjoint metatype, a
sibling_disjoint parent or a partition/separating cover? Four set-emptiness reads
and no walk. The covers are read because separation-frame reads them
(docs/taxonomy.md).
Does the KB separate any two types, by a `disjoint` pair, a disjoint metatype, a `sibling_disjoint` parent or a `partition`/`separating` cover? Four set-emptiness reads and no walk. The covers are read because `separation-frame` reads them (docs/taxonomy.md).
(standing-removed kb {:keys [sentences reports]})The reports of opened that the KB as it stands now, after the rollback, does not
hold, with their :grounds, in content order: the dilemmas the batch opens. The
standing reports are read over the placements of opened's sentences that stand now.
The reports of `opened` that the KB as it stands now, after the rollback, does not hold, with their `:grounds`, in content order: the dilemmas the batch opens. The standing reports are read over the placements of `opened`'s sentences that stand now.
(with-grounds kb reports)reports with each one's clash-grounds under :grounds, read now: a declaration
can move under a report whose members did not, so the grounds ride no memo.
`reports` with each one's `clash-grounds` under `:grounds`, read now: a declaration can move under a report whose members did not, so the grounds ride no memo.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |