v0.37 taught the Smarter Project MCP Server to read every repository, every blog post and every manifest schema. v0.38 and v0.39 are about finding and connecting things. SAM annotations become a real integration point, modeled on Kubernetes, that other systems…
SAM annotations are how Smarter connects its resources to the other systems in your organization. SAM, the Smarter Application Manifest, is the YAML format that declares every Smarter resource (LLMClients, Plugins, Secrets, Guardrails and the rest), and its metadata.annotations work…
This is a how-to for a Slack bot that runs as a single pod on Kubernetes and answers questions with a Smarter LLMClient. The bot is about 200 lines of Python, it ships as an optional subchart of Smarter’s Helm…
Every Smarter platform has an MCP server built in. The Smarter MCP Server gives AI agents a working knowledge of Smarter. It reads Smarter’s source code, documentation and blog as they are today. It describes Smarter’s manifests, and checks them…
Every Smarter platform runs the Smarter Project MCP server, which answers questions about Smarter from its own source code and documentation. Until now it read 8 of the project’s public repositories, and nothing else. v0.37 gives it the rest of…
smarter-api is the official Python SDK of Smarter. It’s meant to be to Smarter what the openai package is to the OpenAI api, so one pip install gives your Python code typed access to your own Smarter platform, whether it…
cache-results v0.1 put Smarter’s @cache_results() decorator on PyPI. v0.2 brings the rest of Smarter’s general-purpose caching code with it. That’s lazy_cache, for the raw get() and set() calls that a decorator doesn’t cover, and a log-prefix hook that colors cache…
Every Smarter resource is declared in a manifest with a kind, such as LLMClient, SqlPlugin, Secret, Guardrail, and so on. Until today, the list of kinds lived in two places. The platform defined it, the smarter-api Python SDK kept its…
Smarter has always cached the expensive parts of an AI platform (database reads on every request, calls to slow and billable third-party APIs) with one decorator, @cache_results(). Until today, the only way to use it was to run Smarter. As…
Smarter uses Calico to enforce Kubernetes NetworkPolicies that start its production namespace from deny-all, in both directions, and then admit traffic by pod label. MariaDB and Redis accept connections only from pods labelled app.kubernetes.io/application-group=smarter, the app accepts web traffic only…