> **v0.1.46 development documentation:** Procedures are reviewed against packaged source; live production operation and updater migration remain unverified. Do not treat this draft as deployment approval. # KIP Interfaces — User Guide v0.1.46 ## About this guide This guide is for people using KIP Interfaces for the first time. KIP Interfaces is a website-management application. It lists managed websites, provides links to their operations, and—when permitted—supports deployment, source comparison, and GitHub-related workflows. You do not need to understand GitHub to view the managed websites. ## 1. Open KIP Interfaces Visit your organization's KIP Interfaces URL. The Home page has tabs for **Managed Websites** and **Documentation**. Select **Managed Websites** to see the websites available to you. Select **Documentation** to open this guide, technical specifications, and administrator instructions. ## 2. View a managed website Find the website in the Managed Websites list. Select **View** to open its operations page. The listed System Version and Data Package indicate the versions reported for that website. These are not necessarily the same as the version of KIP Interfaces itself. ## 3. Sign in when needed Public viewing may be available without signing in. Changing a managed website requires an authorized account. Use **Log in**, enter your assigned credentials, and return to the intended page. If an operation is unavailable, ask an administrator to confirm your role rather than trying to bypass access controls. ## 4. Understand the roles **Visitors** can view public pages. **Normal Users** may be permitted to deploy to managed websites. **Administrators** manage client registrations, credentials, repository enrollment, and rollback. Actual permissions are enforced by the application and the individual client configuration. ## 5. Understand website operations The operations page may provide version information, an update action, and links to source or GitHub tools. Do not upload a release ZIP unless it is the intended package for that website. Deployment and self-update are different: **Self Update** upgrades KIP Interfaces itself; website deployment updates a managed client website. ## 6. Check GitHub status A GitHub status of **Authorized** means the assigned credential has access to the configured repository. **Synchronized** means the deployed files were verified against the configured repository state. **Not synchronized** does not mean authorization failed. **Not configured** means the client has not been fully configured for this check. Ask an administrator to investigate unexpected status changes. ## 7. Read documentation Open the **Documentation** tab. Choose **Read HTML** for a browser-friendly page, **Download DOCX** for a formatted document, or **Source Markdown** for the editable source. The Administrator Guide explains setup and access management; the Installation and Updater Guide explains software updates and recovery limitations. ## 8. Common problems ### I cannot see an action You may not be signed in or may lack the required role. Contact an administrator. ### GitHub says “Not synchronized” This is a file-comparison result, not necessarily a credentials problem. Ask an administrator to run Verify and review repository, branch, and source directory settings. ### An update is rejected Do not repeatedly retry with modified ZIP files. Preserve the error message and installed version, then contact the administrator. The release package may be invalid or incompatible with the installed updater. ### Where do I find more technical details? See the Administrator Guide, Functional Specification, and Integration/API Specification from the Documentation tab. ## 9. Safety and support Before performing a deployment, confirm the target website and release version. Administrators should retain a verified recovery package and backup of persistent data. Do not interpret a successful package integrity check as proof that live deployment and rollback have been tested. ## Practical task: find and read documentation 1. Open the home page and select **Documentation**. 2. Find the topic you need and select **Read HTML** to read it in the browser. 3. Use the clearly labeled **Back to Documents** link at the top or bottom to return to the document index. 4. For a portable copy, select **Download DOCX**. For the editable text source, select **Source Markdown** where available. ## Practical task: investigate a GitHub status 1. Open **Managed Websites**, choose the site and select **View**. 2. Find the GitHub status. **Authorized** means access is permitted; **Synchronized** means a separate source/deployment match has been established. 3. If the status is **Not configured**, contact an administrator to review credential, repository enrollment and client assignment. 4. If the status is **Not synchronized**, report the displayed branch, repository and site name; do not assume the credential is invalid. For administrators configuring access, see [Administrator Guide](Administrator-Guide.html). For API clients, see [AI API Reference](AI-API-Reference.html). ## Historical release notes and development appendices Earlier checkpoint descriptions are retained in the versioned `Release-Notes-v0.1.41.md` through `Release-Notes-v0.1.44.md` and historical continuity records. They do not describe current v0.1.46 behavior.