Changelog
What's new.
Every improvement to the platform, as it ships.
· MCPGatewayService
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-internal
The Organization charter tab — /settings/ai?tab=org-charter loads the organization's own charter layer and hosts CharterEditor at the ORG level on the org id (the id the resolver gives the ORG layer), saves the whole list, reads the answer back and then keeps the text the preview showed (saving is the approval); read-only with its reason when the answer is not editable, Save off while the client validator finds a problem, a padded error with Retry when it cannot load; the page and the settings m...
· MCPGatewayService
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...
· SecurityService
ENFORCE needs readiness — a PUT of **************** that would switch the org to ENFORCE first asks the Tool Plane's GET **************** with the program secret (ToolPlaneReadinessClient, kamoai.tool-plane.internal-url, 3 s/10 s); not ready is 409 {reason:DISCLOSURE_NOT_READY, missing}, unreachable or unreadable 503 {reason:READINESS_UNAVAILABLE}, and either way nothing is written and nothing audited; ready saves with CP05's HIGH audit row; a...
· kamo-internal
The SI hire wizard's Review step — six sections on a tab rail (Who it is, Where it works, Its charter, Voice, Hiring options, What the assistant noted), stacked above the section on a phone; Continue to hire needs names, a sex and a supervisor and lists what is missing with links to its section; PlacementSection offers the draft's New: {title} only to a CONFIGURE_SYSTEM holder and checks the supervisor's coverage with K3; CharterSectionStep renders CP09's CharterEditor at MEMBER for hireSubject(...
· kamo-internal
The communication policy also under Security, for every organization
Owner: "Also under Security". The CP04 policy tab now also renders on /settings/security (tab=communication-policy), with a Security menu entry, a Security landing card and an admin-bar entry (master R1-37), so an organization without the Chat app reaches it. The Chat placement stays. Gated by the Security page's own MANAGE_ACCESS_RULES, which mediaservice now accepts on the policy endpoints beside MANAGE_CHAT_SETTINGS (mediaservice 57e7f93); no other chat setting is exposed. collabSetupExposure pins the new doors and that none depends on the Chat app.
· MCPGatewayService
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-internal
Rehearse — the personality toolbar runs an SI member through four made-up situations with its saved settings and shows what it would write
The toolbar offers Rehearse on an SI member's own charter and on a layer once an SI holds it (else disabled, saying so); the dialog picks the SI, checks the right to supervise it, starts the PERSONALITY_BASIC suite, reads it every 5 s until it finishes or stops, and shows one card per scenario with its reply; the SI room's rehearsal card reads a suite as 'Personality scenarios · 4 items' and its items by scenario title. @kamo/kamoai-core 0.1.1. (KamoCollab CP09 Task 21)
· MediaService
Security's MANAGE_ACCESS_RULES also administers the communication policy
The owner placed the communication policy "also under Security" so an organization without the Chat app can configure it. MANAGE_CHAT_SETTINGS is a Chat-app right that cannot be granted while the app is off, so PolicyAdminRights accepts MANAGE_ACCESS_RULES as well, on the policy endpoints only (ChatPolicyController: policy, versions, simulate, preview, telemetry, the admin contact-request list) and the administrator's read of one contact request. The original **************** path is unchanged; OVERRIDE_CHAT_POLICY is still not accepted.
· MCPGatewayService
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-internal
Make the shipped KamoCollab screens reachable
- Home administrator bar: Disclosure Log and Disclosure beside Access Blocks and System Access Logs (master R1-37; gated by the bar's own rights, which include MANAGE_ACCESS_RULES). - Settings landing: a Communication Policy card under Chat (the CP04 policy tab had a menu entry but no card). - Interaction Center, Chats tab: links to /contact-requests (with the count waiting for a decision) and /supervised-chats. Both CP04 pages shipped with no way in; each link shows only when its list holds something. - collabSetupExposure pins the three doors, like essentialSetupExposure.
· kamo-internal
Every charter host keeps the previewed text after its save — the member card, the role, department, job-title and team dialogs and the persona studio call publishApprovedProse once their save landed, and only then: under the id the save answered, from the key the editor recorded the preview under (LEVEL:new before a create); a refused save keeps nothing and leaves the text for the retry; a text that could not be kept is a warning toast (notice.proseNotKept), settings that moved are not (KamoColl...
· kamo-internal
Personality and Docstion in the charter editor — both sections are offered at every level (editor: true), CharterEditor renders PersonalityPanel and DocstionPanel for them with one search and "only changed" shared across the two and a jump between them, and opens on initialSection; every edit hands back the whole list with only the edited identity changed (CP-D14), so items of keys, kinds and sections this page does not know and hide markers survive; the template gallery names a templa...
· MCPGatewayService
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-internal
The metric mirror, the goal and watch editors, and REPORT links — metrics.ts mirrors shared-lib MetricRegistry (19 metrics, families, units, direction, measured, report; metricsParity.test.ts reads the Java), sections' METRICS is its keys; the GOAL metric select groups its own work and the business, marks what Kamo does not measure and shows % beside a percent target; the watch card offers the 15 measured metrics, keeps a saved unmeasured one with a warning chip; client WATCH validation checks t...
· MCPGatewayService
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-internal
The preview side panel and saving is the approval — PersonalityPreviewDrawer asks CP06's preview when it opens and on request (Write it again once the text is out of date, Try a different wording), never on a slider move, and shows the text with its source, a fallback's reason, its word count, what it is written from and the tendencies readout; Edit the text checks a person's own text and lists each problem with what tripped it; ApprovalNotice names the SI members a save reaches (five, then and ...
· MCPGatewayService
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-internal
The Docstion panel — DocstionPanel (the section title, the shared toolbar state and one card per kind): Working mode as four radio cards, Starting contact and Delegating work per relationship (Everyone and nine) with the levels a level above rules out disabled and named, Escalation conditions with their bound in the trigger's unit, the text a custom one needs and the target through EscalationTargetPicker (extracted from SectionFields), Attention and Digest free below what is inherited,...
· kamo-internal
Relationship and channel adaptations — the Adaptations card after Tendencies: own adaptations (setting, for, on, value, where it comes from, Remove) and those that apply from above (read-only, with their source and Override here, which writes the own item at the inherited value); Add an adaptation offers only the adaptable keys (every dimension, Reasoning, Message structure, Register; Communication threshold and Conflict style per relationship only, with no channel), refuses an identity already ...
· MCPGatewayService
The basis argument — an SI of an ENFORCE org sees the optional basis (up to 20 sourceRefs, KIND:id) on every disclosing tool, static or dynamic; the pipeline takes an SI's basis out of a disclosing tool's arguments in every mode before the schema check, the planner and the args hash, checks it as its schema would (a malformed item is INVALID_ARGUMENTS) and keeps its refs for the disclosure gate; an AUDIT org's list is byte-identical; DISCLOSURE_DENIED (error, DENIED) and BASIS_NOT_READ (error, I...
· kamo-internal
Ordered groups per relationship — Preferred channels, Contact etiquette and Decision priorities cards after Social style, each with For (Everyone or one of nine relationships, marked set here and inherited); ChannelOrderEditor reorders by keyboard drag (dnd-kit KeyboardSensor) and up and down buttons, writing all five positions; EtiquetteTable edits urgency bands with two-thumb ranges, flags overlaps and shows the completed 0–10 result; DecisionPriorityEditor's two priorities must differ; Reset ...
· kamo-internal
The information's owner answers what someone asked an SI — a release proposal opens its approver's form ('<requester> asked <SI>:' and the question, their records as chips, Title and What may be shared); Share this summary records a SUMMARY from those records, checks sharing it with exactly the requester and the SI, answers a warning through the disclosure notice (Send anyway with the acknowledgement) and stops at a block, releases it, then approves with the summary as derivedNoteId; a failed st...
· kamo-internal
The SI memory review's actions — Correct (topic, what it remembers up to its kind's limit, the day it forgets it or Never; only what changed is sent), Narrow… (the current level and those above; on a shared labelled note only the SI, or for an organization-wide note a team, a department or people, for a department's note another department; a card never takes an audience), Delete asked first, restricted rows included, and Share as a summary…, which opens CP05's summary dialog prefilled with the ...
· MCPGatewayService
An SI's task writes, lead notes, master-note entries and workstation typing write their disclosure plans — a task reaches its participants after the call as its TASK label names them (creator, list owner, assignee, and the supervisor of an SI owner or assignee; an update and a comment read the label, a create and an assignment name who they leave, the assignment carrying the task without its old assignee), a lead note the organization through the lead label's required rights, who-i-am the public...
· kamo-internal
The Memory card in the SI room — the supervisor reads an SI's memory cards (by kind, counted) or its labelled notes, searches topics, pages with Load more; each row shows its topic, two lines with Show more, a chip per label field, About and Learned from (a source the reader is not cleared for as a placeholder), who changed it last, and the actions its flags allow; a restricted row is a lock, a date and Delete only (KamoCollab CP11 T23)
· KBService
The supervisor memory review actions — PUT **************** (EDIT_NOTES) corrects a live card's topic, fact and expiry (null clears it): a version of the old words kept, last edited by the reader, the card re-keyed (409 TOPIC_TAKEN on another live card's topic; an expired card holding it is purged), links, label and kind untouched; POST …/{noteId}/relabel (EDIT_NOTES) narrows a note's label: the sensitivity only rises (400 LABEL_WIDENS), never above the reader's effe...
· MCPGatewayService
An SI's sends write their disclosure plans — chat lines and mentions reach the conversation's members (a support conversation's visitor too), mail the members its addresses reach and every other address (a shared mailbox included) aliased by the lead it is about, a reply or forward carrying the original's thread, a text or call the number aliased by its lead or contact (a colleague call the colleague), an invitation the invited colleagues, a join the meeting's participants and guests with an emp...
· kamo-internal
Linked tendencies — the Tendencies card after Strengths (each tendency its own slider, the linked switch, what it is linked to, a live meter, the disagreement with Use {derived}, Move the linked settings and Make independent), TendencyReadout's seven meters and the strengths held; moving a linked tendency writes only its item plus this level's own linked settings, a linked setting moved here takes this level's own linked tendency with it, and the linked rows show the predicted values, Moved by, ...
· KBService
The supervisor memory review and its content gate — GET **************** for a person who supervises the SI (SupervisorGate: VIEW_NOTES, 403 HUMAN_ONLY for an SI session by its own intelligenceType or member row, SUPERVISE_AI_MEMBERS, 404 for anyone but a supervisee), at most 25 rows newest first: CARDS on the SI's live cards (kind, q in the topic key, cardCount), LABELLED on ix_notes_member_updated (its notes but cards and its maste...
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