Listaro Docs

Artifacts and durable jobs

How Listaro stores and exposes source-backed results.

The job lifecycle

A crawl or batch may run asynchronously. Use get_job to inspect the saved state and cancel_job to request safe cancellation. Treat queued, running, partial, failed and cancelled states distinctly where the engine returns them.

The local queue stores worker leases and recovery state in PostgreSQL. A frontend spinner or accepted request is not proof that work completed successfully.

Evidence artifacts

The engine's artifact store provides opaque IDs rather than exposing arbitrary filesystem paths. The get_artifact tool accepts:

  • artifactId — opaque artifact identifier
  • offset — byte position for bounded reads
  • limitBytes — bounded read limit
  • encoding — UTF-8 or Base64 where appropriate

Artifact metadata includes content type, SHA-256 hash, byte size and pagination information. Retrieval must recheck authorization and integrity before any commercial deployment.

What the console must show

Source URL, capture time, actual acquisition mode, content/evidence hashes, explicit completeness warnings, status and artifact links. Partial captures must never be represented as complete datasets.

The proposed 1B durable event outbox and extended artifact manifests are documented separately in supplemental enhancements until certified.

On this page