solodot

Trust

Solodot prepares founder work. It does not quietly act on it.

The roadmap adds memory and approval records as trust controls, not as a license for silent automation. The founder remains the steering point.

Data handling

Use sanitized context and keep the approval boundary visible.

The intake works best when the founder gives enough context to reason about the painpoint without pasting secrets or unnecessary customer records.

What to paste

Use sanitized business context: the offer, stage, blocker, recent attempt, and this week's constraint. Replace customer names, private contract terms, secrets, credentials, regulated data, and raw customer records with plain descriptions.

What Solodot stores

When persistence is configured, Solodot stores the routing result, compact context brief, recommended actions, approval decision, copy/export artifact, and founder-control signals. If storage is not configured, the result remains local to the browser session.

What providers process

The intake prompt is processed by the selected AI provider. Provider keys stay server-side. Do not paste information you are not comfortable sending to the selected provider.

What Solodot does not do

Solodot does not send email, update a CRM, create reminders, automate invoices, publish copy, or automate compliance in this roadmap slice. It prepares a preview and waits for founder approval.

Founder controls

  • Approve, revise, or reject every proposed action before use.
  • Copy approved drafts or export queue actions manually.
  • Export a run history as JSON for founder audit.
  • Delete a stored run with the browser-held owner token.
  • Treat verification as future-only until approved execution exists.

Unsupported claims

  • SOC 2, HIPAA, GDPR, or enterprise compliance claims.
  • Security posture, uptime, support coverage, continuity, or legal guarantees not confirmed by the founder.
  • Claims that prompts are never processed by third-party providers when a provider-backed intake is selected.
  • Claims that agents act silently, autonomously, or outside founder approval.

Solodot trust packet

The trust material is dogfooded on Solodot first.

The same Trust Packet workflow should mark what is known, what is unsupported, and what needs founder confirmation before any buyer-facing claim is used.

Current proof

Solodot can show its product boundary, routing schema, approval gate, export/delete controls when persistence is configured, and source-backed research notes.

Proof gaps

Solodot does not yet claim formal compliance, enterprise security review, production uptime history, or validated paid cohort metrics.

Next validation

Track whether trust language increases completed intakes and whether cautious founders still approve or copy the first agent action.