FAQ¶
Is plugin registration global?¶
No. Plugin loading is instance-scoped via PluginRegistry per runtime.
Does stage order change based on config order?¶
No. Execution order is fixed: clean -> filter -> label -> rate -> match.
Can I disable stages?¶
Yes. Set enabled = false on the stage section.
What if plugin manifest is omitted?¶
Runtime uses an empty plugin registry and only built-in stage behavior.
How do I make runs deterministic?¶
Use fixed inputs/config/plugins and set [runtime].random_seed.
Why do I see success with errors in diagnostics?¶
You likely set fail_fast = false; check non_fatal_errors.
What is the difference between doctor and reliability check?¶
doctorvalidates readiness and prints checks but does not write an artifact.reliability checkruns the same evaluator and writes a gate artifact (dist/reliability/latest/gate_result.jsonby default).
Use doctor for local debugging and reliability check --strict for CI gates.
Where should reliability thresholds live?¶
In a separate reliability.toml file passed with --policy.
Reliability thresholds are intentionally not embedded in pipeline.toml in v1.
What is the difference between ingest sync and ingest sync-all?¶
ingest syncruns one source directly from CLI flags.ingest sync-allruns multiple enabled sources fromingest.tomlin order.
Both write deterministic reports and latest parquet outputs.
Why did missing jobs not get tombstoned?¶
Tombstones are only applied when coverage is complete.
If a run is truncated by max-pages or max-jobs, HonestRoles marks
coverage_complete = false and does not tombstone missing records.
What is snapshot vs latest parquet?¶
- Snapshot parquet is per-run immutable output under
snapshots/. - Latest parquet is rebuilt from active catalog records and used as runtime handoff.