Vendor Contracts

Architecture decisions are commercial decisions. Recording your vendor agreements lets the platform leverage what you already pay for, and warn you when a design's commercial footing is about to change under it.

Record an Agreement

One entry per vendor: status (active, upcoming, or expired), start, end, and renewal dates, discount percentage, committed spend, a preferred flag, and free notes. Two of these do most of the work: the renewal date drives every renewal warning, and the discount appears wherever leverage is shown.

Where Contracts Act

Surface	Effect
Generation	Among equally suitable approved technologies, contracted and preferred vendors win the tiebreak; the design leans toward money already spent
Component cards	Selected components show a leverage chip: "existing contract, 18% off, renews 2026-09-01"
Gap decision options	Options from contracted vendors carry an existing-contract chip, so the commercial context is visible at decision time
Workbench	Contracts renewing within 90 days appear on the renewal watch
Approval readiness	Advisory exposure line: components depending on a contract renewing soon or lapsed
Drift detection	After approval, a leveraged contract renewing or lapsing raises a vendor finding that auto-resolves once renewed

The Loop, Closed

The point is symmetry: contracts flow into designs as leverage, and flow out as risk when the agreement's state changes. Renewing the contract (or completing the migration off that vendor) clears the warnings on their own; no bookkeeping to remember.