Getting started

Create a workspace, connect a source, run your first review, and explore the resulting architectural truth.

Veriom turns technical evidence into a reviewable architecture model. A first review follows five short steps.

Your first evidence-backed reviewFive explicit steps take a selected source from connection to a reviewable result.VERIOM FIELD GUIDEEVIDENCE FIRSTYour first evidence-backed reviewFive explicit steps take a selected source from connection to a reviewable result.TB1TB2CONNECTUNDERSTANDDECIDEconfirm01Connect sourceExplicit scope02Run auditExact revision03Inspect truthEvidence + gaps04Ask workspaceCited answers05Share or actApproval requiredNo source is reviewed until its workspace scope is explicit.
Your first evidence-backed review

1. Create your workspace

Accept your invitation, verify your email, and create a workspace for the team that owns the system being reviewed. Verification links are single-use and expire after 24 hours; request a replacement from the sign-in or verification page if needed. Workspace roles control who can connect sources, run reviews, approve reports, and publish remediation.

2. Connect evidence

Choose the connection that fits your workflow:

3. Start a review

Choose a connected source and start an audit. Veriom admits work to the workspace queue, reports its position, and streams each deterministic and agent-assisted stage as it completes.

4. Inspect the result

Open the architecture view to explore:

  • services, data stores, interfaces, pipelines, identities, and boundaries;
  • relationships with selectable evidence and confidence;
  • contradictions and coverage gaps;
  • findings connected to their architectural context;
  • the specialist-agent artifacts that shaped the review.

5. Ask the workspace

Open Workspace Intelligence to ask a question about the latest reconciled truth. Choose one or more repositories when the question is source-specific, follow the visible verification states, and open citations in the Context inspector to confirm why Veriom believes each factual claim.

Recommendations derived from existing audit artifacts can be acknowledged, assigned, snoozed, discussed, dismissed with a reason, or prepared for remediation. See Workspace Intelligence for grounding, limits, and cost behavior.

6. Share or act

Review the canonical report, approve it, and export JSON, Markdown, DOCX, or PDF. When remediation is appropriate, an Analyst can approve a proposed change and publish a pull request. Veriom never merges automatically.

Prefer the API?

Use the API guide for authentication, idempotency, event streams, errors, and the generated endpoint reference.