Expand description
marque-rules — trait definitions for the marque rule system.
This crate defines the contract every rule crate must satisfy.
It has no rule implementations — those live in marque-capco and future crates.
The engine depends only on this crate, enabling rule crates to be swapped.
§Type split: FixProposal vs AppliedFix
FixProposal is pure data emitted by rules — deterministic, timestamp-free,
classifier-free. AppliedFix wraps a proposal with runtime context (timestamp,
classifier id, dry-run flag) and is constructed only by Engine::fix.
This makes “suggested vs applied” a type-system invariant.
Re-exports§
pub use confidence::Confidence;pub use confidence::FeatureContribution;pub use confidence::FeatureId;
Modules§
- confidence
- Confidence — Phase D audit-provenance payload.
Structs§
- Applied
Fix - A promoted
FixProposalwith runtime context. - Diagnostic
- A single diagnostic emitted by a rule check.
- Engine
Promotion Token - Engine-only proof-of-construction token for
AppliedFix::__engine_promote. - FixProposal
- A proposed fix for a diagnostic violation.
- Rule
Context - Document position context passed to rules alongside parsed markings.
- RuleId
- Unique rule identifier string (e.g., “E001”, “capco/portion-mark-in-banner”).
Enums§
- Document
Position - Coarse position within the document (for banner detection heuristics).
- FixSource
- Provenance of a fix proposal — where the fix recommendation originated.
- Marking
Type - Classification marking candidate type, determined by scanner heuristics.
- Severity
- Rule severity level. Configurable per rule in
.marque.toml. - Zone
- Document zone — where in the document structure a marking appears.
Constants§
- CORRECTIONS_
MAP_ CITATION - Canonical citation string for diagnostics whose authority is the user’s
[corrections]config entry (C001 and the engine’s pre-scanner text-scan path). C001 is not a CAPCO rule — no CAPCO passage governs user-defined typo replacements — so the citation is a config pointer rather than a §/page/line reference. Holding the string in one place prevents silent drift between the rule-pipeline emission site inmarque-capcoand the pre-scanner emission site inmarque-engine; both paths produce the same audit-record shape.