Creytix Contracts
The renewal you have to act on before you can still get out of it.
A contract register that computes each notice deadline from the renewal terms and reports what is approaching, what needs notice now, and what has already renewed without anyone deciding.
Auto-renewal stops being something you discover afterwards.
What it does for you
The deadline that matters is the notice date
A contract renewing in March with sixty days' notice must be acted on in January. Watching the renewal date is watching the wrong date — by the time it arrives the decision is gone.
Silently renewed is its own report
Contracts that rolled over with no decision recorded are listed separately, because that is the failure worth surfacing, not another row in a long list.
Obligations become calendar entries
Deliverables and review dates come out as dated entries, so an obligation lives somewhere someone looks.
Capabilities
- Contract register with renewal terms
- Computed notice deadlines
- Renewal watch by urgency
- Silently-renewed report
- Obligations as calendar entries
Proof, not adjectives
- Engine ships and is tested
- src/lib/contracts/register.ts — notice-deadline computation, the renewal watch, the silently-renewed report and calendar generation, with its own suite.
Related tools
Built with Creytix, on Creytix
This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.