Building operational software and evidence-bound verification for AI-assisted development.
EvoRise Tech focuses on practical software systems for operations, controlled automation, and evidence-bound software delivery.
We work on systems that connect operational reality, software execution, evidence, and human decision-making — without treating AI output as inherently trustworthy.
Evidence-bound verification for untrusted software changes, with AI-generated patches as the primary use case.
EvoOM Guard helps answer one narrow question:
Did this change satisfy the selected judge without manipulating the evidence used to decide?
It provides:
- protected test-harness and policy gating
- structured judge-owned verdicts
- separately packaged verifier packs
- optional black-box execution
- explicit execution and isolation evidence
- offline semantic record verification
- authenticated evidence bundles
Main repository:
EvoOM Guard
Live status sources:
Those core pages are the source of truth for the current published release, repository roles, implemented mechanisms, evidence boundaries, and known gaps. The summary below deliberately avoids duplicating version numbers that can become stale.
Selected public repositories:
| Repository | Current role and evidence boundary |
|---|---|
| EvoOM Guard | Authoritative source-available CLI, GitHub Action, releases, threat model, and security policy. Rely on the linked live status pages for its current release and supported claims. |
| EvoOM Guard Demo | Frozen public demonstration evidence. Its exact version and evidence boundary are recorded in the live project-status map; it does not establish coverage for later releases. |
| EvoOM Guard Evaluation | Archived historical evaluation protocol and record. It is not an independent evaluation or a general accuracy result; its exact scope is recorded in the live project-status map. |
| Trusted Finalizer Pilot | Historical controlled same-owner pilot evidence. It is not production enforcement or third-party validation; its exact version and boundary are recorded in the live project-status map. |
The pilot uses MANA-awam for technical separation of review/deployment roles.
Both accounts are controlled by the same owner, so this is not an independent
review or security audit. The core repository's
project-status map
states the public/private operational boundary and the exact claims supported
by each repository.
- Operational software systems
- Business process automation
- Software verification infrastructure
- Governed AI-assisted development
- Evidence-based engineering workflows
- No result without traceable evidence
- Requested assurance is not treated as delivered assurance
- AI-generated code remains untrusted until independently verified
- Security claims must state their real boundaries
- Operational truth should remain connected to technical execution
EvoRise Tech is based in Saudi Arabia. This profile and its public projects are maintained by Mana Alharbi | مانع الحربي.
Website: evoriseksa.com
Project and release status change as implementation and evidence are added. Read the core repository's project-status map and release-status page for the current, versioned position. Unless those sources explicitly record otherwise, the public repositories do not establish independent validation, third-party adoption, a hosted service, or a general effectiveness rate.