Changelog
What's new.
Every improvement to the platform, as it ships.
· AIService
Read charters from SecurityService; KamoAI-only brief routes
· SecurityService
Internal auth and charter access rules
CharterInternalAuth applies SP02's KamoaiInternalAuth rule to the same secret, so the per-handler guard and the prefix interceptor cannot disagree. CharterAccess keeps SUPERVISE_AI_MEMBERS (alone or with MANAGE_AI_WORKFORCE) to AI targets, as master 6.3 scopes it (ruling SP03-T13).
· MCPGatewayService
MCP 2025-06-18 server at /mcp (stateless streamable HTTP, JSON responses)
One JSON-RPC message per POST: initialize, ping, tools/list, tools/call; notifications and responses answer 202; GET and DELETE answer 405. The body is read after the caller is known, capped at 4 MiB, and must hold exactly one JSON value; a request id is a string or an integer (ruling SP05-T12).
· kamo-internal
Preview a new AI member's charter and brief while adding it
· ConversionService
Transcribe a chunk through AIService's internal façade, routed per org
· KlusterServices
Golden image AI layer — Chrome, x11vnc, computer-use-linux, ydotool
Chrome's source is kamo-google-chrome.list, not google-chrome.list: Chrome's postinst (154.0.8037.57) migrates a google-chrome.list into its own google-chrome.sources, with the keyring the package carries, and deletes it. Google's key file must hold exactly one primary key, and it must be Google's.
· ConversionService
Cut recordings at silences into chunks the AI façade accepts
· MediaService
Name the org when asking for a transcript — ConversionService now routes it through AIService
· kamo-shared-library
Job-posting qualifications with posting-wins de-duplication
· kamo-internal
The member's charter card on Roles & permissions
· MCPGatewayService
The tools/call pipeline — policy, approvals, limits, idempotency, dry run, taint, audit
A stored idempotency entry is answered before the planner reads again (SP05-T11-order); an approved call in a tainted run still answers to the capability and charter checks (SP05-T11-taint); nothing after a successful handler turns it into OUTCOME_UNKNOWN, and untrusted content is withheld while the run cannot be marked (SP05-T11-after); the session's TimezoneType name is the member's zone for daily limits (SP05-T11-zone).
· kamo-shared-library
Role, department and job-title charter write paths; legacy requirements keep other sections
· kamo-internal
Create a job title from one of seven templates
· kamo-shared-library
CharterStamp and the effective-charter wire view
· MCPGatewayService
Tool call audit, 180-day retention purge and internal audit read
The insert's transaction is the repository's save (REQUIRES_NEW), begun and committed inside the writer's catch, so no audit failure reaches a tool call. Rows are always new (one INSERT, no merge). The audit read's page and count each run as their own first statement, which Yugabyte can restart. Ruling SP05-T10.
· MCPGatewayService
Tool visibility by rights, apps, PHI, risk ceiling, taint, capability and charter
The capability gate caches the router's answer per member (SP04 filter 10 narrows candidates by the member's access policies), keeps a failure to get one for 30 s rather than 5 min, and never lets an unexpected error escape; a failed org-facts lookup is UNKNOWN for 5 s rather than a minute (SP05-T9).
· kamo-shared-library
Pure resolver — suppress/lock, additive, specific, restrictive, goals
· kamo-internal
Roles, departments and job titles edit their charter in one editor
· MCPGatewayService
Charter policy, approvals, outreach gate and external recipients
The charter policy compiles SP03's resolved approvals and limits (fail closed when unreachable, refused or without a resolved block); approvals are created and read on kamoai-service's pinned contract with canonical ids; the outreach gate is given the org's IANA zone (Kamo stores TimezoneType names) and never throws from a record.
· KlusterServices
The agent runs the AI workstation profile when cloud-init asks for it
The agent loads kamo_hc_ai only for KAMO_HC_PROFILE=AI_WORKSTATION: the AI's paths on 9810 behind the agent bearer, the MCP bridge on 9811, the AI's activity reasons as the idle clock's sessions, the tidy-up before a hibernate and after a resume, the screen guard on every tick, and the organization's lifestyle logo on the greeter (both profiles). Beyond the plan (SP11-T9 build ruling): every authenticated request notices a resume before it is handled, under a lock held through the reset, so a token, hold or take-over password pushed after a wake is never wiped by the watcher's late tick; /status asks an AI workstation for its activity now rather than reading the last tick; and the profile never runs as a system account.
· kamo-shared-library
Apply by id, legacy requirement replacement, DTO conversion
· kamo-internal
The charter editor: section rail, inherited rows with hide switches, item cards
Drops a hide marker whose target left the chain or has since been locked (SecurityService refuses both), whenever the items or a settled answer for the current subject change; numbers a problem within its section; keeps a half-written paste in its own section; stops adding at the charter's 300-item cap; names the rail and the hide switches for screen readers.
· MCPGatewayService
Downstream calls with the caller's session, internal client, live refresh
Kamo services are called through the BFF's own door per service (*** or a single-use OTK), with the org's workspace host, the actor/run/key headers and spec 4.11's status mapping; internal calls carry KAMOAI_INTERNAL_SECRET and, for K6/KM1, the caller's run and key. rt.org is published for the domains no service announces itself. A connection never opened (refused, unresolvable, connect timeout) is UNREACHABLE; an interrupted or unanswered write is OUTCOME_UNKNOWN; a 4xx is never ambiguous; a failed org lookup is retried after 30 s.
· KlusterServices
AI workstation profile applier, screen guard, software kit and runtime
· kamo-shared-library
MlosAiClient exposes which provider and model answered
· kamo-shared-library
Usage metering columns, routing preferences and budget alert ledger
· MCPGatewayService
Idempotency, limits, run taint, rate limit and OTK minting on Redis
· kamo-shared-library
Charter item entities for roles, departments, job titles and members; operating briefs
· kamo-internal
BFF routes and helpers for AI routing preferences and budgets
· kamo-internal
MCP servers tab for Streamable HTTP servers, masked headers and AI access
Your universe is waiting.
Start free in minutes. Add products whenever you are ready — no migration, no new logins.
Free forever — no credit card required