@hviana/sema 0.5.3 → 0.5.4

package/dist/src/mind/reasoning.d.ts

@@ -1,42 +0,0 @@
-import type { MindContext } from "./types.js";
-import type { Precomputed } from "./pipeline-mechanism.js";
-/** Whether `bytes` is a proper byte-subspan of `query` — already present in
- *  the question, so voicing it back only restates part of what was asked,
- *  never answers it.  The exact guard recallByResonance already applies to
- *  its OWN grounding candidates (tier 1's `restates`, tier 2's subspan
- *  check, tier 0b's argument-binding subspan check) — every mechanism that
- *  walks a LEARNT CONTINUATION EDGE past an already-vetted grounding
- *  (reason()'s own hops below, and CAST's `projectCounterfactual` seat
- *  substitution — see cast.ts) needs the same guard applied to what the
- *  walk turns up, since `follow()`/`chooseNext`/`pivotInto` know nothing of
- *  the query at all — only of what structurally continues what. */
-export declare function restatesQuery(query: Uint8Array, bytes: Uint8Array): boolean;
-/** Extend a grounded answer forward across facts (multi-hop reasoning).
- *  Pivots on the longest unconsumed learnt context each answer contains,
- *  then follows the pivot's continuation to the next fact.  Repeats up
- *  to `cfg.recallQueryK` hops.  `preConsumed` carries node ids already
- *  spoken for by the grounding stage (cover/extract/CAST).  `voiced` carries
- *  the BYTES of the anchors a mechanism declared it voiced (its `used` set),
- *  when it declared one — see the pivot's own containment rule.  `pre` is the
- *  response's shared pre-computation — the post-grounding stages read the
- *  same container the mechanisms did. */
-export declare function reason(ctx: MindContext, query: Uint8Array, answer: Uint8Array, preConsumed: ReadonlySet<number>, pre: Precomputed, voiced?: readonly Uint8Array[]): Promise<Uint8Array>;
-/** Fuse independent points of attention into one answer (multi-topic).
- *  When the consensus climb finds more than one dominant point, each
- *  independent point grounds its own answer; they are bridged together
- *  by any learnt connector the graph holds between them. */
-export declare function fuseAttention(ctx: MindContext, query: Uint8Array, primary: Uint8Array, pre: Precomputed, 
-/** True when `primary` never touched the consensus climb at all — e.g. a
- *  pure ALU computation, which has no anchor of its own.  commitVotes
- *  ALWAYS admits the dominant root regardless of its vote (attention.ts:
- *  "roots.length === 0 || …") on the assumption a lone root already IS
- *  primary's own source; that assumption is exactly backwards when
- *  primary is unclimbed.  Absent or false preserves the original
- *  behaviour exactly. */
-unclimbed?: boolean, 
-/** The query spans `primary`'s own grounding stands on — used ONLY to place
- *  primary in the fused reading order (see below).  Resolved by the caller,
- *  which is the layer that knows how a given grounding records its evidence;
- *  fuseAttention just reads a position from it.  Empty or absent preserves
- *  the original behaviour exactly. */
-primarySpans?: ReadonlyArray<readonly [number, number]>): Promise<Uint8Array>;

package/dist/src/mind/reasoning.js

@@ -1,305 +0,0 @@
-// reasoning.ts — multi-hop reasoning + multi-topic fusion (Section 4 of the mind).
-//
-//   reason       — extend an answer forward across facts (multi-hop)
-//   fuseAttention — fuse independent points of attention (multi-topic)
-import { rItem, rNode } from "./trace.js";
-import { bytesEqual, indexOf } from "../bytes.js";
-import { resolve } from "./primitives.js";
-import { hubBound } from "./traverse.js";
-import { follow, haloSiblings, project } from "./match.js";
-import { joinWithBridge, pivotInto } from "./resonance.js";
-/** Whether `bytes` is a proper byte-subspan of `query` — already present in
- *  the question, so voicing it back only restates part of what was asked,
- *  never answers it.  The exact guard recallByResonance already applies to
- *  its OWN grounding candidates (tier 1's `restates`, tier 2's subspan
- *  check, tier 0b's argument-binding subspan check) — every mechanism that
- *  walks a LEARNT CONTINUATION EDGE past an already-vetted grounding
- *  (reason()'s own hops below, and CAST's `projectCounterfactual` seat
- *  substitution — see cast.ts) needs the same guard applied to what the
- *  walk turns up, since `follow()`/`chooseNext`/`pivotInto` know nothing of
- *  the query at all — only of what structurally continues what. */
-export function restatesQuery(query, bytes) {
-    return bytes.length < query.length && indexOf(query, bytes, 0) >= 0;
-}
-/** Extend a grounded answer forward across facts (multi-hop reasoning).
- *  Pivots on the longest unconsumed learnt context each answer contains,
- *  then follows the pivot's continuation to the next fact.  Repeats up
- *  to `cfg.recallQueryK` hops.  `preConsumed` carries node ids already
- *  spoken for by the grounding stage (cover/extract/CAST).  `voiced` carries
- *  the BYTES of the anchors a mechanism declared it voiced (its `used` set),
- *  when it declared one — see the pivot's own containment rule.  `pre` is the
- *  response's shared pre-computation — the post-grounding stages read the
- *  same container the mechanisms did. */
-export async function reason(ctx, query, answer, preConsumed, pre, voiced = []) {
-    // Echo guard: a query that is ITSELF a learnt continuation (some context's
-    // answer) is being asked back at the system — hopping forward from it would
-    // chain through the very fact that produced it and echo the conversation
-    // back.  The grounded answer alone is the honest read-out.  Deliberately a
-    // broad structural gate; pinned by test/31-audit.
-    const qId = pre.queryResolved;
-    if (qId !== null && ctx.store.prevCount(qId) > 0)
-        return answer;
-    const consumed = new Set();
-    // Consume a node and its neighbours for pivot-cycle prevention — CAPPED at
-    // the hub bound, via the store's LIMITed edge reads: a common continuation's
-    // reverse fan-in (and a hub context's forward fan-out) is corpus-sized, and
-    // no per-hop operation may grow with the corpus.  The cap follows the one
-    // convention every fan-out decision uses (first √N in the relation's own
-    // read order); a pivot suppressed only by a beyond-cap neighbour may now
-    // fire — the same visibility trade chooseNext documents.
-    const bound = hubBound(ctx);
-    const consumeNode = (id) => {
-        if (id === null)
-            return;
-        consumed.add(id);
-        for (const p of ctx.store.prevFirst(id, bound))
-            consumed.add(p);
-    };
-    const consumeAll = (id) => {
-        if (id === null)
-            return;
-        consumeNode(id);
-        for (const n of ctx.store.nextFirst(id, bound))
-            consumed.add(n);
-    };
-    // Pre-consume whatever the grounding stage already spoke for.  The halo
-    // sweep is one ANN query per node — cap it at haloQueryK sweeps (cover
-    // grounding can pre-consume one node per recognised site, O(query length));
-    // nodes past the cap are still consumed directly, they just skip the
-    // synonym expansion.
-    const preconsume = async () => {
-        let haloSweeps = 0;
-        for (const id of preConsumed) {
-            consumeNode(id);
-            if (haloSweeps >= ctx.cfg.haloQueryK)
-                continue;
-            const h = ctx.store.halo(id);
-            if (!h)
-                continue;
-            haloSweeps++;
-            for (const sib of await haloSiblings(ctx, id, h))
-                consumeNode(sib.id);
-        }
-    };
-    if (ctx.meter) {
-        await ctx.meter.time("reason.preconsumeHalos", preconsume);
-    }
-    else {
-        await preconsume();
-    }
-    let cur = answer;
-    const qv = pre.guide; // the response-wide guide IS the query's gist
-    let t;
-    const startedFrom = answer;
-    for (let hop = 0; hop < ctx.cfg.recallQueryK; hop++) {
-        const curId = resolve(ctx, cur);
-        consumeNode(curId);
-        // Forward-absorb: follow only UNCONSUMED continuations.  The gate below
-        // checks an unconsumed edge EXISTS, but follow()'s chooseNext knows
-        // nothing of `consumed` and may still walk to a consumed fixpoint —
-        // absorbing it would repeat content the grounding stage already spoke
-        // for, so a consumed fixpoint falls through to the pivot step instead.
-        if (curId !== null &&
-            ctx.store.nextFirst(curId, bound).some((n) => !consumed.has(n))) {
-            const fwd = await follow(ctx, curId, qv);
-            const fwdId = fwd !== null ? resolve(ctx, fwd) : null;
-            if (fwd !== null && !bytesEqual(fwd, cur) &&
-                (fwdId === null || !consumed.has(fwdId)) &&
-                !restatesQuery(query, fwd)) {
-                consumeAll(curId);
-                t ??= ctx.trace?.enter("reason", [
-                    rItem(startedFrom, "grounded"),
-                ]);
-                ctx.trace?.step("absorbForward", [rItem(cur, "answer", curId)], [rItem(fwd, "answer", resolve(ctx, fwd) ?? undefined)], "the answer is itself a learnt fact — follow its continuation to the fixpoint");
-                cur = fwd;
-                continue;
-            }
-        }
-        // Pivot: find the longest unconsumed learnt context the answer contains.
-        consumeAll(curId);
-        const pivot = await pivotInto(ctx, cur, consumed, voiced);
-        if (pivot === null)
-            break;
-        const fc = await follow(ctx, pivot, qv);
-        consumeAll(pivot);
-        if (fc === null || bytesEqual(fc, cur) || restatesQuery(query, fc))
-            break;
-        t ??= ctx.trace?.enter("reason", [rItem(startedFrom, "grounded")]);
-        ctx.trace?.step("pivotStep", [rItem(cur, "answer"), rNode(ctx, pivot, "pivot")], [rItem(fc, "answer", resolve(ctx, fc) ?? undefined)], "pivot on the shared span this answer contains, then step forward across that fact");
-        cur = fc;
-    }
-    t?.done([rItem(cur, "answer", resolve(ctx, cur) ?? undefined)], "the multi-hop chain's fixpoint");
-    return cur;
-}
-/** Fuse independent points of attention into one answer (multi-topic).
- *  When the consensus climb finds more than one dominant point, each
- *  independent point grounds its own answer; they are bridged together
- *  by any learnt connector the graph holds between them. */
-export async function fuseAttention(ctx, query, primary, pre, 
-/** True when `primary` never touched the consensus climb at all — e.g. a
- *  pure ALU computation, which has no anchor of its own.  commitVotes
- *  ALWAYS admits the dominant root regardless of its vote (attention.ts:
- *  "roots.length === 0 || …") on the assumption a lone root already IS
- *  primary's own source; that assumption is exactly backwards when
- *  primary is unclimbed.  Absent or false preserves the original
- *  behaviour exactly. */
-unclimbed = false, 
-/** The query spans `primary`'s own grounding stands on — used ONLY to place
- *  primary in the fused reading order (see below).  Resolved by the caller,
- *  which is the layer that knows how a given grounding records its evidence;
- *  fuseAttention just reads a position from it.  Empty or absent preserves
- *  the original behaviour exactly. */
-primarySpans = []) {
-    // When the answer is structurally drawn from the query itself
-    // (extraction), it already spans all the query's pieces — fusion
-    // would only add noise from unrelated stored contexts.  The gate is
-    // STRICT containment (resolved node in the query's tree, or a contiguous
-    // byte run): the old sparse-subsequence test was trivially satisfied by
-    // short answers over long queries, silently starving multi-topic queries
-    // of fusion.
-    if (containsSpan(ctx, query, primary))
-        return primary;
-    // The committed points of attention ARE the shared climb's roots (same
-    // query, same k, same DF mode) — read them from Precomputed instead of
-    // re-climbing, so even a traced response pays for the climb once.
-    const forest = (await pre.attention()).roots;
-    // A LONE root is ordinarily primary's own source — nothing to fuse.  But
-    // when primary is unclimbed, the lone root was never checked against
-    // anything: it is admitted by commitVotes unconditionally, so it may be
-    // genuine consensus (Attention.breadth dominates — most of the query's
-    // OWN regions corroborate it) or a coincidental echo (breadth does not
-    // dominate — see test/35-attention-confidence).  breadth is the SCALE-
-    // INVARIANT read of exactly this question: the raw IDF vote cannot serve
-    // here, since it is an absolute ln(N)-scaled quantity (a genuine root on
-    // a large store can score BELOW its own floor while a coincidental echo
-    // on a small one scores comfortably above its own, smaller, floor).
-    //
-    // Breadth alone is not enough when primary is a pure COMPUTATION.  The ALU
-    // answers "2+2 equals what?" with 4, and the store's own arithmetic table
-    // then supplies a lone root — an exemplar like "1+2" — whose breadth
-    // dominates because it is corroborated by the computation's OWN bytes.
-    // Fusing it projected that exemplar's continuation and the bridge voiced
-    // "4+3" (test/11 seed 99).  A second point of attention must stand on
-    // evidence that is structurally SEPARATE from primary's: at least one
-    // perceptual quantum of query between them, the same separation
-    // countClusters uses to tell independent evidence neighbourhoods apart.
-    // Not a score, and not a tuned bar — the fold's own quantum.
-    //
-    // With no primarySpans (the caller did not resolve them) every span
-    // vacuously qualifies, preserving the original behaviour exactly.
-    const quantum = ctx.space.maxGroup;
-    const independentOfPrimary = (root) => primarySpans.every(([s, e]) => {
-        const gap = root.end <= s
-            ? s - root.end
-            : e <= root.start
-                ? root.start - e
-                : 0;
-        return gap >= quantum;
-    });
-    const lonePromotes = unclimbed && forest.length === 1 &&
-        forest[0].breadth > 0.5 && independentOfPrimary(forest[0]);
-    if (forest.length === 0 || (forest.length <= 1 && !lonePromotes)) {
-        return primary;
-    }
-    // WHERE THE QUERY ASKED FOR IT.  The sort below orders the fused pieces by
-    // query position, which is the whole point of the `start` field: a
-    // multi-topic answer should read in the order the question posed its
-    // topics.  Every ROOT carries its own start.  `primary` did not — it was
-    // given forest[0].start, the FIRST attention root's position, which is
-    // primary's own source only when primary happens to come from that root.
-    // When it does not, primary is sorted to a position it never occupied.
-    //
-    // Observed live: "What is the capital of France? And what is 2 + 2?"
-    // answered "4The capital city of France is Paris." — the ALU result, whose
-    // evidence is the "2 + 2" span near the END of the query, inherited the
-    // France root's start of 0 and sorted ahead of the France answer.  Both
-    // pieces were right; only the order was.
-    //
-    // primary's own position is the earliest query byte its grounding stands
-    // on.  `accounted` is the cost-ladder read of that and is authoritative
-    // when non-empty; when it is empty the grounding is a pure COMPUTATION,
-    // whose evidence is its computed span — the same cost-ladder-vs-coverage
-    // distinction think() already draws for the fusion remainder ("`accounted`
-    // alone undercounts this ... cover prices its computed spans at near-zero
-    // and deliberately leaves them out"), read here for position instead of
-    // for coverage.  With neither, nothing is known and the old behaviour
-    // (forest[0].start) stands.
-    const primaryStart = primarySpans.length > 0
-        ? primarySpans.reduce((m, [s]) => Math.min(m, s), Infinity)
-        : forest[0].start;
-    const pieces = [
-        { start: primaryStart, bytes: primary },
-    ];
-    const qv = pre.guide; // once, not per root
-    const rest = lonePromotes ? forest : forest.slice(1);
-    const t = ctx.trace?.enter("fuseAttention", [
-        rItem(primary, "primary"),
-        ...rest.map((r) => rNode(ctx, r.anchor, "point", r.vote)),
-    ]);
-    for (const root of rest) {
-        // DISPERSION: this root's contributing regions are confined to a
-        // single cluster (see Attention.clusters) — one local neighbourhood of
-        // the query, not several separate places.  Raw region count already
-        // failed to discriminate a coincidental match from a genuine further
-        // topic (test/24 gap 3.1 vs test/35's echo); dispersion is a different
-        // question — not how MUCH evidence, but how many separate PLACES in the
-        // query corroborate it — and a coincidental match is structurally
-        // confined to one cluster no matter how strongly it resonates.
-        //
-        // EXCEPTION: crossRegionVotes' own joint conclusions (a query naming
-        // two attributes that were only ever learnt TOGETHER — test/34's own
-        // binding corpus) are inherently ONE fused context and are pooled from
-        // a single synthetic region, so they always read as one cluster even
-        // though they already, by construction, account for both original
-        // mentions.  `breadth` (dominates — the same > half-the-query bar used
-        // everywhere else) still correctly recognises these: a genuine joint
-        // binding explains the MAJORITY of the query's regions on its own,
-        // which a coincidental echo never does (verified: test/35's echo tops
-        // out at 0.40).  So a root is trusted when EITHER measure alone
-        // indicates real signal — excluded only when BOTH are weak.  Cheap and
-        // synchronous — checked before the async already-answered walk below.
-        if (root.clusters < 2 && root.breadth <= 0.5) {
-            ctx.trace?.step("singleCluster", [rNode(ctx, root.anchor, "point", root.vote)], [], "this point's evidence is confined to one local neighbourhood of the query — not trusted as an independent topic");
-            continue;
-        }
-        // ALREADY ANSWERED: this root's own learnt continuation — the same
-        // content-addressed walk reason()'s echo guard already trusts
-        // (`ctx.store.prevCount(qId) > 0`), here applied per-candidate instead
-        // of to the whole query — is VERBATIM present later in the query.  A
-        // query that embeds both an exchange's ask and its own already-given
-        // reply (a conversation's turn plus its own prior answer, concatenated
-        // raw by addTurn — or any caller pasting a transcript into one
-        // respond() call; the check is Mind-bookkeeping-free, so it treats both
-        // identically) has already spoken this root's answer — fusing it in
-        // again would only restate it.  Deliberately NOT a magnitude measure:
-        // it fires on exact content-addressed recurrence, not on how strongly
-        // the root resonates.
-        const cont = await follow(ctx, root.anchor, qv);
-        if (cont !== null && cont.length > 0 && indexOf(query, cont, root.end) >= 0) {
-            ctx.trace?.step("alreadyAnswered", [rNode(ctx, root.anchor, "point", root.vote)], [rItem(cont, "continuation")], "this point's own learnt continuation already appears later in the query — already answered, not fused");
-            continue;
-        }
-        const g = await project(ctx, root.anchor, qv);
-        if (g === null || g.length === 0)
-            continue;
-        if (pieces.some((p) => indexOf(p.bytes, g, 0) >= 0))
-            continue;
-        pieces.push({ start: root.start, bytes: g });
-    }
-    if (pieces.length === 1) {
-        t?.done([rItem(primary, "answer")], "no further independent point grounded");
-        return primary;
-    }
-    pieces.sort((a, b) => a.start - b.start);
-    let out = pieces[0].bytes;
-    for (let i = 1; i < pieces.length; i++) {
-        // An approximate-resonance miss (or a genuinely unlearnt junction) joins
-        // the pieces bare — joinWithBridge surfaces it as a bridgeMiss step.
-        out = await joinWithBridge(ctx, out, pieces[i].bytes);
-    }
-    t?.done([rItem(out, "answer", resolve(ctx, out) ?? undefined)], `fused ${pieces.length} independent points of attention into one answer`);
-    return out;
-}
-// (resonance.js is already a static dependency above — `bridge` — so the old
-// dynamic import of pivotInto guarded against a cycle that does not exist.)
-import { containsSpan } from "./match.js";

package/dist/src/mind/recognition.d.ts

@@ -1,20 +0,0 @@
-import type { MindContext, Recognition, Segment } from "./types.js";
-/** Decompose a byte stream into every stored form that leads somewhere
- *  (has a continuation edge or a halo).  Two complementary readings:
- *
- *   • structural — walk the query's own perceived tree, naming each subtree
- *     by findLeaf at the leaves and findBranch above.  Catches every form
- *     aligned to the query's segmentation.
- *
- *   • canonical — re-derive the store's segmentation directly: at each byte,
- *     the longest known leaf, chained into flat branches.  Names forms the
- *     query's own cut cannot, and records sub-leaf boundaries as `splits`.
- *
- *  Both O(n · maxGroup) bounded O(1) probes — never a scan of the corpus. */
-export declare function recognise(ctx: MindContext, bytes: Uint8Array): Recognition;
-/** Segment bytes using the geometry's own groupings — leaf-parent
- *  nodes from the perceived tree, with consecutive bare leaves merged
- *  into one segment.  Each segment's gist is perceived from its bytes
- *  IN ISOLATION, so the same content has the same gist regardless of
- *  where it appears. */
-export declare function segment(ctx: MindContext, bytes: Uint8Array): Segment[];