Question
A claim enters the system.
A resolution case defines the question, policy, evidence inputs, and expected verdict shape.
accepted
AI Resolution Infrastructure for GenLayer
Real-world questions resolved into verifiable state.
GenLayer Resolution turns ambiguous claims into evidence-bound verdicts using independent AI validators, transparent consensus, replayable audit trails, and registry-ready payloads for intelligent contracts.
EvidenceValidatorsConsensusRegistry
Illustrative ResolutionResolution complete
Question
Was the GenLayer project boilerplate created by GenLayer Labs?
Case createdEvidence fetchedEvidence normalizedValidators evaluatingConsensus increasingRegistry payload readyAudit recorded
EvidenceValidatorsConsensusRegistryReplay
Agreement82%
Why it exists
AI alone is not a decision layer.
Single AI answerOpaqueNo replayProvider trust
Resolution layerEvidence-boundFull auditGenLayer-ready
Resolution pipeline
A verdict is built, not asserted.
The interface follows the trust chain in order. The visitor sees the same sequence an operator audits: question, evidence, validation, consensus, registry, replay.
Evidence
Sources are collected and scored.
Every URL is fetched, normalized, hashed, and recorded with failures visible instead of hidden.
verified
Validation
Independent validators reason from evidence.
Validators use configured models and roles. Each vote, rationale, risk flag, and timeout is preserved.
verified
Consensus
The policy determines the outcome.
Agreement, confidence, participation, and threshold checks produce YES, NO, or UNRESOLVED.
verified
Registry
The verdict becomes structured state.
Evidence and consensus hashes are prepared for the GenLayer registry as a compact payload.
payload ready
Replay
Every step remains auditable.
Operators can replay the case lifecycle, inspect raw events, and verify the trust chain.
verified
Evidence first
Trust starts with sources the system actually touched.
Evidence PacketLOCKED
pkt_0xe3b0Official DocumentationGenLayer · Docs
LOCKEDSourceNormalizeVerifyPacketLocked
canonical documentation source
Repository READMEGitHub · Repository
SCOREDSourceNormalizeVerifyPacketLocked
accessible repository source
Project SpecificationGitHub · Specification
VERIFIEDSourceNormalizeVerifyPacketLocked
project-owned repository source
NormalizeVerifyPacketLocked
Failed sources stay visible. Blocked URLs, 403 responses, timeouts, and low-relevance evidence become part of the record because unresolved outcomes are safer than fabricated certainty.
Evidence lockedValidators initialize
Validator mesh
Independent workers reason before agreement exists.
Validators evaluate independently with role-specific models. Each worker publishes a vote, confidence, risk flags, reasoning, and latency before the system calculates consensus.
Evidence Packet
pkt_0xe3b0Votes receivedConsensus builds
Consensus engine
Agreement emerges from the published votes.
Consensus is calculated from votes, participation, confidence, validator weight, disagreement, and the active policy threshold. Metrics explain the outcome, but the agreement network is primary.
82%agreement
Participation 100%Policy threshold 67%Decision YESDissent 1 validator
Consensus Core82%Policy threshold reached
YES4 validatorsNO0 validatorsUNRESOLVED1 dissent
82% AgreementConfidence stabilizes through majority validator weight
Policy reachedYES becomes the resolved decision
Consensus reachedRegistry prepares
GenLayer registry
The outcome becomes something contracts can use.
The final verdict is prepared as structured registry state: case ID, policy version, evidence hash, consensus hash, confidence, and audit reference.
01PayloadCase state
02SerializationCanonical shape
03HashContent address
04SealVerified seal
05RegistryContract anchor
06ImmutableLocked state
Consensus hash
0x9f41c2e7b6a30d...e84fCase IDEvidence HashConsensus HashAudit Reference
QuestionEvidenceValidatorsConsensusRegistryReplay
Registry anchoredReplay records
Replay audit
Every answer has a path back to its inputs.
rpl_01arpl_02crpl_03frpl_04drpl_05erpl_06brpl_07cAudit recordedConsole ready
Enter the operating system
Launch the console when you are ready to resolve a case.
The console opens the operational system: create a question, preview evidence, run validators, inspect consensus, and prepare the registry payload.