Loft 1.0.0 and 1.0.1: Multi-tenant Loft
Loft now supports separate customer workspaces with tenant-specific access controls, operator administration, and retrieval scoped to each workspace.
Loft now supports multiple customer workspaces in one deployment. Each workspace has its own access boundary, while a person can sign in once and enter the workspaces available to them.
Workspace administration
A separate operator console gives authorized administrators one place to create and manage workspaces and maintain the operator roster. Sensitive changes require additional authentication, and operator activity is recorded for later review.
Loft can also deliver invitation and activation messages. Deployments that do not use email still return the required links to the person who issued them.
Retrieval within each workspace
Retrieval is scoped to the workspace. Loft prepares each active workspace independently, without requiring a separate indexing account. If retrieval is unavailable, authoring remains available and Loft reports the retrieval problem instead of hiding it.
Evidence moves to Berth
Version 1.0.1 removes the former evidence functionality from Loft because evidence belongs to Berth in the Software Plant architecture. Loft is responsible for product intent, specification, and the decisions around it. Berth is the future pillar concerned with software delivery evidence.
Berth is not yet an available product. Removing the evidence functionality from Loft clarifies the boundary between the two rather than presenting Berth as a shipped capability.
Reconciliation remains part of Loft. Its results can inform review, but they do not prove conformance or make acceptance decisions for the people responsible for the product.