Alpha release and verified journeys¶
Version 26.10.0-alpha.1 is published for evaluation. It includes the native pyfly 26.10.18 runtime, organization directory, management interface, typed SDKs and embedding packages. Production acceptance and full migration parity remain incomplete.
Download the release. All 11 package downloads were retrieved after publication and matched both the published SHA256SUMS and GitHub asset digests. The annotated tag resolves to merge commit bb5ac7a9854488db348d678c9b42de6771e9b7f1; its source tree equals the tested delivery revision d28d14f1780d0bad69161b4fafb68fcaff34a2f1. Delivery pull request.
Known startup issue¶
A real canonical document upload against the preserved PostgreSQL clone returned HTTP 500 because the pgvector store had not been initialized before its first business transaction. The failed attempt retained its source admission and original file; no chat run was submitted. A native lifecycle correction is being qualified for the next delivery. Preserve failed intake records and check their status before submitting another upload; do not assume that an error response means no data was saved.
Choose a starting point¶
| What you need | Guide |
|---|---|
| Configure an installation and knowledge services | Guided configuration |
| Learn the interface with screenshots | Visual walkthrough |
| Configure files, object stores or an external content system | Storage and ECM |
| Upload, maintain and query knowledge without Angular | Headless SDKs |
| Add knowledge controls to another product | Embedding |
| Connect an external assistant | Claude and ChatGPT |
The runtime requires Python 3.13. The standalone Python SDK supports Python 3.12 or later; CI covers 3.12, 3.13 and 3.14. TypeScript CI covers Node 22 and 24. Java requires 21 or later, with CI on 21 and 25. SDKs expose 188 canonical operations and 331 wire schemas, including knowledge creation and management subject to the caller's permissions and token scopes.
What the journey checks establish¶
The released interface passed 488 unit tests and 266 controlled Chromium journeys. The browser suite uses the production builds, authorized example service responses, custom elements and an external Angular host installed from the actual package. These are interface and integration-contract checks, not a deployed model or identity-provider acceptance test.
| Journey | Verified behavior | Acceptance still needed |
|---|---|---|
| Personal profile and organization | Photo review, preferences, positions, hierarchy, directory visibility, filters and pagination work across desktop and mobile. Changing workspace retains personal preferences while token responses stay bound to their original access context. | Final deployment and external corporate-directory synchronization. |
| Library and files | Folder navigation, destination review, multi-file selection, filtering, server pages, upload failure recovery and version details are covered. | Fresh canonical intake through the final deployed processing services; general durable bulk jobs. |
| Chat and evidence | Grouped conversation history, attachments, streaming presentation, OpenUI, answer audit, source selection and SQL provenance have controlled browser coverage. | Fresh intake-to-chat/model acceptance and replay after replacing the actual source. |
| Roles, tokens and applications | Source and browser regressions cover current permissions, scoped tokens, one-time secrets, revocation and application review. A signed native request can read its own organization profile while an unauthorized other-person request remains forbidden. | Real external client linking and final provider configuration. |
| Headless knowledge management | Python, TypeScript and Java contract suites pass 149, 43 and 1,120 tests. Installed Python/npm consumers and Java 21 examples are checked. | Configured-service acceptance across the final deployment and package-registry publication. |
| Embedded experience | A clean external Angular host loads the installed package; custom elements use the host client, emit selection events and preserve host styles. Font bytes and narrow layouts are checked. | Acceptance inside each consuming product. |
| Retained-data upgrade | The owned PostgreSQL clone passed native directory revision 22 with document and structured histories at 20 and 17. Existing rows, ACLs, roles and object inventories were preserved. | Rollout to the retained management services. |
The current backend source suite passes 1,466 tests with 39 explicit infrastructure or opt-in skips. Deployment checks pass 22 tests with one nginx skip. Domain suites and their infrastructure boundaries are retained in the detailed qualification history.
The clean installed-runtime baseline passed 3,912 runtime tests and 19 deployment checks before the final self-profile dispatch correction. The rebuilt release wheel passed that new signed native request regression from a separate installed environment, without importing application source. Its namespace bytes matched the wheel before and after the check. Do not treat the earlier full installed suite as a second full run of the rebuilt wheel.
What was published¶
The downloads contain five Python wheels for the backend, documents, structured knowledge, storage and Python SDK; the TypeScript SDK and Angular npm archives; the Java SDK JAR; compiled web assets; the branded desktop MCP bundle; and a skills archive. Licenses and Foundation notices were checked inside the distributions. The Java artifact uses Java 21 bytecode. The 14 complete Java guide examples compile against the distributed JAR.
These are GitHub release downloads. Publication to PyPI, npm and Maven Central remains separate. The desktop package and connection guides do not establish acceptance by the actual Claude or ChatGPT clients.
The documentation site is published on GitHub Pages. Six live desktop/mobile views of storage, the Java SDK and guided setup were checked for successful loading, local Manrope, the family logo, Foundation copyright and horizontal overflow.
Before a production rollout¶
Complete the fresh deployed RAG/SSE/model/source-replacement journey, retained-service rollout, full capability parity, curated-knowledge RLM and durable bulk work. Qualify the configured cloud stores, corporate identity providers and external assistant clients with their real permissions. The corporate profile synchronization expansion is a subsequent delivery and is not included in this alpha.
Do not archive an existing repository or replace retained data on the strength of these interface checks. Follow the migration and recovery guide and the production guide when planning that acceptance.