Changelog
What's new.
Every improvement to the platform, as it ships.
· kamo-internal
The task.assigned tone rides the TASK_ASSIGNED notification; TASK_CHANGED is gone
task.assigned now plays while the tab is visible, as every tone the deck rings does: the deck names no surface, so a playsWhenFocused:false tone there was heard only from a background tab.
· SecurityService
Audit role and security changes; ARTIFICIAL template and AI floor in model endpoints
· MediaService
MediaService announces its own webinar writes
· EmailService
An emailed invitation keeps its recurrence, edited and cancelled instances
An invitation to one date of someone else's series stays the event it describes instead of being refused as an orphan instance, and a series whose organiser moved to a rule the calendar cannot expand stops repeating instead of keeping its old dates.
· MediaService
Relay notification frames to the phone; voicemail gets its own topic
Every pod relays core-NATS email.notify.<memberId> to /topic/notifications/<memberId> on its own broker, for KamoMobile's notification centre. voip.voicemail.* now goes to **************** instead of the SMS topic, and that new topic is guarded per member with client SEND refused.
· SecurityService
Member profile AI state, relabel locks, immediate rights recalculation and audit
· EmailService
Guests hear about one moved or cancelled instance; invitations state the repeat
The instance's ics names the whole guest list and goes to every guest already told; a cancelled instance outranks every notice sent about it; an all-day invitation states its date, not midnight.
· MediaService
Status endpoints, a REST heartbeat, and guarded org and notification topics
· SecurityService
Internal routes for credentials, the exchange, the roster, profiles, the charter and the sweep
· SecurityService
Org AI workforce pause-all and the platform kill switch endpoints
· EmailService
Provision an AI member's mailbox for the SP02 MAILBOX hire step
POST **************** (spec E6, §4.12) behind KAMOAI_INTERNAL_SECRET: KamoMail creates <first.last>@<verified domain> (base, base2 … base99), other providers assign a mailbox an admin created, SMTP-only answers NOT_APPLICABLE. Beyond the brief's code (ruling SP08-T22): a row carrying only this member's own assignment is finished rather than skipped, so a retry converges; a mailbox another hire made primary meanwhile is handed back and the next address taken, so no AI member keeps another's mailbox; a transaction that cannot begin or commit answers 503 RETRY like a DataAccessException.
· MediaService
Status text and actor type, told to the member's organization
· EmailService
Read ics from Google, Outlook and Apple — zones, dates, series and instances
· MediaService
An internal direct-message endpoint for chat lines other services write
· EmailService
Dovecot push endpoint; push-covered KamoMail mailboxes stop holding IMAP IDLE
· MediaService
Every chat sender goes through the one fan-out
Alerts, web-chat visitors, the AI Sales Agent, inbound social messages and the Exec2Exec desk now announce through ChatFanoutService: alerts reach the recipient's window, badge, phone and notification centre; the others keep their own frames and keep the AI turn counter honest; Exec2Exec raises unread-chat cards for its own raise set and admits AI posts through the turn guard. Every sender's frame carries senderIntelligenceType and mentions. A session created in the sender's own transaction has a null roster collection, so the fan-out reads its members from the table: the first message of a new thread (an alert, a calendar line) tells its recipient.
· SecurityService
AI member state, pause/resume/retire and hiring checklist endpoints
· EmailService
One ics writer for invitations, CalDAV and export — series, exceptions, zones
· KlusterServices
The default user may only PING
SP00 stage R3. Persists the runtime rule for a future start of redis-0: default keeps nopass for the unauthenticated readiness probe and may run PING and nothing else. The NetworkPolicy header no longer says the store has no password.
· EmailService
Watch active AI members' mailboxes for arrivals
AiMailboxWatcher keeps a pod-local "ai" IDLE claim on every active AI member's IMAP-reachable mailbox (ARTIFICIAL, record active, membership ACTIVE), skips mailboxes with no IMAP, keeps claims through a failed read or resolve, and releases a mailbox once no AI member claims it (left, no longer IMAP-reachable, or moved to another primary mailbox). Kill switch email.ai-mailbox-watch.enabled.
· MediaService
The live relay carries sender intelligence and mentions
· SecurityService
Pause, resume and retire AI members; org pause-all; the platform kill switch
· AIService
Chat, routing and the model picker run on the registry; capability backfill replaces the pricing backfill
· EmailService
Raise NEW_EMAIL server-side from every inbox arrival
· MediaService
History and rosters carry mentions and who is an AI
· EmailService
Free/busy, working-hours and reminder-methods endpoints
· SecurityService
Hire AI members as seat-consuming team members with hire steps and no mail
· AIService
Catalog and coverage, platform console API, internal registration and attestation, health sweep
· EmailService
Meeting emails wear the organizer's compose template; escape event fields
Invite, update, cancel and RSVP bodies are wrapped for the sending member and their data: images leave as cid: parts (InlineImageTransport). **************** suspends its caller's transaction, so the template's reads never join the invite's.
· MediaService
Mentions follow an edit; only newly named members are told
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