Reviewed AI knowledge changes
Understand the operator workflow for reviewing and releasing language knowledge.
On this page
Separate knowledge from live commerce facts
Language knowledge helps interpret supported concepts and aliases. Current prices, stock, ownership and order outcomes still come from the commerce domains.
Knowledge authoring is an operator workflow, not a merchant content-management screen. Use the platform team's approved tooling and deployment runbook.
Review a proposed change
- Identify the exact release and inspect the concept, existing aliases, rules and provenance.
- Prepare a reviewed draft with a source, reason, reviewer and expected pack hash.
- Preview the proposed alias additions or retirements and compare the resulting diff.
- Apply the approved edits to a new immutable draft revision.
- Run the existing freeze, candidate evaluation and promotion gates before release.
Preserve history and handle conflicts
- Existing published knowledge and historical aliases remain intact.
- Expected hashes and revision checks reject stale edits; reload and review the current diff.
- Validation checks ambiguity, normalized meanings, scope and review hashes.
- Audit records retain the reviewer, source, reason and old/new hashes.
Understand authoring limits
The incremental authoring tool handles aliases on existing concepts. New concepts and rules use the reviewed whole-pack and importer workflows. Concept merges and broader rule editors are not part of this authoring increment.