Conversation
wmadden
added a commit
that referenced
this pull request
Mar 30, 2026
Promote design principles (self-describing domain model, domain/persistence separation, scoped family details, facts-not-instructions) to cross-cutting learnings. Update contract-symmetry with domain/storage separation proposal. Update design questions #1 (embedding as relation property), #6 (discriminator + variants), #10 (domain level as shared contract surface) with concrete design answers. Update overview with redesign summary.
wmadden
added a commit
that referenced
this pull request
Mar 30, 2026
wmadden
added a commit
that referenced
this pull request
Mar 30, 2026
Promote design principles (self-describing domain model, domain/persistence separation, scoped family details, facts-not-instructions) to cross-cutting learnings. Update contract-symmetry with domain/storage separation proposal. Update design questions #1 (embedding as relation property), #6 (discriminator + variants), #10 (domain level as shared contract surface) with concrete design answers. Update overview with redesign summary.
wmadden
added a commit
that referenced
this pull request
Mar 30, 2026
wmadden
added a commit
that referenced
this pull request
Mar 31, 2026
Promote design principles (self-describing domain model, domain/persistence separation, scoped family details, facts-not-instructions) to cross-cutting learnings. Update contract-symmetry with domain/storage separation proposal. Update design questions #1 (embedding as relation property), #6 (discriminator + variants), #10 (domain level as shared contract surface) with concrete design answers. Update overview with redesign summary.
wmadden
added a commit
that referenced
this pull request
Mar 31, 2026
jkomyno
pushed a commit
that referenced
this pull request
Apr 1, 2026
Promote design principles (self-describing domain model, domain/persistence separation, scoped family details, facts-not-instructions) to cross-cutting learnings. Update contract-symmetry with domain/storage separation proposal. Update design questions #1 (embedding as relation property), #6 (discriminator + variants), #10 (domain level as shared contract surface) with concrete design answers. Update overview with redesign summary.
jkomyno
pushed a commit
that referenced
this pull request
Apr 1, 2026
wmadden
added a commit
that referenced
this pull request
Apr 27, 2026
…on API - spec FR4.1-4.4: standardise root accessors on lowercased plurals (db.orm.users / db.orm.posts) per the emitter output, drop the db.transaction(...) runtime requirement, and rewrite FR4.4 so it documents the replica-set requirement and points at TML-2313 as the owner of both the API and dev-environment provisioning. - spec acceptance criteria: switch the Mongo facade-parity AC to db.orm.users.where(...).first() and the transaction line to a documentation-only requirement linking TML-2313. - spec Decisions: rewrite #1 to capture the emitter-driven root convention; add #10 recording that the transaction API is deferred end-to-end to TML-2313. - plan M3 task list: replace the db.transaction implementation task with the documentation task, mention binding-mirror connection inputs, and align the type-chain task and E2E task with the new accessor names.
wmadden
added a commit
that referenced
this pull request
Apr 27, 2026
…on API - spec FR4.1-4.4: standardise root accessors on lowercased plurals (db.orm.users / db.orm.posts) per the emitter output, drop the db.transaction(...) runtime requirement, and rewrite FR4.4 so it documents the replica-set requirement and points at TML-2313 as the owner of both the API and dev-environment provisioning. - spec acceptance criteria: switch the Mongo facade-parity AC to db.orm.users.where(...).first() and the transaction line to a documentation-only requirement linking TML-2313. - spec Decisions: rewrite #1 to capture the emitter-driven root convention; add #10 recording that the transaction API is deferred end-to-end to TML-2313. - plan M3 task list: replace the db.transaction implementation task with the documentation task, mention binding-mirror connection inputs, and align the type-chain task and E2E task with the new accessor names.
wmadden
added a commit
that referenced
this pull request
May 4, 2026
…on API - spec FR4.1-4.4: standardise root accessors on lowercased plurals (db.orm.users / db.orm.posts) per the emitter output, drop the db.transaction(...) runtime requirement, and rewrite FR4.4 so it documents the replica-set requirement and points at TML-2313 as the owner of both the API and dev-environment provisioning. - spec acceptance criteria: switch the Mongo facade-parity AC to db.orm.users.where(...).first() and the transaction line to a documentation-only requirement linking TML-2313. - spec Decisions: rewrite #1 to capture the emitter-driven root convention; add #10 recording that the transaction API is deferred end-to-end to TML-2313. - plan M3 task list: replace the db.transaction implementation task with the documentation task, mention binding-mirror connection inputs, and align the type-chain task and E2E task with the new accessor names.
wmadden
added a commit
that referenced
this pull request
May 8, 2026
Introduce `buildCodec({id, encode, decode, encodeJson?, decodeJson?})`
in `framework-components/codec` so descriptor `factory` bodies and
ad-hoc test fixtures can construct narrow `Codec` instances without
reaching for the legacy `mkCodec(...)` / family-side codec factory.
The helper accepts strictly the runtime instance shape — `id` and the
four conversion methods — and refuses `targetTypes` / `traits` / `meta`
/ `paramsSchema` / `init` / `renderOutputType` at the type level so it
cannot serve as a back-door for the retired contributor surface (the
`@ts-expect-error` block in `test/build-codec.test.ts` pins this).
Sync `encode` / `decode` are auto promise-lifted (per ADR 204);
`encodeJson` / `decodeJson` default to identity when omitted so codecs
whose `TInput` is JSON-safe stay concise.
This unblocks the next M2 R4 commits, which retire `mkCodec`,
`defineCodecGroup`, and `defineCodecBundle` from `relational-core`
(decisions #4 / #9 / #10 in the unattended-decisions log).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.