SHANNON (“the Company”) announces that it has added two read-only tools for referencing revision history to the AI integration (Model Context Protocol / MCP) of its own product, “Kitei Log.” From MCP-compatible AI clients such as claude.ai, users can now trace when, in which version, and how a policy changed, and retrieve the exact text of a specific past version.
Background
Since May 2026, Kitei Log has provided a configuration that lets AI clients reference the latest version of policy and manual text, and has also supported referencing revision history. In ISMS / PrivacyMark audits and labor due diligence, however, it is essential to confirm the provenance and authenticity of a given provision—“from which past version, and starting when, has this provision been in effect?” and “has the text from that time been left unaltered?” This time, we have carved out read-only tools dedicated to this purpose, so that revision history can be traced even from integrations that do not hold write permission.
The Two Tools Added
- Retrieving the list of revisions: Returns the published revisions of each policy in reverse chronological order. For each version, you can confirm the version number, status, change summary, effective date, publication timestamp, and body hash (body_hash). It responds directly to instructions such as “List the revisions to the telework allowance in the work rules, newest first.”
- Retrieving the text of a past version: Specify a version number to extract the full text of the policy as it stood at that point in time. Because the body hash is returned along with the text, you can mechanically verify whether it matches the authoritative original from that time (i.e., whether it has been altered). Long text is safely truncated, and the response makes clear whether truncation occurred.
References Published Versions Only
What these tools return is limited to published and archived versions. Drafts still being written or versions under review are never visible from the AI integration. Because only finalized, disseminated official versions are subject to reference as provenance, there is no risk of unconfirmed deliberations flowing into an external AI session.
Permissions and Tenant Scope
Both tools are read-only and do not create, revise, or publish policies. Access is restricted by a common guard to the scope of the tenant (account) granted to the integration token, and policies or versions of tenants outside that scope are never returned. As before, a record of who referenced which version of which policy via AI is kept in the per-tenant audit log.
About Kitei Log
A SaaS that centralizes the creation, revision, dissemination, and access records of internal policies, manuals, and labor-management agreements. It offers over 100 templates, .docx / .pdf import, automatic logging of access records, and export of audit-ready CSV files and watermarked PDFs. For details, please visit the official site.
Inquiries Regarding This Announcement
SHANNON
- Email: [email protected]
- Contact form: /contact/