Skip to content

k9: fix pre-existing "Validate K9 contracts" failures (3 errors, gates every PR) #59

Description

@hyperpolymath

The Validate K9 contracts check fails on main (pre-existing — surfaced on #56, which was merged past it). 3 errors:

  • coordination.k9 and session/custom-checks.k9: security_level = "data-only" is rejected (Invalid security level 'data-only'. Must be one of: kennel, yard, hunt). Both already carry leash = "Kennel". Fix to match the passing .machine_readable/self-validating/*.k9.ncl pattern: leash = 'Kennel (Nickel enum) + trust_level = "data-only", and drop the invalid security_level field.
  • container/deploy.k9.ncl: Pedigree block missing 'name' — the file exports pedigree = component_pedigree (a let-indirection) rather than the literal pedigree = { name = … } block the validator inspects. It's also an unfilled RSR template stub ({{SERVICE_NAME}}, {{VERSION}}, {{PORT}}, {{REGISTRY}}, {{PROJECT_NAME}}) describing a Hunt-level deployment component. For a docs-only coordinator (per OQ-001 / resolve OQ-001 (A): coordinator + verification host — drop redundant src/ ABI/FFI scaffold #56), this is template residue — either inline the pedigree literal + fill the tokens, or drop container/deploy.k9.ncl. Overlaps OQ-002 (template-placeholder residue).

Small fixes; they unblock the K9 gate for all future nextgen-typing PRs.

https://claude.ai/code/session_01GJatEm2TVFSTBEkKXmserJ

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions