Trust and contact are product work, not footer work

# Trust and contact are product work, not footer work

In many software products, contact pages are an afterthought.

That is the wrong posture for infrastructure that can affect coverage,
settlement, claims handling, or compliance.

## Trust is part of the contract

When a public surface talks about APIs, automation, or support, people are also
implicitly asking:

- who is operating this
- where do legal issues go
- where do security reports go
- what happens when automation is not enough

Those are not secondary concerns. They are part of the product surface.

## Why clear routes matter

If every issue goes through a generic contact form, the product looks immature.

The better pattern is explicit routing:

- legal issues go to legal
- security and trust issues go to trust
- product and integration questions go through the normal support path

That creates clearer expectations for operators and clearer signals for people
trying to evaluate whether the system is serious.

## The operational side

The same rule applies to support escalation.

AI assistance is useful, but it should not erase the human route. When the
issue becomes high-risk, ambiguous, or consequential, the handoff path needs to
be visible and auditable.

That is why Parametrig treats trust, contact, and escalation as part of the
surface design rather than as loose administrative details.