Every Spec id written in prose resolves

outcome

Refuse a prose reference to an absent Spec or entry, and report a prose reference that no declared relation backs.

rule line 21 · specs/validation/prose-mentions.sdp.md:21

The validator id is conformance/prose-mentions, in the conformance family; it reads the graph's Primitive nodes, edges and location table and nothing else.

rule line 22 · specs/validation/prose-mentions.sdp.md:22

The scanned text of a Spec is its narrative and every string value under its sections, except the gwt-vocabulary fence at behavior.exampleSpace and the gwt fences that are object entries of behavior.examples. The title is not scanned. Scan order is the narrative first, then the sections in the serialized graph's order, then entries in their authored order.

rule line 23 · specs/validation/prose-mentions.sdp.md:23

A mention starts at spec: where the character before it, if any, is not an ASCII letter, an ASCII digit, or -. A backslash before ASCII punctuation is read as that punctuation, as Markdown reads an escape. The token ends at ASCII whitespace, at one of the ASCII delimiters ` " ' ( ) [ ] { } < > |, or at a character outside ASCII that is whitespace, U+0085 included, punctuation other than connector punctuation, a symbol, or a space, line, or paragraph separator, so every dash, ellipsis, typographic quote, and arrow ends it. Every other character stays in the token, letters, combining marks, digits, connector punctuation, control characters other than whitespace, and format, private-use, and unassigned characters among them. Trailing . , ; : ! ? * _ ~ are then removed after the prefix, so a sentence, a list, or emphasis may end in an id. When nothing remains after spec:, there is no mention, so a bare prefix or a placeholder such as spec:<id> stays prose. The whole token goes to parseId, so an underscore, a slash, a comma, a control character, or any character outside ASCII that stays in it refuses the whole token as malformed; the token is never cut short to the valid id before that character, and a refused token counts toward no pair. A token equal to the scanning Spec's own id is skipped.

rule line 24 · specs/validation/prose-mentions.sdp.md:24

An open question's links entry is checked whole as a Spec id or entry address, under spec:model.open-question-fields, at path intent.openQuestions[<i>].links[<j>]. It uses the same malformed-token error; an otherwise parsed id outside the Spec namespace has reason expected spec namespace.

rule line 25 · specs/validation/prose-mentions.sdp.md:25

A token that fails parseId is an error with the message Mention "<token>" in "<spec>" at <path> is not a Spec id or entry address: <reason>, where <reason> is the grammar's refusal text with its Invalid ID "<token>": prefix stripped.

rule line 26 · specs/validation/prose-mentions.sdp.md:26

A token whose Spec part names no Primitive node is an error with the message Mention in "<spec>" at <path> points to missing target "<token>"., followed by the referential-integrity nearest-id suggestion when one is unique.

rule line 27 · specs/validation/prose-mentions.sdp.md:27

A token whose Spec exists and whose entry address names no key of that design or ui section, names description there, names a question key no open question of that Spec carries, names a rule key that Spec's behavior.ruleKeys does not carry, or names a term key that Spec's model.termKeys does not carry, is an error with the message Mention in "<spec>" at <path> points to missing entry "<section>.<key>" of "<target>".

rule line 28 · specs/validation/prose-mentions.sdp.md:28

Errors are reported once per scanning Spec, text path, and distinct token; subjectId is the scanning Spec, relatedId the token as written, path the text path, and file the Spec's carrier. The path is narrative or the section path in the mention audit's form, such as intent.openQuestions[0].question, behavior.rules[2], design.step2, or model.terms.<term>.

rule line 29 · specs/validation/prose-mentions.sdp.md:29

A target Spec that exists and shares no declared refines, dependsOn, constrainedBy, decidedBy, verifies, or supersedes edge with the scanning Spec, in either direction, is one warning per scanning Spec and target Spec pair, counting every location where any token names that Spec or one of its entries. The message is Mention of "<target>" in "<spec>" at <n> locations, first at <path>, with no declared relation between them; informative only. Declare the relation that fits, or leave the mention as prose and let the warning stand when none does. with <n> the count of distinct paths, written 1 location when it is one, and <path> the first in scan order; subjectId is the scanning Spec, relatedId the target Spec id, path that first path, and file the Spec's carrier. An address on the scanning Spec's own id is checked for its entry and never warned.

rule line 30 · specs/validation/prose-mentions.sdp.md:30

A mention error or pair warning carries line when the location table records the corresponding text path; behavior.rules[<i>] uses rule[<i>], behavior.flows[<i>] uses flow[<i>], an open question's text uses question[<i>], a question field uses question[<i>].<field>, with each question link using the links row, and a Model term's definition, at model.terms.<term>, uses term[<i>]. Entries of Rule, Workflow and Contract use the same behavior paths as entries of Behavior. An unrecorded line is omitted.

rule line 31 · specs/validation/prose-mentions.sdp.md:31

The warning is honest when it stands: the six relations are typed, a mention that none of them describes is lawful prose, and no author declares a relation to silence the report. Warnings never fail sdp validate; the mention audit recipe reports every location of every pair as data and stays the way to list them at once.

11 unkeyed rules.

Verifier bindings

• test:protocol.entry-locations · anchored · test anchor binding present · test/entry-locations.test.ts:14

  External run evidence from test/entry-locations.test.ts

  Test anchors: test:protocol.entry-locations. Specs verified by those bindings: spec:extraction.entry-locations, spec:validation.prose-mentions.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 391 · Branch: cursor/media-plan-and-articles-09b1 · Commit: 076cd4f1f85640d8236e5cca1bffffa68ab79a33 · Start: 2026-10-31T15:32:20.471Z · Stop: 2026-10-31T15:34:02.073Z

  Name	Suite	Result	Duration
  locates each Gherkin relation at its own tag and defaults at the Scenario line	entry locations	passed	6.91 ms
  records Markdown Design, UI, keyed and unkeyed questions at their first item lines	entry locations	passed	11.12 ms
  locates Markdown question fields, rules, flows and declared relation targets	entry locations	passed	3.12 ms
  records TypeScript property lines through transparent wrappers	entry locations	passed	22.49 ms
  locates TypeScript string questions and omits properties dropped as non-static	entry locations	passed	6.06 ms
  locates Gherkin rules and relations while keeping open questions outside its grammar	entry locations	passed	4.41 ms
  sorts Specs and entries in code-unit order and serializes reversed rows identically	entry locations	passed	4.36 ms
  keeps Primitive and Pack nodes line-free when an edit above entries moves their lines	entry locations	passed	6.24 ms
  compares carrier parity on nodes and edges while locations differ	entry locations	passed	7 ms
  serializes an empty table for entries without recorded carrier lines	entry locations	passed	3.99 ms
  extracts the location table byte-identically twice	entry locations	passed	3.74 ms
  locates errors and warnings in behavior Behavior rule: entries	prose mention finding lines	passed	20.91 ms
  locates errors and warnings in behavior Behavior flow: entries	prose mention finding lines	passed	2.84 ms
  locates errors and warnings in rule Rule entries	prose mention finding lines	passed	2.29 ms
  locates errors and warnings in workflow Workflow entries	prose mention finding lines	passed	2.16 ms
  locates errors and warnings in workflow Workflow rule: entries	prose mention finding lines	passed	2.7 ms
  locates errors and warnings in contract Contract entries	prose mention finding lines	passed	1.89 ms
  locates question text, fields and links and omits an unrecorded line	prose mention finding lines	passed	1.69 ms

• test:protocol.prose-mentions · verifies prose-mention resolution and the unbacked-pair warning · anchored · test anchor binding present · test/validators.test.ts:1321

  External run evidence from test/validators.test.ts

  Test anchors: test:protocol.prose-mentions. Specs verified by those bindings: spec:validation.prose-mentions.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 391 · Branch: cursor/media-plan-and-articles-09b1 · Commit: 076cd4f1f85640d8236e5cca1bffffa68ab79a33 · Start: 2026-10-31T15:32:20.471Z · Stop: 2026-10-31T15:34:02.073Z

  Name	Suite	Result	Duration
  reports referential integrity across relations, pack members, modelRefs, and bindings	graph validators	passed	6.14 ms
  offers a "did you mean" suggestion only when one nearest id is unambiguous (L2)	graph validators	passed	1.2 ms
  reports duplicate node ids — the graph backstop behind the extractor's per-site errors	graph validators	passed	1.17 ms
  keeps the claim taxonomy uncollapsed: a declared satisfies edge violates the edge contract	graph validators	passed	0.53 ms
  admits no inferred edge on the ratified edge types: the claim ships designed-in and empty	graph validators	passed	0.68 ms
  rejects a node claim its nodeType never carries	graph validators	passed	0.4 ms
  rejects wrong-kind endpoints on the kind-typed relations — constrainedBy, decidedBy, supersedes	graph validators	passed	0.89 ms
  accepts the valid kind-typed relation shapes — rule/constraint bounds, a decision decider, decision supersedes decision	graph validators	passed	0.58 ms
  fails the anchors-resolve ready clause when a binding edge has no binding node behind it	graph validators	passed	0.68 ms
  reports a readiness-floor failure with the spec id, stated rung, and failing clause	graph validators	passed	0.7 ms
  surfaces the gap only while no verifier resolves — a derived fact silences it, a stated one never does	graph validators	passed	1.16 ms
  exempts decision-kind Specs from the gap signal while other kinds still warn	graph validators	passed	0.49 ms
  never lets an anchored verifies edge from a non-Anchor source enable an example — fail closed	graph validators	passed	0.99 ms
  refuses an oracle Anchor as the test binding for a direct verifier	graph validators	passed	2.54 ms
  refuses an oracle Anchor as the test binding for a example verifier	graph validators	passed	1.03 ms
  confers satisfies only when the duplicate target's first node is a Primitive	graph validators	passed	1.19 ms
  confers direct verifies only when the duplicate target's first node is a Primitive	graph validators	passed	1.32 ms
  confers example verifies only when the duplicate target's first node is a Primitive	graph validators	passed	2.59 ms
  rejects stated delivery facts the graph does not earn — derived, never authored	graph validators	passed	0.37 ms
  rejects an omitted delivery fact the graph's resolving bindings derive	graph validators	passed	0.46 ms
  fails closed on unratified descriptor values — a conformance error, never a crash or a silent floor skip	graph validators	passed	0.37 ms
  returns a valid empty aggregate report without throwing	graph validators	passed	0.22 ms
  composes cleanly over a valid non-empty model with bindings, a pack, and a model-kind modelRef	graph validators	passed	0.72 ms
  reports nothing when every listed member has its one edge and every edge is listed	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.3 ms
  names a listed member with no belongsTo edge into the pack	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.3 ms
  names a belongsTo edge whose source the members do not list	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.23 ms
  names a listed member that is no Spec when no edge carries it, and defers to the edge contract when one does	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.62 ms
  leaves an absent listed member whose edge dangles to referential integrity	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.53 ms
  leaves an unlisted belongsTo edge from an absent source to referential integrity	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.4 ms
  leaves an unlisted belongsTo edge from a CodeNode to the edge contract	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.33 ms
  names both membership counts when one listed member has two belongsTo edges	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.29 ms
  keeps the duplicate rule: a repeated member is named once, in authored order, with its count	conformance/pack-coherence — the members list and the belongsTo edges agree	passed	0.38 ms
  passes on its contract row (anchored, Anchor → Primitive) and confers no delivery fact	the models edge — the oracle anchor's contract row	passed	0.42 ms
  rejects a declared claim on a models edge — the claim taxonomy is never collapsed	the models edge — the oracle anchor's contract row	passed	0.36 ms
  rejects an oracle target that does not own a behavior example space	the models edge — the oracle anchor's contract row	passed	0.34 ms
  rejects competing oracle anchors for one parent example space	the models edge — the oracle anchor's contract row	passed	0.36 ms
  rejects a models edge whose Anchor does not use the oracle namespace	the models edge — the oracle anchor's contract row	passed	0.39 ms
  accepts a rule-kind oracle target when the rule owns an example space	the models edge — the oracle anchor's contract row	passed	0.25 ms
  rejects a models edge from a non-Anchor source — the endpoints are typed	the models edge — the oracle anchor's contract row	passed	0.24 ms
  flags a dangling models target through referential integrity, like every edge	the models edge — the oracle anchor's contract row	passed	0.32 ms
  refuses a malformed token with the id grammar's own reason	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.69 ms
  refuses a missing target and suggests the unique nearest id	conformance/prose-mentions — prose mentions and their entry addresses	passed	1.63 ms
  refuses a missing target without a suggestion on a tie, once per path and distinct token	conformance/prose-mentions — prose mentions and their entry addresses	passed	1.57 ms
  refuses an entry address whose key the target's section does not hold	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.62 ms
  never resolves an address to a section's description	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.46 ms
  resolves to an open question that carries the key, beside unkeyed and prose questions	conformance/prose-mentions — prose mentions and their entry addresses > a question address	passed	6.21 ms
  fails every mention of an old address once its key is renamed	conformance/prose-mentions — prose mentions and their entry addresses > a question address	passed	0.56 ms
  finds no entry on a Spec whose questions carry no key, or that has none	conformance/prose-mentions — prose mentions and their entry addresses > a question address	passed	0.44 ms
  reads question keys only, never the Design or UI keys of the Spec	conformance/prose-mentions — prose mentions and their entry addresses > a question address	passed	0.31 ms
  treats description as an ordinary question key	conformance/prose-mentions — prose mentions and their entry addresses > a question address	passed	0.4 ms
  refuses a question address with a key off the grammar by the id grammar's reason	conformance/prose-mentions — prose mentions and their entry addresses > a question address	passed	0.25 ms
  checks a self-address for its entry and never warns on it	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.39 ms
  warns once for a pair across three locations, first in scan order	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.5 ms
  writes one location in the singular	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.28 ms
  lets a declared relation in the reverse direction back the mention	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.19 ms
  counts an address mention toward its pair, resolved or not	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.3 ms
  never scans the gwt and gwt-vocabulary fences, and skips them by position only	conformance/prose-mentions — prose mentions and their entry addresses	passed	2.96 ms
  keeps authored order inside an object nested in design, so a nested description is not read first	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.27 ms
  keeps authored order inside an object nested in ui, so a nested description is not read first	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.19 ms
  scans arrays nested in behavior examples, as the mention audit does	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.25 ms
  still warns on a pair joined only by an edge whose claim is anchored	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.34 ms
  still warns on a pair joined only by an edge whose claim is inferred	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  resolves an address only to an own key, never an inherited one	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.22 ms
  puts the pair warning's first path in authored entry order, with description first	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.3 ms
  puts the pair warning's first path in a description authored after another mentioning entry, with description first	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  suggests the nearest Spec id for a missing target written as an address	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.22 ms
  reads the whole token through an underscore and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.26 ms
  reads the whole token through an underscore and a letter and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.18 ms
  reads the whole token through a slash and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.18 ms
  reads the whole token through a slash and a letter and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the whole token through a comma and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the whole token through a comma and a letter and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the whole token through a letter outside ASCII and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the whole token through an escaped underscore and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the whole token through a combining mark and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.67 ms
  reads the whole token through a combining mark after an entry key and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.24 ms
  reads the whole token through a zero-width space and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the whole token through fullwidth connector punctuation and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the whole token through a NUL and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the whole token through an escape character and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the whole token through a delete character and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.2 ms
  reads the whole token through a C1 control character and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the whole token through a hyphenated entry key and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.19 ms
  reads the whole token through an entry suffix with no key and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the whole token through an entry suffix outside design, ui, question, and rule and refuses it, never the existing prefix	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: a sentence dot	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.2 ms
  reads the clean id through Markdown punctuation: a comma	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the clean id through Markdown punctuation: a colon	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.28 ms
  reads the clean id through Markdown punctuation: a closing parenthesis	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.19 ms
  reads the clean id through Markdown punctuation: bold	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: emphasis	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.13 ms
  reads the clean id through Markdown punctuation: strikethrough	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.13 ms
  reads the clean id through Markdown punctuation: backticks	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: ASCII double quotes	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the clean id through Markdown punctuation: ASCII single quotes	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the clean id through Markdown punctuation: typographic double quotes	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the clean id through Markdown punctuation: typographic single quotes	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: an em dash	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: an en dash	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the clean id through Markdown punctuation: an ellipsis	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads the clean id through Markdown punctuation: an escaped star	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the clean id through Markdown punctuation: an escaped exclamation mark	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.16 ms
  reads the clean id through Markdown punctuation: U+0085	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: a no-break space	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: a tab	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.15 ms
  reads the clean id through Markdown punctuation: an arrow	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.17 ms
  reads a placeholder or a bare prefix as prose, not a mention	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.36 ms
  strips a sentence-final dot from a token	conformance/prose-mentions — prose mentions and their entry addresses	passed	0.25 ms

Requirement drawing

• Declared verifying examples: no declared verifying example.

Decisions

• A Spec id written in prose is a checked mention

  A Spec id in narrative or section text, outside gwt and gwt-vocabulary fences, is a mention. A mention that does not resolve is a conformance error. A mention of another Spec that shares no declared relation with the mentioning Spec, in either direction, is one warning per mentioning Spec and target Spec pair, whatever the number of locations; an address on the mentioning Spec's own id is checked for its entry and never warned. An entry address is a Spec id followed by #, the section name design, ui, question, rule, or term, a dot, and the entry's lower-camel ASCII key, as in spec:<id>#design.<key> or spec:<id>#question.<key>. A design or ui address resolves when the Spec exists and that section holds the key as its own key, other than description; a question address resolves when the Spec exists and one of its open questions carries that key; a term address resolves when the Spec exists and one of its Model terms carries that key. The # sub-part is reserved for the entry address in every namespace: a Spec's own id, a relation target, a Pack member or model reference, an anchor id or target, and the specId and ref builders all refuse it. A mention mints no edge, and the reader gains no join.

• component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol

  Uses

  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.notation · the leaf step codec · src/notation/slots.ts:261 · layer domain · context protocol
• component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:72 · layer domain · context protocol

  Uses

  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol
  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.notation · the leaf step codec · src/notation/slots.ts:261 · layer domain · context protocol
• impl:protocol.entry-address-resolution · resolves entry addresses for prose validation and citation readers · src/graph/entry-address.ts:6

  Component: component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol

  Uses

  None.

• impl:protocol.prose-mentions · checks that prose mentions resolve and warns once per unbacked Spec pair · src/validate/validators.ts:1370

  Component: component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:72 · layer domain · context protocol

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.