veriomExplore the platform
Start with the architecture, inspect the evidence, explain the intent, and follow differences over time.
Start with the interactive demo. It opens a fictional Northstar architecture with its trust boundary and source evidence. Inspect a component before opening findings. The guided path follows source selection, map, truth explorer, intent questions, structural weaknesses and historical drift, without connecting an account.
The demo illustrates the workflow. Its source access checks, findings, deployment records, and progress are sample data. Resetting or reloading clears your changes. Sample downloads contain only the content you approved in the demo; a sample review does not create a live public link.
Confirm intent asks four optional questions. At least three answers can annotate different components and the identity-to-store boundary. Every answer remains an editable proposal with its source; skipping or resetting never changes an observed fact. Intent & drift history compares two fixed, dated captures with one named fictional approval. It shows why a broader cloud permission invalidates the condition that made a shared identity acceptable. Recorded freshness belongs to each historical evaluation; opening the page does not refresh a capture.
Capabilities & roadmap links every scene to its demonstrated behavior. Draft adoption and named ratification are an October workflow preview; the guardrail scene illustrates December behavior. Later planned-change, release-check and source-intake capabilities remain subject to workspace rollout and review. See Intended architecture for the actual workflow and evidence boundaries.
Choose a task
| Area | What to do | Guide |
|---|---|---|
| Proposed intent and history | Answer or skip the intent questions, inspect proposed map annotations, and compare the two dated captures | Intended architecture |
| Evidence and repositories | Choose a branch, save its path scope, check repository health, and compare captured commits | Repository reviews |
| Review and ownership | Inspect architectural consequence, assign work, save finding views, and preview CODEOWNERS routing | Finding ownership |
| Architecture | Follow a root cause, inspect service owners, compare environments, and trace dependency evidence | Service and dependency inventory |
| Reporting | Select content, approve a report, and share an expiring snapshot | Report review links |
| Customer assurance | Import questions, draft cited answers, review exceptions, and export approved responses | Questionnaires |
| Team oversight | Find stale evidence, unassigned work, and overdue findings across accessible workspaces | Workspace portfolio |
Follow one review
- Choose the workspace that owns the system. Open Integrations, connect evidence, and select repositories.
- Choose a repository branch and profile. Check the captured commit and include/exclude paths before starting the audit.
- Follow collection, scanning, Context Engine reconciliation, and specialist review. Scanner observations need applicability and architectural review before becoming reviewed impact.
- Open a finding and inspect its evidence, consequence, and remaining uncertainty. Assign an owner or preview ownership routing.
- Review the draft report. Confirm its branch, commit, scope, findings, and coverage limitations before approval.
- Export the approved report or create a review link with explicitly selected content. Use approved report evidence to answer a questionnaire.
- Return to the portfolio to find the next workspace that needs attention.
Understand the evidence states
A connected source can still have missing or stale evidence. An observed deployment does not prove a dependency executes at runtime. A manual statement does not become observed evidence simply because it was saved. An empty finding list does not prove that unassessed paths are secure.
Veriom keeps those distinctions visible so the next action is clear: repair access, collect evidence, complete a review, assign an owner, or approve a supported result.
Automate reviews and keep teams informed
Use Apps and audit automations to schedule a listed branch in your timezone, react to GitHub events, and send audit outcomes to Slack, Discord, email, or your own webhook workflow. Delivery history shows confirmations and retries.
Was this guide useful?
Your response stays in this browser unless you open a GitHub issue.Structural weakness engine
How Veriom detects design conditions with deterministic invariants, bounded paths, propagated confidence, and independently reviewable evidence.
Repository reviews and branch comparisons
Select a branch, reuse an audit profile, inspect source health, and compare reviews without losing scope or commit provenance.