Expand description
Indexed ingestion shared by native inline verification and future Worker
scheduling. Verification extracts large objects into the global object
store before a pack’s Verified state is written (WP-4.10).
Modules§
- budget
- Per-slice subrequest accounting and pack window reads (WP-4.8).
- checkpoint
- Job and checkpoint rows of scheduled verification (
vc, WP-4.8). - classify
- Ticketed upload classification by its first four bytes.
- entries
- Pure index metadata derived from decoded pack entries.
- geometry
- Indexed admission geometry: payload, canonical object and encoded frame bytes.
- inspection
- Bounded, metadata-only enumeration of added-pack files for launch inspection.
- job
- Scheduled verification: the kind-7 slice machine (WP-4.8, R-171).
- publication
- Verify the complete resulting pair, independently of inspector verdicts.
- resolve
- Repository-isolated external delta resolution from member index rows.
- scheduled
- The advance’s side of scheduled verification (WP-4.8).
- state
- Per-(repository, pack) verification state, outside the advance batch.
- verify
- Inline verification before a ticketed advance commits.
Structs§
- Indexed
Config - Limits for opt-in indexed mode. A deployment cannot switch an existing
opaque repository to indexed mode: its member packs have no
irows. Native embedders configure it programmatically; Workers enable it through the Paid Workers launch profile with scheduled verification, permanent retention and GC disabled. Async inspection and holds remain post-launch features.
Enums§
- Verification
Mode - Where a ticketed pack is verified.
Constants§
- DEFAULT_
EXTRACT_ MIN_ BYTES - The default
IndexedConfig::extract_min_bytes: 64 KiB. - DEFAULT_
MAX_ ANCESTRY_ COMMITS - The default
IndexedConfig::max_ancestry_commits. - MAX_
ANCESTRY_ COMMITS_ LIMIT - The largest accepted
IndexedConfig::max_ancestry_commits. - SCHEDULED_
MAX_ ANCESTRY_ COMMITS IndexedConfig::max_ancestry_commitsunder scheduled verification: a Worker alarm cannot walk more (WP-4.17’s Worker cap, R-171).
Functions§
- pending
- The canonical pending response: one protobuf detail, HTTP 503 and
Retry-Afterrounded up to whole seconds.