Axis 08 · PRICING
Pricing Intelligence & Margin Protection
What may be said about price on each surface, and what must never leave the building?
Status
COVERED
answered by a rule or taxonomy today
Rules in force
4
RULE-COST-BAND-001 · RULE-TIER-DISPLAY-001 · RULE-MOQ-APPROVED-001 · RULE-SR-DEFAULT-001
Open gaps
1
each with a stated fix
Decision purposes
2
COST · TIER_COMPARE
Rules answering this axis
| ID | Rule | Status | Ev. | Publication |
|---|---|---|---|---|
| RULE-COST-BAND-001 | Never invent a figure — and match the visibility class to the figure, not to the surface | APPROVED | B | PUBLIC |
| RULE-TIER-DISPLAY-001 | Tier naming — display labels vs code keys | APPROVED | B | PUBLIC |
| RULE-MOQ-APPROVED-001 | No full supplier minimum below APPROVED — a trial quantity is a named exception | CANDIDATE | B | INTERNAL |
| RULE-SR-DEFAULT-001 | StayReady furnishes by bundle over existing SKUs, not bespoke | APPROVED | C | PROFESSIONAL |
Taxonomy
- els-canon-sources.json pricing_authority
- scope-ownership.json
Canon cited
- ALUMAX Sell Catalog (sell-price owner)
- ADOS two-OS ruling — margin lives in staff-gated OS1
- ELS_ALUMAX_Estimator_2.xlsx Rate Card (INTERNAL)
What is missing
1 openMargin protection is enforced by convention, not by a check
RULE-COST-BAND-001 forbids an RM figure on a public surface. Nothing in this repo verifies that a rule, brief or published surface complies — the estate's own Sell tool ships a CCT validator, but this repo has no equivalent guard on money.
Fix — A validate.mjs check that fails on an RM figure inside a PUBLIC-level rule would make the rule self-enforcing. Cheap, and it is the one place automation clearly pays.