Lead
Application Services
SDK Systems Map
Every call has a motive.
Every layer has an alibi.
This is the systems map behind Locus integration: clear layers, predictable routing, safe fallbacks, and controls that keep behavior stable in production.
Co-star
Domain Contracts
Wildcard
Provider Registry
Witness
DTO Boundary
Layer drama board
Click any layer to see what it owns and why it matters.
Layer 1
Prelude
Ergonomic import surface for hosts.
Layer 2
Application
Orchestrates find, recall, explain, aggregate, transform.
Layer 3
Domain
Neutral contracts and request/result types.
Layer 4
Infrastructure
Provider adapters, registries, embedding backends.
Layer 5
Interface DTO
Transport-safe shape conversion boundary.
Path explorer
Switch paths to follow how requests move through the platform.
Find path
- Bound request size for safe execution.
- Collect candidate memory entries for the selected scope.
- Apply filters for relevance and quality.
- Sort and page results consistently.
- Return a stable cursor for the next page.
Provider resolution simulator
Explore how provider selection behaves under different policies.
Resolve
Result: pending
Production commitments
Simple promises that keep operations calm as load and provider mix evolve.
Guardrails
Bounded limits protect performance under load.
Fallbacks
Fallback behavior is explicit and easy to trace.
Feature Flags
Optional capabilities stay isolated and controlled.