Repository navigation
Collections stage 4: reference fields and repeaters (needs RFC) #114
Description
Planned after stages 1–3 (#71, closed): reference fields (an entry pointing to entries of another collection) and repeaters/blocks (lists of grouped values). RFC-0042 §6 left them out on purpose. They need:
- cross-node integrity: what happens when a referenced entry is deleted or archived;
- a locale rule for references;
- cost control for resolving them on render;
- nested Studio forms;
- MCP and JSON Schema output that strict structured-output modes still accept.
Next step: an RFC (.agents/skills/write-rfc). No implementation before it is accepted.
Activity
docs(rfc): accept RFC-0045 (collections stage 4)
Madraka commentedon Nov 10, 2026
RFC-0045 (collections stage 4: reference fields and repeaters) was accepted on 2026-11-10, with its three decisions ratified. The document is in PR #193:
docs/rfcs/0045-collections-stage-4-references-and-repeaters.md.Rollout, one PR per step. Both new types stay refused on every write path until step 7.
asset_refsby site, a prerequisite. It scopesdeleteAsset, the rebuild and theunusedfilter by site, chunks the rebuild, adds field assets to the purge asset rule, and skips the rebuild on anunchangedimport. That last part fixes Sync: an 'unchanged' import rebuilds asset_refs from plan-time rows and can drop a concurrent edit's row #196.pnpm gen, thefields_unsupportedgate (checkFieldDefinitionsandcheckBundle), and the checker, resolver and JSON Schema emitter. No behaviour change.entry_refs(migration 0033), the batch-time guards, rebuilds,fieldAssetRefsfor repeater items, kind-aware release dependencies and edition id mapping. It also changes behaviour on existing sites:translation_group_in_use, thereadsOriginaltightening, the group check on group-only changes, canonical import bodies, and the collections anchor.fields: 2.fieldsSchemaStrict,fieldsStrict/clearFields,list_references, the translation tools.EntryPicker,ReferenceList,RepeaterField,FieldControlandUsedByListblocks, plus the builder.fields: 2, followed by a one-time, per-node rebuild.ReferenceValueSourcewithtargetField.The RFC's "Implementation watch list" names the riskiest SQL. Each phase PR's review checks it.
Merge pull request #193 from cloudhal-dev/docs/rfc-0045-references-re…
Merge pull request #203 from cloudhal-dev/claude/rfc45-contract-core-…