Add memory provider#13
Open
fivetran-davefowler wants to merge 2 commits into
Open
Conversation
…, OSI framing - confidence is now FLOAT in [0,1] (was free-form varchar) so consumers can threshold/rank - relationship anchors carry the join inline via from_*/to_* (+ paired array columns) instead of a single-table locator; relationship_name is an optional, unenforced pointer to OSI_RELATIONSHIP when present - tighten anchor validation: reject locator columns that don't belong to the anchor type - document when to use memory and that OSI-native teams should prefer object-local ai_context (memory is the no-semantic-layer path) - add agents-schema-memory workflow + composite action + memory-setup.md to match the other providers; link from README - follow OSI parent/child key convention (documented in code + SPEC) - fix memory_path variable shadowing Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a tool-agnostic memory provider: durable, agent-facing notes anchored to the warehouse objects where they're relevant. Supersedes #11 (that PR's branch
notes_providerwas renamed tomemory-provider, which closed it).agents-schema memory --memory-file memory.yml→ writesAGENTS.MEMORY+AGENTS.MEMORY_ANCHOR, registers thememoryprovider inAGENTS.ROOTmemory-setup.md, mirroring dbt/Looker/OSIPositioning (what changed from #11)
Memory is framed as the lightweight path for teams without a semantic layer. If you run OSI, object-local
ai_contextalready carries these notes and memory is largely redundant — the SPEC and setup guide say so plainly rather than overselling. Anchors target physical objects (schema/table/column) on purpose: a column anchor is reachable from raw schema and from an OSI-aware consumer (OSI fields map down to columns); the reverse isn't true.metricandrelationshipare the only logical anchors, for things with no single physical column.Schema / design decisions
confidenceisFLOATin[0,1](was free-form varchar) so consumers can threshold and rank.from_*/to_*with positionally-pairedfrom_columns/to_columnsarrays (handles composite/>2-column keys, mirrorsOSI_RELATIONSHIP).relationship_nameis an optional, unenforced pointer toOSI_RELATIONSHIP.namewhen OSI is present — memory does not depend on OSI.MEMORY(source+confidence) for v1; a separateMEMORY_SOURCEedge table is deferred.confidencerange.MEMORY.memory_id↔MEMORY_ANCHOR.memory_id), documented in code and SPEC.Verification
🤖 Generated with Claude Code