AvailabilityKnow what you can use.
Know what you can use.
Know what each status means.
This page describes the website’s delivery and interaction boundaries. It is not live infrastructure telemetry.
| Area | Availability model | What you can do |
|---|---|---|
| Company & architecture | Website pages | Read company, platform, component and foundry explanations. |
| Exploration controls | Browser interaction | Choose a goal, inspect component responsibilities and filter the foundry directory. No external action is executed. |
| Enquiry preparation | Local draft | Prepare and copy a draft. Sending uses your email app and remains your action. |
| Technology workbench | Separate application | Explore the retained technology workbench. Host and connected-service operations have separate access and availability. |
| ClaimPath workspace | Separate application | Open the existing claim workspace. Paid operations depend on its configured billing and verification service. |
| CasePath preparation | Public application surface | Open the public preparation interface. External filing, professional advice and service completion are separate capabilities. |
| Estate monitoring | No live feed | No uptime, host health or live operational status is asserted here. |
Access remains deliberate.
Website visibility follows the Site’s current sharing configuration. Application authority and owner-only operations retain their separate access controls.
The hosting access gate is separate from application permissions. An accessible page does not grant authority to private runtime tools.
Start with what needs to work better.
Bring a process, an idea or a systems question. We’ll help define the next useful step.