P94 � AIEP � Anticipatory Branch Surfacing and Evidence Convergence Notification
Field of the Invention
[0001] The present invention relates to governed reasoning substrates for cognitive assistance systems.
[0002] More particularly, the invention relates to a deterministic mechanism within an Architected Instruction & Evidence Protocol (AIEP) substrate for monitoring the evidence weight of archived reasoning branches and automatically surfacing a branch to the user when newly admitted evidence causes the branch’s cumulative evidence weight to cross a schema-defined reactivation threshold, such that the substrate notifies the user of a previously unresolved hypothesis that is now resolvable � before the user re-encounters the question that produced it.
Background
[0003] Governed reasoning substrates accumulate reasoning branches over extended periods. A branch may be formed from genuine evidential divergence but archived because available evidence at the time of formation was insufficient to resolve it. Subsequent evidence admitted to the substrate may, when accumulated against an archived branch, cause that branch to become resolvable.
[0004] Conventional AI assistant systems do not maintain persistent archived branches across sessions and therefore cannot detect that newly admitted evidence completes a previously unresolved inference.
[0005] Even systems that maintain session history do not evaluate incoming evidence against archived branch evidence weight continuously, do not compute a cumulative evidence weight threshold crossing event, and do not generate a user-facing notification from that event as a primary output independent of any user query.
[0006] Existing systems do not provide:
(a) continuous evaluation of newly admitted evidence against the evidence weight of all archived branches in the substrate, independent of user query; (b) detection of a threshold crossing event when cumulative evidence weight of an archived branch crosses a schema-defined reactivation threshold; (c) automatic generation of a user-facing BranchSurfacingNotification upon threshold crossing, identifying the archived branch, its formation context, and the specific evidence that completed it; (d) cryptographic binding of the BranchSurfacingNotification to the archived branch record and the triggering evidence artefact; or (e) deterministic replay of the threshold crossing evaluation from stored Evidence Ledger entries.
[0007] There exists a need for an anticipatory branch surfacing mechanism that evaluates newly admitted evidence against archived branches continuously, detects threshold crossing events, and generates user-facing notifications that surface previously unresolved inferences before the user re-encounters the originating question.
Summary of the Invention
[0008] The invention provides a deterministic anticipatory branch surfacing system within an AIEP substrate.
[0009] The system maintains for each archived branch in the Evidence Ledger a CumulativeEvidenceWeightRecord comprising the branch identifier, the evidence weight at time of archival, and the accumulated evidence weight of all subsequently admitted evidence that bears on the branch.
[0010] Each time a new evidence artefact is admitted to the Evidence Ledger, the system evaluates the artefact’s BranchRelevanceScore against each archived branch. BranchRelevanceScore is computed as a deterministic function over the artefact’s evidence fields and the branch’s canonical conclusion representation.
[0011] Where BranchRelevanceScore exceeds a schema-defined minimum relevance threshold, the artefact’s evidence weight is added to the archived branch’s CumulativeEvidenceWeightRecord.
[0012] The system evaluates whether the updated CumulativeEvidenceWeight crosses a schema-defined ReactivationThreshold.
[0013] Upon threshold crossing, the system generates a BranchSurfacingNotification comprising: the archived branch identifier and canonical conclusion; the formation timestamp and context summary; the cumulative evidence weight at crossing; the specific triggering evidence artefact hash; a ConvergenceHash computed over the archived branch record and triggering artefact; and a generation timestamp recorded as data.
[0014] The BranchSurfacingNotification is surfaced to the user as a primary substrate output, independent of any pending user query.
[0015] The BranchSurfacingNotification and the threshold crossing event are recorded in the append-only Reasoning Ledger.
[0016] The technical effect is a governed reasoning substrate that notifies the user when previously unresolvable inferences become resolvable � anticipating the user’s return to an archived question rather than waiting for the user to re-raise it.
Definitions
[0017] CumulativeEvidenceWeightRecord: An append-only per-branch record comprising the branch identifier, evidence weight at archival, and accumulated weight of all subsequently admitted relevant evidence.
[0018] BranchRelevanceScore: A deterministic score quantifying the evidential relevance of a newly admitted evidence artefact to an archived branch, computed as a function of the artefact’s evidence fields and the branch’s canonical conclusion representation.
[0019] ReactivationThreshold: A schema-defined minimum CumulativeEvidenceWeight value at which an archived branch is considered resolvable and a BranchSurfacingNotification is generated. Version-bound schema parameter.
[0020] BranchSurfacingNotification: A primary substrate output generated upon ReactivationThreshold crossing, comprising the archived branch identifier, canonical conclusion, formation context, cumulative evidence weight, triggering artefact hash, ConvergenceHash, and generation timestamp.
[0021] ConvergenceHash: A cryptographic hash computed over the canonical serialisation of the archived branch record and the triggering evidence artefact hash, binding the notification cryptographically to its generating inputs.
Detailed Description of Preferred Embodiments
1. Continuous Evidence Evaluation Against Archived Branches
[0022] Upon admission of each new evidence artefact to the Evidence Ledger, the branch surfacing engine evaluates the artefact against all archived branches.
[0023] Evaluation is triggered by the Evidence Ledger append operation and executes before the next user interaction cycle.
[0024] For each archived branch, BranchRelevanceScore is computed as:
BranchRelevanceScore = f(CanonicalSerialise(ArtefactEvidenceFields), BranchConclusionRepresentation, SchemaVersionId)
[0025] The function f is defined in the schema and is deterministic. In one embodiment f computes semantic overlap between the artefact’s stated conclusion fields and the branch’s canonical conclusion representation using schema-defined term mappings.
[0026] BranchRelevanceScore is normalised to [0.0, 1.0].
2. CumulativeEvidenceWeightRecord Maintenance
[0027] Where BranchRelevanceScore exceeds the schema-defined minimum relevance threshold, the artefact’s evidence weight � scaled by BranchRelevanceScore � is appended to the archived branch’s CumulativeEvidenceWeightRecord.
[0028] CumulativeEvidenceWeight is computed as the sum of: the evidence weight at archival; and all subsequently accumulated scaled evidence weight additions.
[0029] CumulativeEvidenceWeightRecord entries are append-only.
3. ReactivationThreshold Crossing Detection
[0030] After each CumulativeEvidenceWeightRecord update, the system evaluates whether CumulativeEvidenceWeight has crossed the ReactivationThreshold.
[0031] The ReactivationThreshold is a schema-defined version-bound parameter.
[0032] Crossing is defined as CumulativeEvidenceWeight = ReactivationThreshold where the previous evaluation returned CumulativeEvidenceWeight < ReactivationThreshold.
[0033] Only the first threshold crossing for each archived branch generates a BranchSurfacingNotification. Subsequent additions to an already-crossed branch update the record but do not generate further notifications.
4. BranchSurfacingNotification Generation
[0034] Upon ReactivationThreshold crossing, the system generates a BranchSurfacingNotification.
[0035] ConvergenceHash is computed as:
ConvergenceHash = H(ArchivedBranchRecordHash || TriggeringArtefactHash || CumulativeEvidenceWeight || SchemaVersionId)
[0036] The BranchSurfacingNotification is presented to the user as a primary substrate output � not as a response to a query, but as an independently generated surface event.
[0037] The notification presents to the user: the original reasoning branch conclusion in natural language; the context in which it was formed; the specific new evidence that completed it; and an invitation to re-engage with the branch.
[0038] The BranchSurfacingNotification and ConvergenceHash are appended to the Reasoning Ledger.
5. Deterministic Replay
[0039] Replay of threshold crossing detection uses stored Evidence Ledger entries, CumulativeEvidenceWeightRecord entries, and the schema version identifier recorded at time of notification.
[0040] Replay reproduces the BranchRelevanceScore computation, CumulativeEvidenceWeight accumulation, and threshold crossing event from stored inputs without dependence on current system state.
6. Swarm Substrate Integration
[0041] In a swarm deployment, evidence artefacts admitted from peer nodes are evaluated against local archived branches using the same BranchRelevanceScore computation.
[0042] Cross-node evidence that crosses a local ReactivationThreshold generates a BranchSurfacingNotification on the local node.
[0043] The swarm amplifies anticipatory surfacing by extending the evidence pool evaluated against each node’s archived branches.
Claims
-
A deterministic anticipatory branch surfacing system within an AIEP substrate, the system configured to: maintain a CumulativeEvidenceWeightRecord for each archived branch comprising accumulated evidence weight of all admitted relevant evidence; evaluate each newly admitted evidence artefact against all archived branches by computing a BranchRelevanceScore as a deterministic function of artefact evidence fields and branch canonical conclusion representation; add scaled evidence weight to a branch’s CumulativeEvidenceWeightRecord where BranchRelevanceScore exceeds a minimum relevance threshold; detect a ReactivationThreshold crossing event when CumulativeEvidenceWeight reaches a schema-defined threshold; and generate a BranchSurfacingNotification as a primary substrate output upon threshold crossing, comprising the archived branch identifier, canonical conclusion, formation context, cumulative evidence weight, triggering artefact hash, and a ConvergenceHash.
-
The system of claim 1 wherein BranchSurfacingNotification is generated as a primary substrate output independent of any pending user query.
-
The system of claim 1 wherein only the first ReactivationThreshold crossing for each archived branch generates a BranchSurfacingNotification.
-
The system of claim 1 wherein ConvergenceHash is computed as a cryptographic hash over the archived branch record hash, triggering artefact hash, cumulative evidence weight, and schema version identifier.
-
The system of claim 1 wherein BranchSurfacingNotification and the threshold crossing event are recorded in the append-only Reasoning Ledger.
-
The system of claim 1 wherein deterministic replay reproduces BranchRelevanceScore computation, CumulativeEvidenceWeight accumulation, and threshold crossing from stored Evidence Ledger entries without dependence on current system state.
-
The system of claim 1 wherein cross-node evidence artefacts admitted from swarm peers are evaluated against local archived branches using the same BranchRelevanceScore computation.
-
A method for anticipatory branch surfacing in a governed reasoning substrate comprising: evaluating each newly admitted evidence artefact against archived branches by BranchRelevanceScore; accumulating scaled evidence weight in CumulativeEvidenceWeightRecords; detecting ReactivationThreshold crossing; and generating a BranchSurfacingNotification as a primary output.
-
A non-transitory computer-readable medium storing instructions which, when executed, perform the method of claim 8.
Drawings
Figure 1 � CumulativeEvidenceWeight Accumulation per Archived Branch
Archived Branches (not yet reactivated):
Branch B1 (archived): CumulativeEvidenceWeight = 0.0
Branch B2 (archived): CumulativeEvidenceWeight = 1.8
Branch B3 (archived): CumulativeEvidenceWeight = 3.1
|
v new artefact admitted: EV-042
+----------------------------------------------+
| For each archived branch B_i: |
| BranchRelevanceScore(EV-042, B_i) |
| = f(artefact_evidence_fields, |
| branch_canonical_conclusion) |
| |
| score = min_relevance_threshold? |
| YES ? CumulativeEvidenceWeight_i |
| += score � artefact.weight |
| NO ? no update |
+----------------------------------------------+
|
v
Branch B2: 1.8 + 0.6 = 2.4 (below threshold)
Branch B3: 3.1 + 1.2 = 4.3 (THRESHOLD CROSSED)
Figure 2 � BranchSurfacingNotification Generation
Branch B3 CumulativeEvidenceWeight (4.3) = ReactivationThreshold (4.0)
|
v
convergence_hash = sha256(
archived_branch_record_hash
? triggering_artefact_hash ? EV-042
? cumulative_evidence_weight ? "4.3"
? schema_version
)
|
v
BranchSurfacingNotification {
archived_branch_id: "branch-B3"
canonical_conclusion: "..."
formation_context: "..."
cumulative_evidence_weight: 4.3
triggering_artefact_hash: sha256(EV-042)
convergence_hash: "cf:a3b7..."
}
|
v emitted as PRIMARY substrate output (not query-dependent)
Figure 3 � System-Level Surfacing Flow
Evidence Ledger (ongoing admissions)
�
� each new admission
?
BranchRelevanceScore evaluation
(ALL archived branches evaluated in parallel)
�
� weight accumulation
?
CumulativeEvidenceWeightRecord per branch
�
� threshold crossing detection
?
BranchSurfacingNotification ------------------? User presentation
(first crossing only) "Previously unresolvable
inference now resolvable"
�
� recorded
?
Reasoning Ledger (append-only)
Figure 4 � Deterministic Replay Verification
Replay from stored Evidence Ledger entries:
Step 1: replay all evidence admissions in order
Step 2: recompute BranchRelevanceScore for each
(artefact_fields, branch_conclusion ? deterministic)
Step 3: recompute CumulativeEvidenceWeight sequence
Step 4: detect threshold crossing at same point
Step 5: recompute convergence_hash
compare to stored BranchSurfacingNotification
match ? REPLAY VERIFIED
mismatch ? TAMPER DETECTED
Cross-node swarm artefacts evaluated identically.
All computations deterministic from ledger state.
Abstract
A deterministic anticipatory branch surfacing system within an AIEP governed reasoning substrate is disclosed. The system maintains a CumulativeEvidenceWeightRecord for each archived branch, accumulating scaled evidence weight from each newly admitted artefact whose BranchRelevanceScore exceeds a minimum relevance threshold. Upon the CumulativeEvidenceWeight crossing a schema-defined ReactivationThreshold, a BranchSurfacingNotification is generated as a primary substrate output independent of any user query, comprising the archived branch identifier, canonical conclusion, formation context, cumulative evidence weight, triggering artefact hash, and a ConvergenceHash cryptographically binding the notification to its generating inputs. The notification presents to the user that a previously unresolvable inference is now resolvable, before the user re-encounters the originating question. All threshold crossing events are recorded in the append-only Reasoning Ledger and are deterministically replayable from stored Evidence Ledger entries.