Policy packs

Everything that differs between agencies’ rules is data in a policy pack, so each agency is configured rather than customized. A pack is versioned: one person edits a draft, the system shows the diff, and a different person approves it before it takes effect. Each rule can cite the manual or ordinance it came from.

What a pack holds

Section	What it sets
methods	Procurement methods and thresholds (micro-purchase, informal quotes, formal bid, RFP, cooperative, sole source, emergency) and what each requires
approvals	Approval chains by role, manager or position, on conditions over the record’s facts
approvalTimers	Reminder and escalation timing
ap	Match tolerances for price and quantity
tax	Sales and use tax checks and rates by delivery site
budget	Funds checks, hard or soft control, and whether Spend or the ERP holds encumbrances
bank, paymentMethods	Bank account ownership checks, prenotes and per-method payment limits
pcard	Card limits, blocked and restricted merchant categories, receipt threshold, split-purchase window
expense	Receipt threshold, mileage rate, per diem by location, submission window
construction	Pay applications, retention cap and release timing
sourcing	Bid distribution channels and auctions
clauses	Required contract clauses and the conditions that require them
agents, agentModes	The ceiling on connected agents’ autonomy and amount, and each built-in agent’s mode
ai	Document classes never sent to the AI provider, and the markings that identify them
diversityGoals, cycleTimeTargets	Goals for certified-business spend and target days per procurement stage
fiscalYearStartMonth, recordsRetentionYears	Calendar and retention

Rules are written in a small condition language over the record’s facts (amount, category, funding, CIP-013 scope and so on), so “formal bid above $100,000 for goods, unless a cooperative contract applies” is a rule, not a code change.