Skip to content

Pre-existing: WF11 tagged/tagged-in HDC drift-claim LINK silently rejected by the declaration gate #52

Description

@MSD21091969

Surfaced (not caused) by the #50/#51 adversarial review — two independent lenses flagged it.

The HDC drift-claim annotation path emits a LINK with ports tagged/tagged-in under WF11, but ontology v4.0.1's WF11 declares only synced-via/sync-target (primary; no additional pairs). Since the T=171 declaration gate (linkPairDeclared), any such LINK is rejected with "port pair (tagged, tagged-in) not declared for WF11" — silently from the emitter's perspective if errors aren't surfaced. tagged/tagged-in carry authored storage color in declared_pairs_by_wf (also not attached to WF11 there — the authored rows put tagging under WF12-adjacent semantics).

Pre-existing: this is the declaration gate, unchanged by #51; the color gate never sees the pair. The ports ARE covered by DefaultPortColors (storage), so the fix is grammar-side, not color-side.

Fix options (ontology round + possibly kernel):

  1. Declare tagged/tagged-in as a WF11 additional_port_pairs entry (grammar_fragment → next collected ontology round), or
  2. Re-home the HDC drift-claim emission to the WF/pair the grammar intends (kernel-side emitter change), or
  3. Retire the emission if the annotation path is dead code.

Needs a live-fold readback first: do any historical logs carry these relations (grandfathered), and does the current HDC path still attempt the emission?

Refs: #50, #51 (review findings), ffs0#140 (t249 anchor).

authored-by: agent:claude-cowork.hp-z440 / session:sam.z440-cowork-workspace / color-gate-data-driven

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions