Skip to content

spec: what a copy does not carry over - #58

Open
delchev wants to merge 1 commit into
mainfrom
spec/duplicable-defaults-reset
Open

spec: what a copy does not carry over#58
delchev wants to merge 1 commit into
mainfrom
spec/duplicable-defaults-reset

Conversation

@delchev

@delchev delchev commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

The site half of intent-specification#76.

duplicable: true clones the source header verbatim, so every ordinary user field rides along - including the ones a business rule says must be fresh. On a sales invoice the copy carries the source's date, due and taxEventDate, and a calculatedActionOnCreate cannot correct them: such a rule fills an empty value and respects a present one, which is exactly what makes the copied value stick.

Adds ### What a copy does not carry over to the Entities page (after Control order, before unique), and points the duplicable row of the entity-level attributes table at it. Covers the object form (defaults: + reset:) and why the two keys are separate, the build order of the clone, the now token's per-field shape plus its local-calendar rule, and the list of invalid declarations.

Implemented in eclipse-dirigible#7360. Verified with npm run docs:build (clean).

🤖 Generated with Claude Code

`duplicable: true` clones the source header verbatim, so a copied invoice
keeps the source's date, due date and tax-event date - and a create-time
rule cannot correct them, because such a rule fills an empty value and
respects a present one. Document the object form (`defaults:` + `reset:`),
the build order of the clone, the `now` token's per-field shape and its
local-calendar rule, and what is invalid.

Proposal: IntentFile/intent-specification#76

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant