Entrypoints and Examples¶

Use these entrypoints when choosing the right maintainer command. This crate is a binary boundary; there is no Rust library API to call from product crates.

Maintainer Route¶

flowchart TD
    change["repository policy<br/>or benchmark evidence change"]
    command["bijux-gnss-dev command"]
    evidence["validation output<br/>or benchmark report"]
    review["maintainer review"]

    change --> command --> evidence --> review

Command Selection¶

maintainer question	command	evidence produced
Are reviewed audit exceptions valid and unexpired?	`audit-allowlist`	pass/fail over `audit-allowlist.toml`
Which cargo-audit ignore flags are allowed?	`audit-ignore-args`	derived `cargo audit --ignore` arguments
Are dependency-policy deviations still reviewed?	`deny-policy-deviations`	pass/fail over `configs/rust/deny.deviations.toml`
Did benchmark evidence regress beyond the allowed threshold?	`bench-compare --strict`	artifacts and benchmark snapshot comparison

Example Sequence¶

If a maintainer updates a reviewed security exception, the durable sequence is:

edit audit-allowlist.toml
run bijux-gnss-dev audit-allowlist
run bijux-gnss-dev audit-ignore-args if automation consumes the derived flags

If a maintainer changes benchmark evidence, the durable sequence is:

run the benchmark comparison workflow
inspect current evidence under artifacts/
update benchmarks/bencher_baseline.txt only when the new baseline is intentionally accepted

First Proof Check¶

Inspect crates/bijux-gnss-dev/docs/COMMANDS.md, crates/bijux-gnss-dev/docs/WORKFLOWS.md, crates/bijux-gnss-dev/docs/PUBLIC_API.md, and crates/bijux-gnss-dev/src/main.rs.