Repository navigation
Conversation
Add a "systemone" provider kind alongside "jev" so AML memory-agent deployments can use self-hosted or custom System One servers (such as Karpo Decision 31B or local Ollama clef/clef-flash) over POST /v1/systemone without JEV model pinning, paid budget requirements, or mandatory API keys. - Accepts https:// or loopback http:// baseURLs and normalizes base, /v1, and /v1/systemone paths. - Leaves all existing "jev" invariants (pinned versions, strict metering, USD billing, BYOK, budget caps) untouched. - Enforces fail-closed credential checks when keyEnv is explicitly configured, uses the 128-question batch limit and interactive decision timeout, and rejects completion calls. Validation: go vet ./... and targeted memoryagent/aml/architecture tests pass.
audreyt
force-pushed
the
feat/memoryagent-systemone
branch
from
November 22, 2026 00:45
18ad06d to
b0f58e5
Compare
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.
Add a
"systemone"provider kind alongside"jev"so AMLmemory-agentdeployments can use self-hosted or custom System One decision servers (such as Karpo Decision 31B or local Ollamaclef/clef-flash) overPOST /v1/systemonewithout JEV version pinning, paid budget requirements, or mandatory API keys.Summary of changes
internal/memoryagent/provider.go: Addkind: "systemone"acceptinghttps://or loopbackhttp://baseURLs, normalizing base,/v1, and/v1/systemonepaths. Reuses the System One decision path (MaxQuestions() == 128, rejectsComplete), parsesusagewithout JEV USD billing, and checkskeyEnvfail-closed when explicitly configured. Leaves all"jev"invariants untouched.internal/memoryagent/budget.go: Treat"systemone"as unpaid (like"local"), requiring no paid budget reservation.internal/memoryagent/resilience.go: ApplyinteractiveDecisionTimeoutto"systemone"calls.internal/memoryagent/keys.go: Recognize"systemone"inKindName,modelsURL, andcheckBody.internal/memoryagent/provider_test.go: AddTestSystemOneProviderSupportsKarpoDecisioncovering Karpo-shaped responses, endpoint normalization, keyless loopback, HTTPS + optionalkeyEnv, and non-loopback HTTP rejection.Example
memory-config.jsonValidation
go vet ./...go test ./internal/memoryagent ./test/mnemond/architecture -count=1karpo-decision-31BoverPOST /v1/systemone.