Repository navigation
[3d] Add token commands with parity tests #443
Description
Part of Phase 3 (#426) of the data layer plan.
Token commands (gloss, approve, payload dedupe and merge) with the approval rule, plus parity tests. Sets the pattern for 3e to 3i.
Done when: its commands pass their parity tests.
Depends on: 3b (#441), 3c (#442).
From the plan
API
| Call | Kind | Request | Response | Replaces today | Issue |
|---|---|---|---|---|---|
Commands by intent (writeGloss, approveAnalysisForToken, createPhrase, ...) |
command | session, intent arguments | ChangeSet, plus touched pool buckets |
Dispatch plus whole-draft saveDraft |
3d to 3i |
Decisions
| Question | Decision | From |
|---|---|---|
| Approval rule (one approved link per token or segment) | Enforced in the domain layer. Loads and PT9 import saves keep reporting breaches at the storage boundary; the breach report on project Save is removed in 4c | J |
Metadata
Metadata
Assignees
Labels
No labels
Activity
Add token commands with parity tests (#443)
Add token commands with parity tests (#443)
Add token commands with parity tests (#443)
Add token commands with parity tests (#443)
Add token commands with parity tests (#443)
Add token commands with parity tests (#443)
Add token commands with parity tests (#443)
Add token commands with parity tests (#488)
[claude] Add morpheme commands with parity tests (#497)