Technology / boundaries made visible
Orvessian connects records across systems without pretending that every kind of trust is the same.
The architecture
Your agent or runtime executes the work and enforces permissions.
Authority and sensitive evidence remain within the organisation's controls.
Signed records bind events to evidence; verifiers check specific properties.
Base records batch commitments; private records, indexes and inclusion proofs support review.
Architecture direction. Components have different readiness levels; the complete product is not a production release.
What does “verified” actually mean?
Disclosed bytes match their commitment. This does not establish whether the evidence is true.
A particular key signed a record. Identity and trust in that issuer require additional checks.
The relevant permission holds at a defined reference point. Runtime enforcement remains a separate responsibility.
A precisely defined computation evaluated a committed action against a committed policy. Not a general proof of AI correctness.
A reviewer attests to a specific decision and evidence version. Human judgement remains fallible.
A record belongs to a checked chain view or batch. Inclusion does not authorise every leaf or guarantee permanent finality.
Safety evidence boundary
A policy gateway, sandbox or security monitor must make a local allow, block, pause or revoke decision without waiting for a ledger. Orvessian can then bind selected policy versions, alerts and authorised interventions into an independently checkable timeline.
A confirmed record may be harder for one operator to silently change than a private database entry. Attackers can still compromise keys, source events, runtimes, relayers, indexes, contracts or consensus. The claim must always be checked against the actual system and its operators.
Current technical baseline
Versioned profiles, exact-byte commitments, signatures, private openings, streams and batch links exist in local reference tooling.
The internal alpha’s RISC Zero policy path proves a committed action against committed policy and configuration. It does not prove AI execution or outcome truth.
A supervised relayer sponsors synthetic batch transactions on Base Sepolia. The portal checks canonical inclusion; production mainnet operations remain gated.
Independent infrastructure
Base is the accepted launch settlement direction. Orvessian operates a governance and verification application on that network; it is not launching its own L1 or a separate L2.
Private structured records and receipt openings stay in the platform database. Only batch commitments are published. The recording key and gas-paying publisher have distinct roles; customers need neither ETH nor a native token.
Current evidence comes from Base Sepolia, including sponsored submission and restart recovery. Historical mining experiments are outside the launch plan. Larger and hierarchical batches still need measurement.
General 0.4.0-alpha receipts and the authorised AVR flow have different capabilities. Missing evidence, unsupported checks and unknown authority should remain visible rather than becoming a universal success badge.