No frontend secrets
SMTP credentials and future provider credentials belong on the server or in secure local storage, not in browser code.
Privacy-conscious by design.
TraceLayer is built around local-first operation, scoped access, explicit review, and conservative handling of private or sensitive content.
Minimal form metadata
Contact and early-access forms store only practical metadata for follow-up. Full contact messages are not written to public logs.
Conservative publishing
Private, protected, working copy, noindex, and sensitive content should not be indexed or syndicated automatically.
Public/private boundaries
TraceLayer separates public discovery surfaces from private operational surfaces. Marketing pages, documentation, route descriptions, and public-safe reports can be indexed; admin workspaces, credentials, working copies, private previews, and sensitive operational material stay outside public discovery.
Local-first posture
The product direction favors local computation, cached reports, explicit review, and generated knowledge over repeatedly sending private context elsewhere. Visibility reports are designed to summarize readiness without exposing private paths, secrets, customer content, or server-only configuration.
Review before automation
Automation should make decisions observable before it makes them irreversible. TraceLayer uses confirmation gates, diagnostics, health states, and recovery notes so publishing workflows can be inspected before a live deployment, redirect, email, or indexed update is allowed to proceed.