Begin with the method or a real service question
Architecture Portal develops the architecture method, logical system blueprint and practical assets. Its first loop model and catalogue are available on this site. Both are in development and have not been independently tested; the next test is to apply them to a delivery slice and record where they help or fail.
Public Purpose Lab supplies the applied public-purpose context. It may assemble selected components in synthetic demonstrations and return test results, operational observations and limitations to Architecture Portal. Its governance foundation and public site exist; it has not yet published a complete integrated demonstrator.
Open BPM is the reactivated programme for open reference work, case and workflow-management components, public interfaces and participant views. Historical design material provides lineage. The new component, application programming interface (API) and interface are proposed rather than implemented.
Develop business languages without rebuilding every tool
DomainLang develops methods and reusable tools for creating small languages that express business rules, work and information. Its method and combined toolchain are in development.
CoreLang is DomainLang’s principal worked business-language example and is proposed as a common syntax and toolchain base for suitable business-related languages. The new language, parser and common base have not yet been built. Languages that do not fit that base remain free to take another path.
Reuse the working language, execution and editor spine
cREXX and CREXX contain the working cREXX compiler and the RXAS, RXLINK and virtual-machine execution stack, with libraries and packaging tools. In this portfolio, cREXX is the preferred surface for rules whose source, inputs, version and result people can review, and for transformations and scripting. It is not the required language for every component.
DSLSH is working middleware for keeping an editor and parser synchronised and returning structured language information. It is one part of a toolchain, not a complete language workbench.
THE CREXX Edition is a modernised editor fork and a working reference integration for CREXX and DSLSH. It also has parser-backed source rendering and an opt-in Preact and TypeScript browser interface. The browser interface is a working proof of concept with documented session, protocol and user-interface limits, not a production multi-user web editor.
RXAS, RXLINK and the CREXX virtual machines are the preferred first execution path for suitable CoreLang and DomainLang examples. That connection remains proposed and would not make either source language adopt REXX syntax or behaviour. The LLVM compiler infrastructure is later backend research.
Keep source-grounded retrieval separate from desktop orchestration
crexx-rag is the in-development reference for knowledge, retrieval and source grounding. It retains a native executable reference and has accepted cREXX slices plus a schema-v2 storage foundation. The target cREXX product is incomplete and has not replaced the native reference.
Cognitive Pipelines is a working experimental Qt desktop graph application for composing and running AI, retrieval, script, external-tool and human-input steps. It does not own durable human work and is not a distributed scheduler or production multi-user platform.
No integration among these two projects, Open BPM and Public Purpose Lab currently exists. The blueprint explains their distinct logical roles before proposing how they might exchange requests and results.
Let implementations change the shared architecture
The projects do not form a one-way stack. DomainLang can expose language needs to CoreLang and the editor tools. A future Public Purpose Lab demonstration can expose missing component contracts. Implementation, tests, operation and support can then return a specific lesson to Architecture Portal’s method, blueprint or assets.
That learning path is the programme. Earlier Architecture Portal, Open BPM, CoreLang, DomainLang and interoperability work shows continuity, while old middleware choices and general-purpose language drafts remain historical material rather than current recommendations.