Live Change Log

Every feature, fix and improvement, posted as it ships. Nothing is held back for a launch.

18,391

Total Changes

6,526

Features

5,537

Fixes

Projects

Filter by project

All Projects18,391 AIService276 APIService177 BillingService161 ConversionService117 DaemonService146 DocsService240 ESigService93 EmailService619 InitializerService344 KBService162 KlusterServices769 MCPGatewayService277 MediaService620 RAGService79 SecurityService1,995 TranslateService62 VOIPService265 VectorService11 kamo-apps26 kamo-asterisk-support28 kamo-capcha17 kamo-capcha-widget4 kamo-internal8,691 kamo-login342 kamo-marketing642 kamo-nowww20 kamo-register213 kamo-shared-library1,824 kamo-signer-monorepo57 kamolos114

Filter by type

All Types Build23 CI525 Chore794 Docs3,286 Feature6,526 Fix5,537 Other1,001 Performance174 Refactor281 Revert23 Style45 Test175 Upgrade1

October 15, 2026

FixMCPGatewayService

"list…", "show…", "give me…" and "pull up…" are orders too, and a run with no order says why in the log

Live check in sp00verify (2026-10-15): a peer's "Nell, list the open tasks assigned to you and tell me how many there are." verified as their request (author, a...

Kamo·3w ago

FeatureMCPGatewayService

The No Insubordination Rule — an SI carries out a teammate's direct order on their rights

Owner 2026-10-15, refined the same day: "It should apply to any team member. But just because a team member (human or SI) has more rights, does not mean that au...

Kamo·3w ago

FixMCPGatewayService

A team member's call to a number on the do-not-contact list reads as who asked not to be called, and since when

kamoai-service 8b7b8d5 added the organization's do-not-contact list for calls (K6 409 DO_NOT_CONTACT), and a team member's call now carries the day the number w...

Kamo·3w ago

FixMCPGatewayService

An uncited wake stands for an outside call only when its words ask for a call

The run's own wake (RequestVerifier.inferFromRun) is the request for a call to a colleague, but someone outside the org is rung on a teammate's name, with no co...

Kamo·3w ago

FixMCPGatewayService

Phone_call calls whoever a team member named, looked up by name, with no approval and no consent gate, and never anyone else

Owner 2026-10-15: "When a supervisor, or any team member for that matter, tells SI to call someone else on the team, they should call them. No questions asked, ...

Kamo·3w ago

October 14, 2026

FixMCPGatewayService

Meetings_join is JOIN_MEETING, not PLACE_CALL, and an unnamed JOIN_MEETING does not ask

Owner 2026-10-14: Luna (crm) asked the owner to approve joining a meeting he had told her to join; meetings_join was classed PLACE_CALL, so the charter's "Placi...

Kamo·3w ago

FixMCPGatewayService

Meetings_join is "Join a meeting", not a phone call, and a meeting's link is joined as the room it names

Owner, 2026-10-14: SIs asked to join a meeting answered that they could not "join by phone" because "there's no dial-in", and asked for a room with dial-in enab...

Kamo·3w ago

FixMCPGatewayService

An SI acts on the request its run was woken by without having to cite it, and K3 hears the tool's rights so a colleague who may do it themselves can direct it

Owner 2026-10-14: Luna (crm) asked the owner to approve joining the meeting he had just told her to join. Evidence: run 47cc1908 (NEW_CHAT, woken by his message...

Kamo·3w ago

FixMCPGatewayService

An AUDIT org's SI is shown the record-link kinds every SI saw before KamoCollab

CP97 Task 17's Luna compare found her tools/list changed by KamoCollab: CP05 Task 7 appended TASK, DOCUMENT, KB_ARTICLE, MEMBER, AI_RUN and SMS_THREAD to Record...

Kamo·4w ago

FixMCPGatewayService

Stamp a communication-policy refusal of a tool with no intent COLLAB_DENY interaction:<ruleId>

An SI's chat_find_or_create_dm refused by the interaction policy answered COLLAB_DENIED INTERACTION_POLICY but left its audit row's policy_decision and policy_r...

Kamo·4w ago

FixMCPGatewayService

Build-info runs at prepare-package, so a test run (offline included) never resolves its extra plugin dependencies; CI's package still writes build-info.properties for the release fingerprint (KamoCollab CP15 D14, follow-up)

Kamo·4w ago

FixMCPGatewayService

An SI's own record with nothing behind it names nobody to ask — CP05 refuses every person's release of a record no person owns or takes part in, yet a withheld SI record with no resolvable source was still routed to the SI's supervisor; live A1 of CP07 Task 43 (run 17): the rep's question about Harbor Point was routed with the SI's two plan tasks beside four releasable KB articles, so the owner's summary dry run answered NOT_PARTICIPANT twice and the release form could only decoder; such a recor...

Kamo·4w ago

FixMCPGatewayService

An SI's withheld note asks about only what the audience may not know, and asks a person who takes part — live A1 of CP07 Task 43 (run 17): a rep's run withheld the SI's journal and passed it on as every chat it learned from, the rep's own chats included, each routed first to the SI's supervisor (the org owner stands in for the SI participant), so the release proposal named ten sources and the owner's summary was refused NOT_PARTICIPANT by CP05; an SI record is now passed on only as the inherited...

Kamo·4w ago

FixMCPGatewayService

An approved re-execution is never refused INTENT_REQUIRED — the approval stores the tool's own arguments only, so in an ENFORCE org every approved send that starts a conversation (a release by the information's owner, or the charter's approval) failed INVALID_ARGUMENTS on re-execution: live A5 of CP07 Task 43, approval 3a7b843e FAILED after Noseat approved it; the call stated its purpose when it was first made, and a person has since approved it (ruling CP07-T43-4)

Kamo·4w ago

TestMCPGatewayService

The owner's verified request releases her Confidential DM to a department she does not head — live A2 of Task 43 was DENIED NO_SINGLE_RELEASER until shared-lib 0074aca4 (the organization span covers every team and department, ruling CP07-T43-3); this build picks it up (KamoCollab CP07 Task 43)

Kamo·4w ago

FixMCPGatewayService

An SI's own note is passed on as what it learned from — disclosure_request routed a withheld SI card (private to the SI, Confidential with its setter) to that setter or the SI's supervisor, whose summary of it CP05's release authority then refused NOT_PARTICIPANT (no person owns or takes part in an SI's note), so the owner's release form always blocked; a withheld record no person owns or takes part in now stands in the withheld store for its resolved inherited sources (walked through further su...

Kamo·4w ago

October 13, 2026

FixMCPGatewayService

An outside party's own record clears only its external view, and only when it is theirs — a send's leadUid (mail_send, sms_send) or contactRef (phone_call) aliases an outside recipient only when that lead or contact holds the recipient's address or number (one keyed read: leads by leads_pkey, the org compared on the row; a contact by its primary key through its book in the org), so a cc'd vendor, a mistyped address or another lead's number is never cleared as OWN_RECORD; and the gate's new step ...

Kamo·4w ago

RefactorMCPGatewayService

A person's consult route order moves to collab/ConsultChannels — their stated order, then the SI's CHANNEL_ORDER for the relationship, then CHAT, EMAIL, ASYNC, each route once; CollabPack, which also plans collab_position, now names no personality type; behaviour unchanged (KamoCollab CP13 Task 22, D19, ruling CP13-T22-1)

Kamo·4w ago

TestMCPGatewayService

Collab_position stays personality-free — CollabPack references nothing in com.kamo.z.shared.personality, and charters that differ only in PERSONALITY (CONFLICT_STYLE AVOID vs CHALLENGE, or none) send KBService identical requests with disagreementThreshold from the DISAGREEMENT escalation bound (2 with one, else 3) (KamoCollab CP13 Task 22, D19)

Kamo·4w ago

FeatureMCPGatewayService

An offered SI's send says what it was in the result's _meta["kamo.collab"] — purpose, urgency, regarding, intent source, outcome (SEND, or DEFER with deliverAfter), the colleagues reached with kind and person flag (the gate's own recipients when it judged them, else the plan's with CollabCallFacts.kindOf and the org graph), the thread and a consult's id; written before the key is DONE so a replay carries it, on delivered and deferred INTENT calls of SIs IntentOffer offers; content and structured...

Kamo·4w ago

FeatureMCPGatewayService

Tasks_list_comments shows a comment's kind and stance when it is not a plain comment — a POSITION, HANDOFF or ESCALATION row adds kind (and stance when it has one) for the disagreement protocol and the runtime; a COMMENT row, or one KBService gives no kind, is byte-identical to before (KamoCollab CP13 Task 9, D30)

Kamo·4w ago

October 12, 2026

FeatureMCPGatewayService

An SI whose PERSONALITY is configured is offered the intent arguments — IntentOffer = CP12's CollabOffer, or an SI with a configured personality; tools/list adds purpose, urgency and regarding to its INTENT tools, IntentResolver resolves its calls as an offered SI's (MISSING, never NOT_OFFERED) and its stated record joins the communication-policy question; the collab_* tools and the ENFORCE rejection of a missing purpose keep CP12's offer; an SI with neither section keeps the golden schemas byte...

Kamo·4w ago

TestMCPGatewayService

Golden schemas of an SI with neither a DocsTION nor a PERSONALITY section, captured from origin/main before CP13 changes the intent offer; **************** compares every catalogue tool byte for byte (KamoCollab CP13 Task 8)

Kamo·4w ago

TestMCPGatewayService

Notifications_list offers every kind EmailService knows except those that never reach an SI — SP05's check follows the pinned filter (KamoCollab CP07 final fix 1, ruling CP07-FF-1)

Kamo·4w ago

FixMCPGatewayService

Someone outside an ENFORCE organization is told only their own record's external view — in an EXTERNAL or MIXED run, leads_search reduces each row to spec §5.18's projection as the grid row carries it (uid, companyName, status, primaryContact, addressMailing, mortgageFields, the team member by name and role), leads_history answers 'Not found.' without asking SecurityService (every line is an internal field), accounts_search and accounts_get keep only who the customer is and how to reach them, an...

Kamo·4w ago

FixMCPGatewayService

Every SI's tools/list is CP04's again — notifications_list's kind filter is a pinned list of the kinds an SI can receive, not NotificationKind.values(), so DISCLOSURE_REQUESTED (sent only to a person, a release's human approver) leaves the schema every SI of every org has served since CP07 Task 5; a kind added later is offered only deliberately (NotificationsPackTest fails until each kind is pinned or listed as never reaching an SI); the AUDIT and memory-off snapshots lose the kind, ToolListPari...

Kamo·4w ago

TestMCPGatewayService

ReportsHiddenWithoutWatches ignores the collab_* tools a configured charter also offers (KamoCollab CP14 Task 12)

Kamo·4w ago

FeatureMCPGatewayService

An SI hands its task to a colleague and states its position on a task — collab_handoff and collab_position (pack collab, AI_ONLY, EDIT_NOTES, opened by CP11's charterSwitch DocsTION, offered in ENFORCE too): a hand-off names an active colleague other than the SI (else INVALID_ARGUMENTS NOT_A_COLLEAGUE) and a task the SI can read and is the assignee or creator of (a task without a recorded creator is its list owner's; else, or unreadable, INVALID_ARGUMENTS NOT_YOUR_TASK); it is ASSIGN_WORK j...

Kamo·4w ago

FixMCPGatewayService

A refused collab_* call's dry-run report names its colleagues — CP15 Task 6 gave DocstionGate.report a targetMemberIds argument after CP12 Task 29 was written, so Task 29's rebased refusal branch no longer compiled; the refusal's dry run now reports the same colleagues its COLLAB_DENIED names (KamoCollab CP12 Task 29, found by Task 30)

Kamo·4w ago

FeatureMCPGatewayService

An SI asks a colleague and answers an SI that asked — collab_consult and collab_answer (pack collab, AI_ONLY, opened by CP11's charterSwitch DocsTION, offered in ENFORCE too): a consult to an SI colleague that takes consults (its org in ENFORCE or its own DocsTION switched on, else COLLAB_DENIED NOT_DocsTING) is recorded in kamoai-service's POST /api/kamoai/internal/consults with the asking run as parentRunId and the run's onBehalfOf chain plus the SI (more than five, or back alon...

Kamo·4w ago

FeatureMCPGatewayService

The Tool Plane's build identity and an SI's daily Docstion counts — GET /api/tool-plane/internal/build answers {service:"mcpgatewayservice", version, time} from Spring Boot's BuildProperties (pom.xml runs build-info; both null without it); GET **************** answers {orgId, memberId, day, contacts:{started, replies, deferred, rerouted, denied, approvalRequired}, escalationSends} for one SI and UTC day from its real, gate-stamped calls in its org...

Kamo·4w ago

FeatureMCPGatewayService

An SI's first contact with an outside person needs CONTACT_NEW_PERSON (defect 7) — mail_send and mail_forward list each outside address (email:<lower>), sms_send and an outside phone_call the number (phone:<E.164>), as ToolPlan.FIRST_CONTACT for an SI, and each declares CONTACT_NEW_PERSON; the Docstion gate, for every SI and not on an approved re-execution, drops the people the run already speaks with and asks AIService's POST **************** (FirstContactClient: 20 ...

Kamo·4w ago

FeatureMCPGatewayService

Rehearsal run contexts on the Tool Plane — a run whose context carries CP15's rehearsal block takes dry-run calls only (a call or tools/list without X-Kamo-Dry-Run answers UNAVAILABLE REHEARSAL_RUN_DRY_ONLY before anything runs); simulateEnforce judges that run in ENFORCE (EffectiveDisclosureMode) in the audience filter, the read audience, the disclosure gate and disclosure-check, and the tool list (disclosure_request, basis, sourceRef); a non-blank privateContext is recorded as the run's Confid...

Kamo·4w ago

FeatureMCPGatewayService

SI loop guards in the Tool Plane — an SI's tasks_comment sends aiTurnLimit and its mail_reply the multipart field aiTurnLimit, both its charter's maxAiOnlyChatTurns (6 by default), so KBService's and EmailService's thread turn guards hold it to its own limit (their 429 AI_TURN_LIMIT answers WAIT_FOR_HUMAN, as in chat; a person's comment or reply is unchanged); and the SI pair budget (AiPairBudget): beside the charter's limit counters, an SI's disclosing send takes one unit on kamo:collab:pair:<o...

Kamo·4w ago

FixMCPGatewayService

Label on write of SI memory fails closed in every mode — memory_record and a memory-on SI's journal line are not written when the ledger, org graph or settings cannot be read (UNAVAILABLE DISCLOSURE_UNAVAILABLE) or the SI calls outside a run (UNAVAILABLE RUN_CONTEXT_MISSING), AUDIT included, so no unlabelled PRIVATE card reaches the SI's management chain (KamoCollab CP11 final review, ruling CP11-FF-1)

Kamo·4w ago

FeatureMCPGatewayService

A deferred SI message goes through the disclosure gate to the outbox — when the Docstion gate DEFERs an SI's chat_send in a direct chat or its mail_send to one colleague, the call still meets CP07's disclosure gate (an ENFORCE refusal stops it, nothing queued), the charter's outcome, the limits and the outreach gate, and OutboxDefer then replaces the handler: the gate's snapshot (with the run's sealed excerpts of its sources) is kept 73 h as kamo:tool:held:outbox:<itemId>, the item is poste...

Kamo·4w ago

FeatureMCPGatewayService

The Docstion gate — an SI's call of an INTENT tool is judged where CP04's interaction gate stood: its intent (ToolPlan.INTENT; an offered SI of an ENFORCE org that starts a contact without a purpose is refused INVALID_ARGUMENTS INTENT_REQUIRED), CP04's communication policy as step 1 (a refusal stamps COLLAB_DENY interaction:<ruleId>, an approval it asks for COLLAB_REQUIRE_APPROVAL), then, for an SI whose DocsTION charter is configured only, CollabCallFacts and DocstionPolicy per r...

Kamo·4w ago

FeatureMCPGatewayService

The reports pack — reports_list, reports_run and metrics_get under the caller's own report rights (KamoCollab CP14 Task 12)

reports_list reads SecurityService's report library on the caller's session: the reports they may run, the measurable metrics of those reports and, for an SI ca...

Kamo·4w ago

FeatureMCPGatewayService

The SI intent arguments — purpose, urgency and regarding on an offered SI's INTENT tools (CollabTools: INTENT and NO_INTENT with reasons, every disclosing tool ruled), injected by tools/list only for an SI whose Docstion is configured or whose org is in ENFORCE (an unconfigured SI of an AUDIT org keeps byte-identical schemas), taken out of an SI's arguments beside onRequestOf before the schema check, the planner and the args hash and checked (INVALID_ARGUMENTS with field); IntentResolver: v...

Kamo·4w ago

FeatureMCPGatewayService

Seed an SI run's source ledger, and the WATCH charter switch — POST **************** (X-Internal-Auth) takes {orgId, memberId, items:[{ref, excerpt}]}: 1-5 canonical refs with excerpts of at most 4,000 characters (else 400 items), labels them through LabelService and records each in the run's source ledger as a read of tool runtime:signal, its excerpt sealed (204); a run with no registered context of this SI is 404 RUN_CONTEXT_MISSING; an AUDIT org whose calls go une...

Kamo·4w ago

FeatureMCPGatewayService

Knowledge_context — an SI's standing knowledge through kbservice's GET /api/notes/ai/context, passed through: Our Master Note, the knowledge notes (the charter's, then its teams' and departments' pinned notes) and the decisions in force, each entry its NOTE at /orgMaster/i, /knowledge/i and /decisions/i; pack memory (AI_ONLY, NOTES, READ, VIEW_NOTES), offered only when the SI's charter sets maxContextKnowledgeChars to 1 or more (ENFORCE alone never offers it); at most 8 noteIds; a strict read, s...

Kamo·4w ago

FeatureMCPGatewayService

The SI memory tools, the charter switch and strict reads — memory_record, memory_search and memory_forget (pack memory, AI_ONLY) over kbservice's /api/notes/memory; ToolDescriptor.charterSwitch, the program's one opt-in rule (R1-5): a tool naming a switch is offered to an SI only when its charter sets that LIMIT key to 1 or more, or its org is in ENFORCE and the switch lets ENFORCE offer it, else hidden as CHARTER_SWITCH_OFF; the memory tools' switch is maxMemoryCards with ENFORCE offering nothi...

Kamo·4w ago

FeatureMCPGatewayService

Label on write for SI memory — LabelOnWrite.forMemory links a card or a memory-on SI's journal line to every labelled source of its run, or, in ENFORCE with the leak check on, to its basis alone when the check finds the fact clean of everything else the run read (LEAKS, UNSURE, a failure, a source without its excerpt, AUDIT and a disabled check keep every source); unlabelled content and a source past 49 add AI_RUN:<runId>; the highest sensitivity of every chosen source, Confidential when any is,...

Kamo·4w ago

FeatureMCPGatewayService

Disclosure readiness — GET **************** answers whether an org may switch to ENFORCE: pack coverage (every READ static tool ruled LABELED or NOT_CONTENT), the excerpt key, and one leak-check probe with a fixed synthetic draft and excerpt (REACHABLE on any verdict but AIService's no-model UNSURE, within 8 s; DISABLED when the org's leak check is off), with the org's SI-enabled federated servers and its last seven days of WITHHELD, WOULD_WITHHOLD and UNLABEL...

Kamo·4w ago

FeatureMCPGatewayService

Label on write and the runtime's two internal endpoints — an SI's notes_create, notes_update, notes_append_journal and notes_master_append in a run send, in the same request, LEARNED_FROM links to what the run read (its basis, else every labelled source of its ledger; never an unlabelled one or an AI_RUN; at most 50, newest first), the highest sensitivity among them and the Confidential marker with its highest-ranked setter (org owner, then effective level, then id; an unknown setter stands for ...

Kamo·4w ago

FeatureMCPGatewayService

Decisions and note sharing for an SI of an ENFORCE org — decisions_search lists the decisions and summaries it may read, each named as its NOTE; decisions_create records one released at birth and notes_share gives one of its own notes a new audience, both through kbservice's internal release endpoints with the basis the disclosure gate allowed the call on (CLEARED with no grant, VERIFIED_REQUEST by a verified request's author, APPROVAL by the information owner whose release cleared it; without o...

Kamo·4w ago

FeatureMCPGatewayService

Disclosure_request and the approval status of a proposal — an SI of an ENFORCE org passes a colleague's question on to the owners of what its run's reads withheld: forMemberId must be in the run's audience, each withheld source (newest first) goes to its first release owner other than the requester, at most 5 owners with 10 sources each, one RELEASE_PROPOSAL (reason DISCLOSURE, class RELEASE_INFORMATION) per owner keyed <key>:owner:<id> with only that owner's sources, at most 3 calls a run; the ...

Kamo·4w ago

FeatureMCPGatewayService

Approved releases, their re-execution and chained approvals — the information owner's approval of a held send is recorded in its snapshot as their OWNER_RELEASE over the sources it was asked for (the snapshot now names that asked release), and the gate decides again from the snapshot with fresh labels, needing neither the run's context nor its ledger; a release that no longer covers the send (a marker set meanwhile) is DISCLOSURE_DENIED, never asked again; a release reaches only the recipients i...

Kamo·4w ago

FixMCPGatewayService

An AUDIT hit of the communication policy is written once, as the call runs — not also when the charter asks a person first, and not for a decoderd approval (KamoCollab CP04 Task 31)

Found live in sp00verify: an SI's internal email under an AUDIT DENY rule, behind a charter approval (autonomy ceiling 1), wrote two chat_policy_event rows for ...

Kamo·4w ago

FeatureMCPGatewayService

The disclosure gate — an SI's call of a disclosing tool is judged after CP04's interaction gate and before any approval: the run's source ledger, the records the call carries and its basis (which must be what the run read, else BASIS_NOT_READ in ENFORCE) are labelled now and decided with DisclosurePolicy, the verified request as a VERIFIED_REQUEST grant and a held snapshot's releases as OWNER_RELEASE; in ENFORCE the run's other uncleared reading goes to the bounded leak check (LeakPrefilter, Lea...

Kamo·4w ago

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free Forever View Pricing