Pre-release documentation. This guide describes the current product design and evaluation build. Packaging, availability and commercial terms may change before release.
1. Connect authoritative sources
Start with the material that already governs the organization: policy manuals, procedures, contracts, control matrices, workbooks and code conventions. Scope the source set to a decision domain that has a clear owner.
- Preserve the source revision and location of every cited span
- Separate authoritative material from helpful reference content
- Record effective dates, jurisdictions and ownership where they matter
2. Compile proposals
The compiler extracts actors, actions, objects, conditions, deadlines, outcomes and source evidence into typed proposals. It also surfaces conflicts, unresolved references and calculation checks.
3. Confirm and test
Authorized reviewers compare each proposal with the verbatim source, correct the structured meaning, reject unsupported material and run representative decision cases. Workbook calculations can be checked against sample cells already present in the source.
- Review history remains attached to the rule
- Conflicts block publication until resolved
- Simulation shows how a draft would change recorded decisions
4. Publish a sealed version
Publishing creates a signed, content-addressed Rulepack. The version freezes the rules, definitions, quotes and compiled predicates that can participate in a decision.
avy compile ./company-policy
avy review
avy publish
avy ask "Can a contractor approve this expense?"