Mechanism
Two people can present the same credentials, issue the same query, and mean entirely different things. The adaptive index already scopes what each requester is permitted to see: an anchor publishes its semantic neighborhood to an arriving discovery object under that object's policy profile and biological-identity credential, so access is personalized. What that access-control scoping does not capture is meaning. The same admissible neighborhood, ranked the same way for everyone, cannot distinguish the user who always means their own pet when they say a name from the user who means the public figure. The personal lineage layer adds that missing axis. Each user maintains a per-user record of their own accumulated traversals, and that record biases how an anchor ranks the candidate transitions it offers to a discovery object carrying that user's identity, without changing which transitions are admissible.
The layer is a weighting overlay applied at the moment an anchor publishes its neighborhood to a discovery object. The discovery object carries, in its policy reference field, a reference to its originating user's personal lineage layer: a structured subgraph drawn from that user's prior admitted transitions. The filed specification discloses the discovery object's lineage field, which records, for each admitted transition, the anchor identifier, the timestamp, the semantic state mutation applied, the admissibility determination that permitted the transition, and the semantic neighborhood from which the transition was selected. The specification further records, for each completed traversal, how much semantic progress was achieved between successive anchors and whether the traversal reached a resolution state or was abandoned. The personal lineage layer accumulates these recorded transitions and traversal outcomes across the user's history. At each anchor, the candidate transition set produced by the search step is reweighted against this subgraph. Transitions structurally aligned with neighborhoods the user has previously traversed and resolved are elevated; transitions aligned with the user's prior abandonments and backtracks are deprioritized. The underlying anchors, the shared substrate, and every other user's experience are untouched. The substrate stays common; the experience of it becomes personal.
The defining property of the layer is that it is built from the user's own admitted transition history rather than from an opaque behavioral profile inferred at the application layer. Because the specification keys traversal access to a resolved biological identity rather than to a session or device, the layer that applies on a given traversal is the one bound to the identity that originated it. The personalization derives from the same auditable lineage record the system already maintains for governance, not from a separately accumulated behavioral dossier.
The Governance Boundary
The personal lineage layer modulates preference among admissible candidates; it never alters admissibility. This separation is the load-bearing constraint of the mechanism and is enforced structurally rather than by convention. The candidate transition set presented to the weighting step has already passed the anchor's policy-scoped neighborhood publication: every candidate in it is one the user is authorized to traverse. The layer can only reorder that set. It cannot introduce a transition the policy profile excluded, cannot reveal a neighborhood the credential does not authorize, and cannot surface another user's lineage. A user's history can make an admissible result rank first; it can never make an inadmissible result reachable.
Because the boundary is structural, personalization and governance do not compete. A regulated deployment can offer deeply personalized ranking with no risk that personalization becomes a covert access-control bypass, because the governance evaluation that determines admissibility runs before and independently of the weighting overlay. The layer also cannot leak across users: a discovery object references only its own originating user's layer, and the merge of another user's history is impossible by construction rather than prevented by policy.
Operating Inputs
The layer draws on the inputs the specification already records in the discovery object's lineage field. Each admitted transition in a user's history carries an anchor identifier, a timestamp, the semantic state mutation that was applied, the admissibility determination that permitted it, and the semantic neighborhood from which it was selected. The aggregate of a user's completed traversals also records, per the specification, how much semantic progress was achieved between successive anchors and whether the traversal reached a resolution state or was abandoned. These recorded inputs are what the weighting overlay consults when it reorders the candidate transition set at publication time. The specification does not fix a numeric scoring formula, a decay schedule, or a bias bound for this overlay, so none is stated here; the layer is constrained only by the requirement that it reorder admissible candidates without altering admissibility.
The layer is keyed to a resolved user identity rather than to a session or a device. The specification's biological identity scoping produces persistent identity through behavioral continuity rather than session tokens, so a user who initiates a traversal in one session and resumes it in another is recognized as the same user, and the layer that applies follows that resolved identity across sessions and endpoints. The same biological-identity credential that scopes the user's access also keys which lineage applies. The specification further contemplates non-human originating entities, including autonomous agents whose cognitive state governs their traversals, so an agent's own accumulated lineage can likewise bias its later choices toward neighborhoods its prior traversals resolved successfully.
Alternative Embodiments
In a professional-research embodiment, a user's accumulated medical or legal research lineage biases their later queries toward the neighborhoods their prior work established as authoritative for them, so a clinician and a patient issuing the same query receive the same admissible sources ranked to their respective histories. In a developer embodiment, a user's coding lineage biases later queries toward the libraries and patterns they have repeatedly traversed, without restricting access to alternatives. In an agent-delegation embodiment, an autonomous agent's prior delegation outcomes bias its subsequent counterparty selection toward higher-success partners, a governed preference that improves coordination without hard-coding a partner list.
In a hosted-service embodiment, the substrate is operated as a hosted semantic traversal service through which many agents and independently operated systems query a shared index, and a user's resolved identity continues to key the lineage that biases their ranking regardless of which system hosts the index infrastructure. In a regulated embodiment, because the layer is built from the same lineage records the system already governs, the access scoping that controls which neighborhoods a user may reach also governs which lineage applies, so personalized ranking operates strictly inside the existing governance configuration rather than alongside a separate personalization store.
Composition
The personal lineage layer composes with the anchor-level neighborhood publication: the layer is applied to the candidate transition set that the publication produces, so it inherits the publication's policy scoping for free and operates strictly inside it. It composes with biological-identity-scoped access: the same credential that determines which neighborhoods a user may see also keys which personal lineage layer applies, binding personalization to a verified identity rather than to a spoofable session. It composes with the aggregate index-evolution signal disclosed for lineage as a whole: collective lineage drives how anchors split, merge, and re-publish for everyone, while the personal layer drives how an already-published neighborhood is ranked for one user. The two are deliberately separate consumers of traversal history, one shaping the shared structure and one shaping the individual experience, and neither can be used to reconstruct the other.
Prior-Art Distinction
The specification distinguishes the substrate from link-count relevance ranking, exemplified by PageRank, which computes a query-independent global score that requires bolted-on personalization layers and contextual boosting to approximate query-specific relevance. The personal lineage layer takes the opposite approach: it operates at the substrate layer as a reordering of structured candidate transitions a user is already authorized to traverse, and it is bound to the same governance evaluation that determines admissibility rather than applied as a separate ranking stage. The specification also contrasts its collaborative traversal mechanism with collaborative filtering in recommendation systems, noting that the disclosed mechanism operates on structured semantic state and is governed by policy at every boundary rather than on user-item interaction matrices. The distinguishing combination here is identity-scoped weighting of admissible candidates, drawn from the user's own auditable traversal lineage, and bounded so that preference modulation never becomes an access-control bypass.
Disclosure Scope
The policy-scoped, requester-specific anchor neighborhood publication is disclosed in United States Patent Application 19/647,395 at Section 10.4, the biological-identity scoping of traversal access at Section 10.15, and the use of aggregate traversal lineage as an index-evolution signal at Section 10.20. The discovery object's lineage field, which records each admitted transition's anchor identifier, timestamp, semantic state mutation, admissibility determination, and selecting neighborhood, is disclosed at Section 10.2. This article discloses, as an extension of those primitives, the personal lineage layer: a per-user subgraph of that user's accumulated admitted transitions; the application of that subgraph as a weighting overlay on the anchor's published candidate transition set; the structural separation between preference modulation and admissibility; and the embodiments enumerated above. The specification does not fix a numeric scoring formula, decay schedule, or bias bound for this overlay, and none is claimed here. The scope extends to weighting policies not described whose behavior reduces to reordering of admissible candidates, and to identity bindings, including autonomous-agent identities, for which a personal lineage layer is maintained and applied at traversal time.
