portalr 0.1.1

portalr is the portal into an application built on lattice: an app UI for the people who use it, to chat with its agents and see their artifacts, proposals, rules and runs, and an admin UI for those who run it, to manage access and see feedback, evaluations, usage and spend. Both are static single-page apps in React, sharing a typed client and a ui kit, and served by a router the application mounts beside the libraries'.

Status: built, and on PyPI. The router, the app's areas and the admin UI, including the operators' tenants and tools and people shown by email, are built and tested, and stackr's template mounts it (guides, architecture). Not built yet: magic links and other sign-in providers. Its wheel carries both UIs: uv add portalr.

Why

Every surface in lattice is an API, a WebSocket or an MCP server, so an application built on it has to build its own UI before anyone can use it, and running one is blind without an admin UI. lattice RFC-0002 designs that UI once, and portalr is where it is built.

What it does

• The browser calls each package's own routes. A chat goes to artifactr's WebSocket, a rule to reflexr's REST, a grant to grantr's API, on one origin with one token. Nothing proxies them, so nothing re-declares their types (ADR-0001).
• Two static apps on Vite, in React 19 and TanStack, with no server rendering and no Node server (ADR-0002).
• A chat of its own, thin, in ui, over artifactr's protocol (ADR-0003).
• A tenant's own observability, native, in the admin UI: its feedback, evaluations, spend, traces and logs, with deep links out to the tools for operators (ADR-0004, ADR-0005).
• Every read filtered by tenant, in one module, over the stack's shared stores (ADR-0006).
• Permissions asked, never guessed. The UIs ask grantr what the user may do, and the server checks each command again.

Documentation

portalr's documentation is its section of lattice's site, at https://lattice.alexnodeland.com/portalr/, built from docs/portalr/.

• Getting started: install the wheel, mount the router, sign in.
• Guides: the app, the admin UI, an operator's runbook, and what portalr keeps from view.
• Architecture decision records: why each part is the way it is.
• RFCs: the v0.1 plan, its phases and what each waits on.
• lattice RFC-0002: the design portalr builds.
• Brand: the marks and their colours.

Contributing

See CONTRIBUTING.md for setup, the trunk-based workflow, and the RFC and ADR process.

License

MIT. The UIs carry lattice's typefaces, Schibsted Grotesk and Fragment Mono, under the SIL Open Font License 1.1.