Trust boundaries before trust claims

What the planned boundary must preserve

• Tenant data and execution state remain separated by explicit tenant scope.
• Provider credentials remain separate from public artifacts and are intended to use least-privilege access.
• Public explanations remain separate from private contracts, operational evidence, and tenant records.
• The public website collects only the business-contact fields needed to evaluate a design-partner conversation.

Planned encryption and access controls will be stated as implemented only after their actual boundaries have been verified. Supervised automation must deny work that lacks legal, feasible, or authorized scope rather than silently weakening a contract.

PillarMesh claims no certifications and no production SLA. The product is in development; public availability and operational assurances will be stated only when they are current and independently supportable.

Read the responsible disclosure guidance, privacy notice, and accessibility statement for the current public-site policy context.