What this mockup shows, and what it does not
Both coats carry the same architecture: the three rings of the library (estate-wide core, brand and tier, property-local), the same document types, the same reference numbering, the same three named seats per property, and the same assistant answering only from the approved corpus. That is deliberate. The taxonomy is the invariant; the platform is a choice of coat, and this page lets the room try both coats on. Sample content only: the standards shown are illustrative, not issued documents, and no live system sits behind this page.
The two routes, plainly
Google. Google Sites over shared drives inside Aleph’s own Workspace. Fastest and cheapest to stand up, the same sign-in everyone already has, and nothing to host. Search, permissions and approval flows are what Sites allows, which is where the earlier attempt stalled; the design answers those three differently (the assistant is the search, the seats and rings are the access model, the change process is the approval flow).
Custom build on Laravel. A web application written for Aleph, on its own address, hosted where Aleph chooses, signed into with the same Google accounts. Laravel is the framework GO-Globe proposed for it: an established open-source toolkit for web applications (current release 13, March 2026, supported to 2028) with sign-in by Google account, document storage, search, an approval workflow and English-French switching as standard parts, and its own tools for the assistant layer. The library, the rings, the approval flow and the assistant are built exactly as designed rather than fitted to what a site builder permits. The trade is plain: everything is possible, and everything must be built, hosted and maintained by someone, so it costs more and takes longer than the Google route. The coat shown here follows the screens GO-Globe already designed for Aleph.
Microsoft SharePoint is no longer shown. Aleph runs on Google and Neil confirmed the preference to stay there; the earlier mockup’s SharePoint coat is kept in the archive.
