stigmergic/container/ at 584a09a8f5a5adc5765e02bc4d757da8af3f3025 · nandi.uk/stigmergic · Tangled

nandi.uk / stigmergic

0

This repository has no description

0

stigmergic / container

5 files

at 584a09a8f5a5adc5765e02bc4d757da8af3f3025

nandi refactor: use carry query for structured matching, drop vault note keyword overlap 2mo ago

refactor: use carry query for structured matching, drop vault note keyword overlap The mapper was producing garbage connections (e.g. "checkin" daily note matched to mental health vertices) because it used raw keyword overlap on vault note content. Carry already exports structured semantic triples via `carry query --format json`. Changes: - Install carry binary in container (patchelf for Nix→Debian compat) - Run `carry query` during sync to export JSON (entities, citations, connections) — always runs, not just after git pull - Rewrite mapper to use carry structured data: 1. Carry connections: match by URL overlap with island vertices, resolve entity names to URLs via carry entity index 2. Carry entities/citations: match by TF-IDF name similarity 3. D1 carry data: same structured matching - Remove vault note content matching entirely - Remove Letta URL discovery (carry records already have URLs) - Add TF-IDF weighting with IDF computed across carry + island corpus - Expand stop words to filter common vault noise - Add connections to D1 getCarryData (worker reads connection records) - Remove Letta env vars from worker/container Performance: 301-vertex island analysis drops from 3.5min to 0.26s. Quality: all connections are real semantic triples, no more noise. Tested locally with `docker run -v carry-vault:/data/carry`. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>

2 months ago

refactor: use carry query for structured matching, drop vault note keyword overlap The mapper was producing garbage connections (e.g. "checkin" daily note matched to mental health vertices) because it used raw keyword overlap on vault note content. Carry already exports structured semantic triples via `carry query --format json`. Changes: - Install carry binary in container (patchelf for Nix→Debian compat) - Run `carry query` during sync to export JSON (entities, citations, connections) — always runs, not just after git pull - Rewrite mapper to use carry structured data: 1. Carry connections: match by URL overlap with island vertices, resolve entity names to URLs via carry entity index 2. Carry entities/citations: match by TF-IDF name similarity 3. D1 carry data: same structured matching - Remove vault note content matching entirely - Remove Letta URL discovery (carry records already have URLs) - Add TF-IDF weighting with IDF computed across carry + island corpus - Expand stop words to filter common vault noise - Add connections to D1 getCarryData (worker reads connection records) - Remove Letta env vars from worker/container Performance: 301-vertex island analysis drops from 3.5min to 0.26s. Quality: all connections are real semantic triples, no more noise. Tested locally with `docker run -v carry-vault:/data/carry`. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>

2 months ago

feat: container-backed deriveIsland and analyze xrpc methods - Container reads vault via ob sync, carry via git pull - deriveIsland: with seed → single island, without → all islands - analyze: cross-references island against vault+carry - Lexicon methods: org.latha.strata.deriveIsland, org.latha.strata.analyze - StrataContainer Durable Object manages container lifecycle - carry-vault pushed to github.com/codegod100/carry-vault (private) 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>

2 months ago

refactor: use carry query for structured matching, drop vault note keyword overlap The mapper was producing garbage connections (e.g. "checkin" daily note matched to mental health vertices) because it used raw keyword overlap on vault note content. Carry already exports structured semantic triples via `carry query --format json`. Changes: - Install carry binary in container (patchelf for Nix→Debian compat) - Run `carry query` during sync to export JSON (entities, citations, connections) — always runs, not just after git pull - Rewrite mapper to use carry structured data: 1. Carry connections: match by URL overlap with island vertices, resolve entity names to URLs via carry entity index 2. Carry entities/citations: match by TF-IDF name similarity 3. D1 carry data: same structured matching - Remove vault note content matching entirely - Remove Letta URL discovery (carry records already have URLs) - Add TF-IDF weighting with IDF computed across carry + island corpus - Expand stop words to filter common vault noise - Add connections to D1 getCarryData (worker reads connection records) - Remove Letta env vars from worker/container Performance: 301-vertex island analysis drops from 3.5min to 0.26s. Quality: all connections are real semantic triples, no more noise. Tested locally with `docker run -v carry-vault:/data/carry`. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>

2 months ago

refactor: use carry query for structured matching, drop vault note keyword overlap The mapper was producing garbage connections (e.g. "checkin" daily note matched to mental health vertices) because it used raw keyword overlap on vault note content. Carry already exports structured semantic triples via `carry query --format json`. Changes: - Install carry binary in container (patchelf for Nix→Debian compat) - Run `carry query` during sync to export JSON (entities, citations, connections) — always runs, not just after git pull - Rewrite mapper to use carry structured data: 1. Carry connections: match by URL overlap with island vertices, resolve entity names to URLs via carry entity index 2. Carry entities/citations: match by TF-IDF name similarity 3. D1 carry data: same structured matching - Remove vault note content matching entirely - Remove Letta URL discovery (carry records already have URLs) - Add TF-IDF weighting with IDF computed across carry + island corpus - Expand stop words to filter common vault noise - Add connections to D1 getCarryData (worker reads connection records) - Remove Letta env vars from worker/container Performance: 301-vertex island analysis drops from 3.5min to 0.26s. Quality: all connections are real semantic triples, no more noise. Tested locally with `docker run -v carry-vault:/data/carry`. 👾 Generated with [Letta Code](https://letta.com) Co-Authored-By: Letta Code <noreply@letta.com>

2 months ago