Save this task as task-demo.json in the reference directory, or use the supplied file in the documentation package. Every line matches at least one term; the second line ranks first because it matches two distinct terms.
{
"version": "0.2",
"operation": "literal-line-search",
"document": "Alpha\nalpha delivery\ndelivery",
"terms": ["alpha", "delivery"],
"top_k": 2
}Swipe or scroll to view all columns →
| Rank | Line | Score | Matched terms |
|---|---|---|---|
| 1 | 2 | 2 | alpha, delivery |
| 2 | 1 | 1 | alpha |
total_matches is 3 before truncation. The line field is one-based. Each match includes the original line text and matched_terms in normalized term order. No match produces an empty matches array and total_matches equal to 0.
Receipt fields#
Swipe or scroll to view all columns →
| Field | Value or meaning |
|---|---|
| version | "0.2" |
| execution | "local-cpu" |
| implementation | "ocean6-python-reference/0.2" |
| task_sha256 and result_sha256 | SHA-256 of the exact original file bytes |
| started_at and finished_at | Local UTC claims with six fractional digits and a Z suffix |
| signature and settlement | Both null |
verify first compares the result with a replay, then checks the exact receipt field set, fixed values, file digests, timestamp format and time ordering. JSON whitespace and member order do not affect semantic comparison, but any byte change affects the relevant receipt digest.
A local receipt is not an authenticated execution certificate. An attacker who replaces the task, result and receipt together can construct a self-consistent bundle. These records do not identify a remote executor or prove a payment.