User interfaces
The React application contains office, customer, worker, subcontractor and platform-administration surfaces. Each surface presents the records and actions relevant to its users. Authorization is enforced separately. Shared components and design tokens provide consistent presentation, while loading, editing and conflict states explain the outcome of user actions.
Office workspaces
Section titled “Office workspaces”Office users work with customers, opportunities, quotes, projects, planning, costs and reports according to company permissions. A project provides shared context across these workspaces. Navigation provides entry points; direct links and API requests still require the same resource checks. Reports additionally apply the permissions of their source datasets.
Office workspaces gives the detailed contract, examples and evidence limits.
Customer, worker and subcontractor surfaces
Section titled “Customer, worker and subcontractor surfaces”The customer surface presents authorized and published project information. Worker surfaces focus on assigned work and the worker’s own execution context. Subcontractor workspaces expose scoped commitments, responses and submissions. These are different audiences. Assignments and conversation audiences remain explicit even when components or records are shared.
Portal surfaces and audiences gives the detailed contract, examples and evidence limits.
Editing and conflict states
Section titled “Editing and conflict states”Saving can involve a direct database mutation or a privileged transaction. Domain contracts determine revision checks and retry behaviour. For example, purchase-cost conflicts retain the office draft and require a fresh read. The interface must distinguish unsaved work from an accepted save. Mutation handling connects these states to the returned result.
Editing, save status and conflicts gives the detailed contract, examples and evidence limits.
Responsive layout and accessibility
Section titled “Responsive layout and accessibility”The frontend uses project-specific semantic tokens for surfaces, text, borders and interaction states. The visual catalogue exercises synthetic states in mobile and desktop viewports and both themes. These checks complement authenticated workflow testing. Test execution defines their scope; a rendered component does not establish complete accessibility or business correctness.
Presentation across devices and themes gives the detailed contract, examples and evidence limits.