Skip to content

music-history-db: Define deterministic PNW relevance rules #73

Description

@FarPointer

Finding

The specification lists regional relationship types but does not define which relationships confer PNW relevance, how temporal overlap is evaluated, or whether indirect links such as “member connection” make an event regional. Different reviewers and implementations could classify the same event differently.

Relevant sections: Pacific Northwest scope, entity-to-place relationships, unit tests, and PNW publication gates in tools/specs/music-history-db/KSER_Music_History_Technical_Implementation_Strategy.md.

Required decision

Define deterministic, explainable PNW classification semantics with controlled human overrides.

Acceptance criteria

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions