T-SI3K-constraint-entity
Status: closed/wontdo · Impact: medium · Complexity: medium
Constraint (CO) has sat planned in D-ORMG; the donor’s six live instances
prove the shape. Stand it up gated on its consumer: ensure-ready / task-work
injecting in-scope constraints into implementation prompts
(D-3PDM-cross-project-data-model-adoption P6).
Proposed
Section titled “Proposed”- Package
plugin/lib/model/entities/constraint/:category ∈ technical | regulatory | business | contractual | stylistic,severity ∈ hard | soft,source(provenance),scope= capability wikilinks (empty = global); incrementingCO-NNNNids; create/preview-id ops; registry + identifier rows. - The named consumer ships with it: readiness/prompt assembly includes the
constraints whose
scopecovers the task’s capabilities, plus globals. - D-ORMG Constraint row flips
planned → activeon ship.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1:
sdlc constraint createmints a valid instance; audit validates it. - AC-2:
scopewikilinks are validated against capabilities in audit. - AC-3: the consumer ships in the same milestone: task readiness/prompt assembly surfaces in-scope constraints.
- AC-4: the D-ORMG Constraint row is
active; at least one real instance exists in the corpus.
Out of scope
Section titled “Out of scope”- Redefining the Standard/Constraint boundary (Standard globs files via
applies_to.paths; Constraint scopes entities — both stand). - Hard enforcement gates driven by constraints.
Dependencies
Section titled “Dependencies”- Activation-gated: starts when the ensure-ready consumer is scheduled in the
same milestone (D-ORMG activation rule). No hard
depends_ontoday.
Discovery context
Section titled “Discovery context”D-3PDM-cross-project-data-model-adoptionP6: the donor Constraint had 6 live instances (its own storage rule among them) — modest but real usage; shape confirmed nearly field-for-field against the planned D-ORMG row.