SELF-SERVE PREVIEW · VERIFICATION SCOPE
A rule result is not a guarantee.
Aegis applies configured checks to structured batch data and reports a rule-based amount recommendation. The buyer and provider still decide whether the work is acceptable, what needs repair, and how to settle outside Aegis.
Four different questions
- Structure and timing
- Checked against configured rules: JSONL structure, required fields and types, allowed domains, normalized duplicate keys, record-count thresholds and submission deadline.
- Item-by-item source matching
- Not checked in this preview. An allowed domain and a record count do not establish that the requested source items were delivered.
- Factual accuracy
- Not independently verified. A correctly typed price, inventory value or URL can still be inaccurate or fabricated. Aegis does not fetch source pages to check facts.
- Business acceptance
- Not recorded by the current product. A rule result or page view is not evidence that the buyer accepted the delivery.
Reading the result and amount
The existing API statuses accepted, partially_accepted, rejected and manual_review describe configured rule outcomes, not factual truth, agreement, or a completed transaction. The interface labels them as rule results.
Amounts follow the recorded thresholds and failure policy. A pro-rata amount uses the exact rule-valid record fraction and rounds half-up to the minor unit. This is one configured pricing method, not a definition of economic fairness. Important missing records may matter more than their count suggests.
No payment or refund is recorded or executed by Aegis. A zero-payable recommendation is not proof that money was prepaid or refunded. Any payment or refund must be handled through the parties' existing channel. Manual review does not mean that Aegis has appointed an arbitrator.
Hashes, versions and clocks
The deal hash binds the canonical terms. The artifact hash binds the exact uploaded bytes. A hash is not a signature: it does not prove that the content is true, that a person agreed, or that an identified organization submitted it.
Reports carry an evaluator version, evaluation time and clock source when those fields were recorded. Missing legacy fields remain unknown. Displaying an old receipt does not reevaluate it with today's code.
For the web flow, delivered_at is the server's submission receipt time. evaluated_at is the evaluation time with its stated clock source. Datetime values inside the artifact are provider-declared; falling within the permitted interval does not prove when a source was actually observed. None of these is a qualified third-party timestamp.
Agreement and authority
The current preview has no separate in-product provider confirmation step. Creating or opening a record is not evidence that the provider agreed to its terms. This does not rule out agreement through another channel. A capability link authorizes its holder to perform scoped actions; it does not authenticate their identity or representative authority. Keep private capability links private.
Retention and the latest report
Raw JSONL is checked in memory and not retained. Report metadata expires, and the owner can delete the record earlier. Both parties should keep their own terms, artifacts and reports before expiry or deletion. Deletion from Aegis does not erase copies already retained elsewhere.
The public page shows the first receipt of the latest distinct artifact, not an immutable URL for every historical version. Retrying an identical artifact returns its first receipt without making it the newest public result. No independently signed offline evidence bundle is provided in this preview.
Implementation availability
The implementation repository is currently not publicly available. This page explains the verification boundary; it is not a substitute for a public code audit. A separate, reviewed release of the minimal validator, specification and test vectors would require an explicit publication decision. Do not treat this preview as independently audited or guaranteed.