Conversational document-schema creation is already a general capability delta
Retired delta: one vendor's paired announcements do not yet demonstrate a reusable cross-product capability change.
Disappearing action
Human ritual: Promote a same-vendor launch and duplicate signal pair into a durable, general capability delta. Old cost: The record overstates portability and user impact while hiding schema complexity, validation, error rates, and vendor coupling. Replacement pattern: Keep the launch as a source-inspected signal; publish a delta only when independent implementations demonstrate the same bounded capability with inspectable reliability limits.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | llamaindex.aisource | primary receipt | source_urls |
| 2 | x.comsource | supporting receipt | source_urls |
Why this delta is retired
Natural-language schema creation is an appealing capability claim: describe the fields needed from a document and let an agent construct an extraction setup. The evidence here does not yet establish that it is a general, reusable capability. It is one vendor announcement and closely related communication from the same source family, not independent confirmation across products or workflows.
The difference matters because a schema is not merely a list of field names. It contains validation rules, optionality, normalization, provenance, confidence thresholds, exception routing, and consequences for downstream systems. A demonstration can make the first draft easier while leaving the hardest reliability work unchanged.
Better unit of observation
Keep the underlying release as a source-inspected signal. Ask a bounded question instead: for a stated document class and field set, can the system produce a schema that validates, exposes evidence for each extracted value, reports errors, and survives an independent replay? If the answer is yes in multiple unrelated implementations, that can support a future Delta.
Where the old interface wins
Hand-authored schemas remain clearer for stable documents, compliance-sensitive fields, and deterministic integration contracts. They let a team specify validation before extraction and diagnose a failed record without interpreting an agent’s explanation. Conversational assistance may speed schema design, but it does not remove the need to own those rules.
Reopen condition
Reopen only after independent tools demonstrate the same bounded workflow with explicit validation and error evidence, a reproducible task boundary, and counterexamples that reveal where the capability fails. Until then, calling it a general Delta would confuse a promising launch with verified portability.