@praxisui/charts 8.0.0-beta.2 → 8.0.0-beta.21

package/README.md

@@ -378,6 +378,39 @@ This first published version is focused on the core runtime:
 - declarative `selectionChange` and `crossFilter` actions emitted from selected chart points
 - `distinct-count` aggregation mapped to canonical `praxis.stats` `DISTINCT_COUNT`
 - host-owned remote data resolution through `remoteDataResolver`
+- executable agentic authoring manifest for `praxis-chart`, exported as `PRAXIS_CHARTS_AUTHORING_MANIFEST`
+
+## Agentic Authoring Contract
+
+`@praxisui/charts` publishes a component-level authoring manifest for `praxis-chart`.
+The manifest is an executable backend/tooling contract for canonical
+`PraxisXUiChartContract` documents, not prompt-routing documentation.
+
+The governed authoring targets are:
+
+- `chartType`
+- `series`
+- `axis`
+- `dataBinding`
+- `queryContext`
+- `crossFilter`
+- `drilldown`
+- `selection`
+- `legend`
+- `tooltip`
+
+Remote resource and field binding must come from governed API metadata,
+`availableResources` and `availableFields`. Cross-filter, drilldown and
+selection authoring persists structured `events.*` actions instead of command
+strings or raw prompt examples. The visual editor remains the canonical
+round-trip surface for this document: open, edit, apply/save, reset and reopen
+must preserve the same `x-ui.chart` shape consumed by the runtime.
+
+Each manifest operation declares its own editable target, resolver,
+ambiguity policy, preconditions, validators, affected paths, effects and
+`submissionImpact`. Chart document, type, series and axis changes are
+`config-only`; remote data binding, query context and event mappings
+`affect-remote-binding`; legend and tooltip changes are `visual-only`.
 
 ## Current Non-Goals