## Definitions

For development and engineering priorities (let's not talk include DEFINE research work immediately)

- Now: this sprint
- Next: short-term in the next 4-8 sprints
- Future: months, years into the future

## Next

- **Reviewing the oscal-content repository for example data (*not* official catalogs)**
- Can we go linear? catalog->profile; CDEFs+SSPs; AP+ARs;
- How simple can we go? What is the minimally viable and complex?
- How realistic do they need to be?
- What is implied process by usage of OSCAL?
- **Planning cohesively documenting approach to model usage** (how do the examples connect?)
- Control mapping

## Future

- CRM
- Cross-model risk linking
- Constraint and allowed-value improvements
- Profile resolution tech debt?
- OSCAL website content review
- SSP examples around inventory (documentation)