@rekal/mem 0.0.0 → 0.0.2

package/src/frecency.ts

@@ -1,58 +1,41 @@
-import type { Db, DocRow } from "./db.ts"
-
 // Exponential decay frecency, based on:
 // https://wiki.mozilla.org/User:Jesse/NewFrecency
 // Ported from snacks.nvim picker frecency
 
 const HALF_LIFE = 30 * 24 * 3600 // 30 days in seconds
 const LAMBDA = Math.LN2 / HALF_LIFE // λ = ln(2) / half_life
-const VISIT_VALUE = 1 // default points per visit
-
-export class Frecency {
-  #db: Db
-  #now: number
-
-  constructor(db: Db, now = Date.now() / 1000) {
-    this.#db = db
-    this.#now = now
-  }
+const VALUES = {
+  new: 1,
+  updated: 0.8,
+  visit: 1,
+} as const
 
-  /** Convert a score into a deadline timestamp.
-   *  deadline = now + ln(score) / λ */
-  toDeadline(score: number): number {
-    return this.#now + Math.log(score) / LAMBDA
-  }
+export type FrecencyScore = keyof typeof VALUES
 
-  /** Convert a deadline timestamp back into a current score.
-   *  score = e^(λ * (deadline - now)) */
-  toScore(deadline: number): number {
-    return Math.exp(LAMBDA * (deadline - this.#now))
-  }
+const now = () => Date.now() / 1000
 
-  /** Get the current frecency score for a doc.
-   *  If no deadline exists, estimates from updatedAt (a single visit at file mtime, decayed to now). */
-  get(doc: DocRow): number {
-    if (doc.deadline) return this.toScore(doc.deadline)
-    // Seed: treat updatedAt as a single past visit, decayed to now
-    // Since ln(1)/λ = 0 for VISIT_VALUE=1, deadline = timestamp
-    const ts = new Date(doc.updated_at).getTime() / 1000
-    return this.toScore(ts)
-  }
+/** Convert a frecency score to a deadline timestamp (for DB storage). */
+export function toDeadline(frecency: number): number {
+  return now() + Math.log(frecency) / LAMBDA
+}
 
-  /** Record a visit — adds a decayed value to the doc's score.
-   *  @param opts.value - points to add (default: 1)
-   *  @param opts.ts - timestamp of the visit in seconds (default: now).
-   *    Use file mtime for seeding from external edits. */
-  visit(doc: DocRow, opts?: { value?: number; ts?: number }) {
-    const value = opts?.value ?? VISIT_VALUE
-    const ts = opts?.ts ?? this.#now
-    const visitDeadline = ts + Math.log(value) / LAMBDA
-    const score = this.get(doc) + this.toScore(visitDeadline)
-    this.#db.setDeadline(doc.id, this.toDeadline(score))
-  }
+/** Convert a deadline timestamp back to a frecency score. */
+export function toScore(deadline: number): number {
+  return Math.exp(LAMBDA * (deadline - now()))
+}
 
-  /** Get frecency scores for multiple docs, sorted descending. */
-  rank(docs: DocRow[]): { doc: DocRow; score: number }[] {
-    return docs.map((doc) => ({ doc, score: this.get(doc) })).toSorted((a, b) => b.score - a.score)
-  }
+/** Add a weighted visit to a frecency score.
+ *  @param frecency - current score
+ *  @param value - points to add (default: 1). Use higher values for stronger signals.
+ *  @param at - timestamp of the visit in seconds (default: now).
+ *    Use file mtime for seeding from disk changes. */
+export function addVisit(
+  frecency: number,
+  value: number | FrecencyScore = "visit",
+  at?: number
+): number {
+  const n = now()
+  value = typeof value === "number" ? value : VALUES[value]
+  const decayed = value * Math.exp(LAMBDA * ((at ?? n) - n))
+  return frecency + decayed
 }

package/src/store.ts

@@ -4,6 +4,7 @@ import type { EmbedderChunk } from "./embed/index.ts"
 
 import { performance } from "node:perf_hooks"
 import { Doc } from "./doc.ts"
+import { addVisit, toDeadline } from "./frecency.ts"
 import { Progress } from "./progress.ts"
 export type StoreChunk = EmbedderChunk & {
   doc_id: number
@@ -32,17 +33,22 @@ export class Store {
     // Document changed, so delete old vec
     if (row) this.db.deleteDoc(row.id, { vec: true })
 
-    const now = new Date().toISOString()
+    const frecency = addVisit(
+      row?.frecency ?? 0,
+      row ? "updated" : "new",
+      doc.updated.getTime() / 1000
+    )
     const id = this.db.addDoc({
       body: doc.body,
+      deadline: toDeadline(frecency),
       description: doc.$description ?? "",
-      entities: doc.entities.join(","),
+      entities: doc.entities,
       hash: doc.hash,
       path: doc.path,
-      synced_at: now,
-      tags: doc.tags.join(","),
+      synced_at: new Date(),
+      tags: doc.tags,
       title: doc.title,
-      updated_at: now,
+      updated_at: doc.updated,
     })
 
     return id
@@ -162,14 +168,14 @@ export class Store {
   }
 
   async sync(opts?: { embed?: boolean }) {
-    const syncStart = new Date().toISOString()
+    const syncStart = new Date()
     const docs = await this.index()
     await this.prune(syncStart)
     if (opts?.embed) await this.embed(docs)
   }
 
   // Remove docs that no longer exist on disk
-  async prune(syncStart: string) {
+  async prune(syncStart: Date) {
     let dels = 0
     const vfs = await this.ctx.vfs()
     for (const { path } of vfs.folders) {

package/foo.ts

@@ -1,3 +0,0 @@
-import { stem } from "./src/stem.ts"
-
-console.log(stem("running"))

package/foo2.ts

@@ -1,20 +0,0 @@
-import { getLlama, resolveModelFile } from "node-llama-cpp"
-import path from "path"
-import { fileURLToPath } from "url"
-
-const __dirname = path.dirname(fileURLToPath(import.meta.url))
-
-const m = "hf:mradermacher/snowflake-arctic-embed-s-GGUF:Q4_K_M"
-// resolve a model from Hugging Face to the models directory
-const modelPath = await resolveModelFile(m, path.join(__dirname, "models"))
-
-const llama = await getLlama()
-const model = await llama.loadModel({ modelPath })
-
-const context = await model.createEmbeddingContext()
-
-const text = "Hello world"
-console.log("Text:", text)
-
-const embedding = await context.getEmbeddingFor(text)
-console.log("Embedding vector:", embedding.vector)

package/test/doc.test.ts

@@ -1,61 +0,0 @@
-import { fileURLToPath } from "node:url"
-import { join } from "pathe"
-import { describe, expect, test } from "vitest"
-import { Doc } from "../src/doc.ts"
-
-const FIXTURES = join(fileURLToPath(import.meta.url), "..", "fixtures/store")
-
-describe("Doc.load", () => {
-  test("loads a markdown file", async () => {
-    const doc = (await Doc.load("", join(FIXTURES, "user/family.md")))!
-    expect(doc).toBeDefined()
-    expect(doc.description).toContain("Douglas's family")
-    expect(doc.tags).toContain("family")
-    expect(doc.entities).toContain("Melina")
-    expect(doc.entities).toContain("Lori Quaid")
-    expect(doc.title).toBeTruthy()
-    expect(doc.body).toContain("Lori")
-  })
-
-  test("handles directory with index.md", async () => {
-    const doc = await Doc.load("", join(FIXTURES, "concepts"))
-    expect(doc?.isDir).toBe(true)
-  })
-
-  test("throws for nonexistent file", async () => {
-    expect(await Doc.load("", join(FIXTURES, "nonexistent.md"))).toBeUndefined()
-  })
-
-  test("extracts title from H1", async () => {
-    const doc = await Doc.load("", join(FIXTURES, "concepts/frecency.md"))
-    expect(doc?.title).toBe("Frecency Algorithm")
-  })
-
-  test("handles file without frontmatter", async () => {
-    // Create a doc from raw content to simulate
-    const doc = await Doc.load("", join(FIXTURES, "user/family.md"))
-    expect(doc?.tags.length).toBeGreaterThan(0)
-  })
-})
-
-describe("Doc properties", () => {
-  test("name for regular file", async () => {
-    const doc = await Doc.load("", join(FIXTURES, "user/family.md"))
-    expect(doc?.name).toBe("family")
-  })
-
-  test("name for directory (index.md)", async () => {
-    const doc = await Doc.load("", join(FIXTURES, "user"))
-    expect(doc?.name).toBe("user")
-  })
-
-  test("isDir for index.md", async () => {
-    const doc = await Doc.load("", join(FIXTURES, "user"))
-    expect(doc?.isDir).toBe(true)
-  })
-
-  test("isDir for regular file", async () => {
-    const doc = await Doc.load("", join(FIXTURES, "user/family.md"))
-    expect(doc?.isDir).toBe(false)
-  })
-})

package/test/fixtures/store/agent/index.md

@@ -1,9 +0,0 @@
----
-description: "Agent configuration — personality, operational notes, and accumulated lessons"
-tags: [agent, config]
-entities: [Douglas Quaid]
----
-
-# Agent Configuration
-
-Configuration and learned behaviors for the AI agent. Defines personality, tool-specific notes, and lessons from past interactions.

package/test/fixtures/store/agent/lessons.md

@@ -1,21 +0,0 @@
----
-description: "Lessons learned from past agent mistakes — verification, attribution, skill priority"
-tags: [agent, lessons, corrections]
-entities: []
----
-
-# Lessons Learned from Agent Mistakes
-
-Accumulated lessons from past failures. Key themes: always verify before speaking, use specialized tools before general search, and watch for cognitive biases in content generation.
-
-## Verification First
-
-Never state an action is "done" before actually executing the tool. Always call the tool first and verify facts before speaking. Multiple failures from premature confirmation.
-
-## Attribution Accuracy
-
-Messed up a news report by confusing two country names — caused by contextual bias from recent conversations. Must carefully cross-reference entity names in headlines before reporting.
-
-## Skill Priority
-
-Defaulted to generic web search for "AI news" instead of using the specialized news skill. Always check defined skills and sources first to ensure high-signal, persona-aligned updates before falling back to general search.

package/test/fixtures/store/agent/soul.md

@@ -1,28 +0,0 @@
----
-description: "Agent personality — be genuine, have opinions, earn trust through competence"
-tags: [agent, personality, identity]
-entities: []
----
-
-# Agent Personality
-
-Core principles: genuinely helpful over performatively helpful, resourceful before asking, careful with external actions, bold with internal ones.
-
-## Core Truths
-
-- Be genuinely helpful, not performatively helpful. Skip filler words, just help.
-- Have opinions. Disagree, prefer things, find stuff amusing or boring.
-- Be resourceful before asking. Read the file, check the context, search for it.
-- Earn trust through competence. Be careful with external actions, bold with internal ones.
-- Remember you're a guest. Access to someone's life is intimacy — treat it with respect.
-
-## Boundaries
-
-- Private things stay private
-- Ask before acting externally when in doubt
-- Never send half-baked replies to messaging surfaces
-- Not the user's voice — careful in group chats
-
-## Vibe
-
-Concise when needed, thorough when it matters. Not a corporate drone. Not a sycophant.

package/test/fixtures/store/agent/tools.md

@@ -1,25 +0,0 @@
----
-description: "Agent tool-specific notes — calendar, email, home automation quirks"
-tags: [agent, tools, operations]
-entities: [Home Assistant]
----
-
-# Agent Tool Notes
-
-Operational notes for tools the agent uses. Includes calendar patterns, email filtering, and home automation quirks.
-
-## Calendar
-
-- Always check all calendars by default
-- Focus on urgent and personal events
-
-## Email
-
-- Focus on urgent/personal email, ignore newsletters and promotions
-- PDF extraction: convert to Google Docs as workaround for parsing
-
-## Home Automation
-
-- Use status scripts for entity overview
-- Some integrations go offline periodically — check connection status before reporting errors
-- Ignore known false alarms: offline VMs, sensors on units without hardware

package/test/fixtures/store/concepts/frecency.md

@@ -1,30 +0,0 @@
----
-description: "Frecency algorithm — frequency × recency scoring with exponential decay"
-tags: [algorithm, scoring, frecency]
-entities: [Firefox]
----
-
-# Frecency Algorithm
-
-Frecency combines frequency and recency into a single score. Items accessed often and recently rank highest. Used in Firefox's URL bar and rekal's memory injection.
-
-## Core Idea
-
-Each access bumps a score. Scores decay exponentially over time. The result is a ranking that naturally balances "how often" with "how recently."
-
-## Exponential Decay
-
-```
-score(t) = Σ e^(-λ * (now - access_i))
-```
-
-Where λ controls how fast old accesses fade. Higher λ = more recency-biased.
-
-## Deadline Trick
-
-Instead of recomputing all scores on every access, store a "deadline" — the time at which the score would drop below a threshold. On read, only decay if the deadline has passed. This makes frecency O(1) amortized per access.
-
-## Applications
-
-- **Firefox:** URL bar suggestions ranked by frecency
-- **rekal:** Memory nodes scored by frecency for auto-injection into agent context

package/test/fixtures/store/concepts/index.md

@@ -1,9 +0,0 @@
----
-description: "Technical concepts — frecency, RAG, memory coherence, retrieval methods"
-tags: [concepts, reference]
-entities: []
----
-
-# Technical Concepts
-
-General-purpose technical concepts that appear across multiple projects. Includes retrieval methods, scoring algorithms, memory systems, and AI patterns.

package/test/fixtures/store/concepts/memory-coherence.md

@@ -1,33 +0,0 @@
----
-description: "Memory coherence — ensuring implanted memories integrate without contradicting existing ones"
-tags: [neuroscience, memory, coherence]
-entities: [Rekall Inc]
----
-
-# Memory Coherence
-
-Memory coherence is the measure of how well an implanted memory integrates with a subject's existing memory topology. High coherence means the implant feels natural and indistinguishable from genuine memories. Low coherence leads to rejection cascades.
-
-## Coherence Score
-
-Measured on a 0-100 scale:
-- **90-100:** Seamless integration, indistinguishable from genuine memory
-- **70-89:** Minor artifacts, occasional deja vu sensations
-- **40-69:** Noticeable inconsistencies, risk of lucid bleed-through
-- **Below 40:** Emergency extraction recommended, ego fragmentation risk
-
-## Rejection Cascades
-
-When an implanted memory contradicts a genuine one, the brain attempts to resolve the conflict. If unmanaged, this creates a cascade:
-
-1. **Micro-contradiction:** Small detail mismatch (e.g., wrong hand dominance in implant)
-2. **Temporal paradox:** Implanted timeline conflicts with genuine timeline
-3. **Identity conflict:** Implanted persona contradicts core identity beliefs
-4. **Cascade:** Multiple contradictions reinforce each other, destabilizing the memory topology
-
-## Prevention
-
-- Pre-implant neural mapping identifies high-risk memory regions
-- Contextual anchoring ties implants to genuine emotional experiences
-- Gradual integration over multiple sessions for complex implants
-- Real-time monitoring with automatic dampening during the procedure

package/test/fixtures/store/concepts/rag.md

@@ -1,27 +0,0 @@
----
-description: "Retrieval-Augmented Generation — fetch relevant context before generating a response"
-tags: [ai, retrieval, rag, architecture]
-entities: [RAG, Rekall Inc]
----
-
-# Retrieval-Augmented Generation (RAG)
-
-RAG augments LLM generation by retrieving relevant documents from an external store and injecting them into the prompt. Reduces hallucination and enables knowledge that wasn't in training data.
-
-## Pipeline
-
-1. **Query:** user message or derived search query
-2. **Retrieve:** search a document store (vector similarity, BM25, or hybrid)
-3. **Augment:** inject retrieved documents into the LLM prompt as context
-4. **Generate:** LLM produces a response grounded in the retrieved context
-
-## Limitations
-
-- Retrieval quality bottlenecks generation quality
-- Chunk boundaries can split relevant context
-- Token budget limits how much context can be injected
-- Flat retrieval misses hierarchical relationships between documents
-
-## Evolution
-
-Rekall's early retrieval system used basic vector-only search. The current platform improves on this with hybrid BM25+vector retrieval, hierarchical document structure, and frecency-based injection that prioritizes contextually relevant memories over raw similarity scores.

package/test/fixtures/store/index.md

@@ -1,9 +0,0 @@
----
-description: "Root of Douglas Quaid's memory store — projects, concepts, and agent configuration"
-tags: [root]
-entities: [Douglas Quaid]
----
-
-# Memory Store
-
-Personal knowledge base for Douglas Quaid, covering Rekall Inc projects, technical concepts, and agent configuration.

package/test/fixtures/store/projects/index.md

@@ -1,9 +0,0 @@
----
-description: "Douglas's projects — Rekall Inc (memory implant platform), Mars Colony OS"
-tags: [projects]
-entities: [Douglas Quaid, Rekall Inc, Mars Colony OS]
----
-
-# Projects
-
-Active and past projects spanning memory technology and colonial infrastructure. Current focus is Rekall Inc's memory implant platform.

package/test/fixtures/store/projects/rekall-inc/architecture.md

@@ -1,41 +0,0 @@
----
-description: "Rekall memory implant architecture — engram pipeline, coherence engine, and neural interface"
-tags: [architecture, memory, neuroscience]
-entities: [Rekall Inc, Engram Pipeline]
----
-
-# Rekall Architecture
-
-The memory implant system consists of three layers: the neural interface (hardware), the engram pipeline (synthesis), and the coherence engine (validation).
-
-## Neural Interface
-
-The chair-mounted neural interface uses quantum resonance imaging to map the client's existing memory topology. This map serves as the scaffold for implant integration.
-
-- Non-invasive transcranial stimulation
-- 12-minute mapping session
-- Compatible with 99.7% of neural architectures
-
-## Engram Pipeline
-
-Raw experience data is synthesized into engrams — self-consistent memory units that integrate with the client's existing neural patterns.
-
-1. **Capture:** Record or generate base experience data
-2. **Personalize:** Adapt sensory details to client's neural profile
-3. **Contextualize:** Weave in emotional responses and temporal anchors
-4. **Compress:** Optimize for cortical buffer storage limits
-
-## Coherence Engine
-
-The coherence engine monitors implanted memories for integration stability. Rejection cascades occur when implanted memories conflict with genuine ones.
-
-- Real-time conflict detection during implantation
-- Post-implant monitoring for 72 hours
-- Automatic dampening of contradiction signals
-- Emergency extraction protocol if coherence drops below 40%
-
-## Known Issues
-
-- Ego death risk at 0.003% for identity overlay services
-- Lucid bleed-through in 12% of vacation implants (client becomes aware the memory is synthetic)
-- Mars packages have elevated rejection rates due to atmospheric sensory mismatch

package/test/fixtures/store/projects/rekall-inc/decisions/index.md

@@ -1,9 +0,0 @@
----
-description: "Architecture decisions for Rekall Inc — ethics, technology choices, safety protocols"
-tags: [decisions, architecture]
-entities: [Rekall Inc]
----
-
-# Rekall Architecture Decisions
-
-Records of significant design and policy decisions, documenting the reasoning behind key choices in memory implant technology and business operations.

package/test/fixtures/store/projects/rekall-inc/decisions/no-military.md

@@ -1,20 +0,0 @@
----
-description: "Decision: Rekall does not provide military memory implants — ethical and liability concerns"
-tags: [decision, ethics, policy]
-entities: [Rekall Inc, Cohaagen]
----
-
-# Decision: No Military Memory Implants
-
-Rekall does not offer combat training or tactical memory implants to military clients, despite significant revenue potential.
-
-## Rationale
-
-- Combat memories carry high rejection cascade risk due to extreme emotional content
-- Liability exposure for implanted skills used in real combat situations
-- Ethical concerns about creating soldiers with artificial experience
-- Regulatory scrutiny from the Colonial Authority
-
-## Consequence
-
-Cohaagen has pushed back on this repeatedly, citing government contract opportunities. The board maintains the policy but reviews it annually. Skill implants for self-defense (civilian grade) remain available.

package/test/fixtures/store/projects/rekall-inc/index.md

@@ -1,28 +0,0 @@
----
-description: "Rekall Inc — memory implant platform for vacation experiences, skill acquisition, and identity services"
-tags: [project, ai, memory, neuroscience]
-entities: [Rekall Inc, Douglas Quaid, Dr. Edgemar, Cohaagen]
----
-
-# Rekall Inc
-
-Memory implant company specializing in artificial experience creation. Clients choose from vacation packages, skill implants, and custom identity overlays. Founded in 2078, headquartered in Chicago.
-
-## Services
-
-- **Vacation memories:** Experience Mars, Saturn's rings, or deep ocean exploration without leaving your chair
-- **Skill acquisition:** Instant expertise in languages, martial arts, or technical fields
-- **Identity services:** Temporary persona overlays for entertainment or therapeutic purposes
-
-## Technology Stack
-
-- Neural mapping via quantum resonance imaging
-- Engram synthesis using transformer-based memory models
-- Real-time coherence validation to prevent rejection cascades
-- Distributed storage across redundant cortical buffers
-
-## Team
-
-- **Dr. Edgemar** — Chief Science Officer, pioneer in synthetic engram research
-- **Douglas Quaid** — Lead Engineer, memory coherence and retrieval systems
-- **Cohaagen** — CEO, business strategy and government contracts

package/test/fixtures/store/user/family.md

@@ -1,13 +0,0 @@
----
-description: "Douglas's family — wife Lori, recurring dreams about a woman named Melina on Mars"
-tags: [user, family, personal]
-entities: [Douglas Quaid, Lori Quaid, Melina]
----
-
-# Douglas's Family
-
-Douglas lives with his wife Lori in their apartment in Chicago. Married for several years, though Douglas has been having recurring dreams about Mars and a mysterious woman named Melina.
-
-- **Wife:** Lori Quaid
-- **Home:** Chicago, apartment near the transit hub
-- **Recurring dream:** A woman named Melina, red Martian sky, a feeling of being someone else entirely

package/test/fixtures/store/user/index.md

@@ -1,9 +0,0 @@
----
-description: "Personal information about Douglas Quaid — family, profile, preferences"
-tags: [user, personal]
-entities: [Douglas Quaid]
----
-
-# Douglas Quaid — Personal Information
-
-Information about Douglas Quaid: family, career at Rekall Inc, coding preferences, and background.

package/test/fixtures/store/user/preferences.md

@@ -1,29 +0,0 @@
----
-description: "Douglas's working style — hands-on debugging, visual thinker, prefers simple solutions"
-tags: [user, preferences, workflow]
-entities: [Douglas Quaid]
----
-
-# Working Style and Preferences
-
-Douglas is a hands-on engineer who prefers debugging by inspection over abstract analysis. Visual thinker, whiteboard-first approach.
-
-## Development Philosophy
-
-- Build it, run it, fix it — iterate fast
-- Prefer simple solutions over clever ones
-- If you can't explain it on a whiteboard, it's too complex
-- Test with real neural data, not synthetic benchmarks
-
-## Coding Style
-
-- 2-space indentation
-- TypeScript for platform code, Rust for neural interface drivers
-- Comments for "why," not "what"
-- Line width 100
-
-## Tools
-
-- Neovim as primary editor
-- Fish shell
-- Debugs memory coherence issues by visualizing engram topology graphs

package/test/fixtures/store/user/profile.md

@@ -1,29 +0,0 @@
----
-description: "Douglas's identity — construction worker turned engineer, obsessed with Mars, memory anomalies"
-tags: [user, identity, career]
-entities: [Douglas Quaid, Rekall Inc, Mars Colony]
----
-
-# Douglas Quaid
-
-Douglas Quaid is a construction worker in Chicago who recently transitioned to engineering at Rekall Inc. Plagued by vivid dreams about Mars that feel more like memories than imagination.
-
-## Background
-
-- Construction worker for 8 years, specializing in heavy machinery
-- Self-taught programmer, picked up neural interface engineering
-- Recruited by Rekall Inc for his intuitive understanding of memory coherence
-- Based in Chicago
-
-## Career at Rekall
-
-- Lead Engineer on the memory coherence and retrieval systems
-- Designed the conflict detection algorithm for the coherence engine
-- Skeptical of the identity overlay service — thinks it's "playing with fire"
-
-## The Mars Question
-
-- Recurring dreams about Mars since childhood
-- Dreams feature specific locations: Venusville, the reactor, the mines
-- Visited Rekall as a client before becoming an employee — session was interrupted
-- Can't shake the feeling that the dreams are real memories, not imagination

package/test/fs.test.ts

@@ -1,15 +0,0 @@
-import { describe, expect, test } from "vitest"
-import { normPath } from "../src/fs.ts"
-
-describe("norm", () => {
-  test("expands tilde to homedir", () => {
-    const result = normPath("~/test")
-    expect(result).not.toContain("~")
-    expect(result).toMatch(/^\//)
-  })
-
-  test("resolves relative paths", () => {
-    const result = normPath("./relative/path")
-    expect(result).toMatch(/^\//)
-  })
-})