SomabaseOpen workspace →From a requirement to collected evidence
Database-encryption evidence for Northstar production. This static example shows a scoped artifact summary, not a collected customer file.
What qualifies
A configuration export identifying the resource and environment, whether encryption at rest is enabled, and when it was collected. Confirm the source and scope before authorizing upload.
How the local agent would collect it
Use an authorized read-only configuration query. Do not inspect database rows. Authentication happens in the collector’s environment, not through this page.
What must stay out
Database contents, customer records, credentials, connection strings, and unrelated resources.
Fictional artifact summary: production-encryption.json
Resource: northstar-production. Environment: Production. Encryption at rest: Enabled. Collected: 12 September 2026, 09:12 UTC. These are illustrative fields, not a hosted original export.
What the person approves
Inspect the minimized artifact, source, scope, date, and exclusions before authorizing upload in the local MCP client. The ledger records collected evidence; control conclusions remain separate.
What is real in this example
Only the published text and navigation. No source was queried, no model was called, and no evidence was uploaded.
Evaluate one bounded workflow.
Start with fictional data and a clear definition of what must not be shared.