Adaptive Formalization

Use this skill to guide representation design in AI/Agent-native software systems. The goal is not to avoid schemas. The goal is to choose the degree of formalization that fits the entity's current product role, evidence maturity, consumer needs, and risk.

Core principle:

Choose the right degree of formalization for the entity's current product role. Preserve Agent semantic freedom where it creates product value, and add structure where system boundaries, consumers, validation, or auditability require it.

Reach for this skill when creating or materially changing durable representations: DB tables, ORM models, API DTOs, JSON schemas, events, config schemas, state machines, Agent memories, plans, profiles, evaluations, workspace artifacts, or outputs that may become UI state or workflow input. Do not use it for routine internal refactors where no representation boundary changes.

Formalization Gradient

Treat schema objects and Agent artifacts as points on a gradient, not as opposing categories: