Skip to content

spec: 3 docs updates (extensions.collection, broader playback enums, internal-ref scrub)#18

Merged
tymofiy merged 3 commits into
mainfrom
dev
May 26, 2026
Merged

spec: 3 docs updates (extensions.collection, broader playback enums, internal-ref scrub)#18
tymofiy merged 3 commits into
mainfrom
dev

Conversation

@tymofiy
Copy link
Copy Markdown
Owner

@tymofiy tymofiy commented May 26, 2026

Summary

Three docs-only commits land in the public KP:1 spec. All currently sit on dev; this PR fast-forwards main so the Nova workspace's submodule pointer (which references the tip of these changes) is reachable from origin/main.

  • ae1a946docs(extensions): add extensions.collection with item_kind taxonomy — documents the extensions.collection block (name, id, role hub/member/standalone) and the 9-value item_kind controlled vocabulary the viewer's inventory dashboard buckets packs by.
  • 29834cadocs(playback): broaden purpose + domain_lens enums for non-compliance use cases — adds six new purpose values (pre_meeting, hiring, partnership, competitive_intel, sales_prep, appreciation) and six domain_lens values; both enums marked extensible with fallback to orientation/general.
  • c6c6167docs(spec): scrub internal references from public spec — drops the "Nova" codename and the "kp-forge / kp-packs / kp-viewer" parenthetical from public docs (only kp itself is public).

Why now

Nova's submodule pin for repos/kp is at ae1a946, which until this push existed only locally + on dev. A clean Nova clone with --recursive would fail to fetch the spec pointer. Merging here makes it reachable from origin/main (the canonical reference).

Test plan

  • CI passes (docs-only — no normative content changes)
  • After merge, git -C repos/kp branch -r --contains ae1a946 shows origin/main

tymofiy and others added 3 commits May 18, 2026 22:17
Pre-production review found leakage in the public KP:1 specification
repo. The "Nova" codename is internal-only, and EXTENSIONS.md
described kp-forge / kp-packs / kp-viewer as "the public" reference
implementation, which is factually wrong (only kp is public today).

- EXTENSIONS.md: drop the "(the public kp-forge, kp-packs, and
  kp-viewer repositories)" parenthetical; the catalogue still
  describes producer-defined extensions in active use across the
  reference implementation, just without naming the private repos.

- DEFINITIONS.md, CHANGELOG.md, SPEC.md: replace "Nova ecosystem"
  and "Nova IDs" prose with neutral phrasing ("the reference
  implementation", "canonical entity IDs"). No normative content
  change — these were intent annotations.

Tool names (kp-forge, kp-packs, kp-viewer) are retained as
descriptive references; only the workspace codename and the
factually-wrong "public" attribution were scrubbed.

Co-Authored-By: Claude <noreply@anthropic.com>
…e use cases

Add six new purpose values (pre_meeting, hiring, partnership, competitive_intel,
sales_prep, appreciation) and six new domain_lens values (hr_reviewer,
partner_evaluator, competitor_analyst, admirer, meeting_host, salesperson) to
PLAYBACK.md section 3.

Mark both enums as extensible in new section 3.3: renderers MUST fall back to
orientation / general for unknown values, so newer pack profiles don't crash
older renderers and new values can ship via spec updates without coordinated
viewer rebuilds.

Refs: sessions/2026-05-19-research-framing-broadening/SESSION.md

Co-Authored-By: Claude <noreply@anthropic.com>
Collections P1 (2026-05-24). Documents the extensions.collection
block on PACK.yaml: name, id, role (hub/member/standalone) plus the
new item_kind / item_role inventory taxonomy.

item_kind is a 9-value controlled vocabulary (spine, subcollection,
object, person, place, period, event, document, narrative) that the
viewer's inventory dashboard uses to bucket packs into sections.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 26, 2026 17:55
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Docs-only PR that fast-forwards main to include recent public KP:1 spec documentation updates (extensions catalogue expansion, PLAYBACK enum broadening, and scrubbing “Nova”/internal phrasing) so downstream consumers can reference the commit via origin/main.

Changes:

  • Document extensions.collection and its controlled item_kind taxonomy in EXTENSIONS.md.
  • Expand and explicitly document AudienceProfile.purpose and AudienceProfile.domain_lens enums (with extensibility rules) in PLAYBACK.md.
  • Replace remaining “Nova ecosystem/IDs” phrasing with “reference implementation” / “canonical entity IDs” in core spec text and changelog.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
spec/SPEC.md Updates deprecated entities.md guidance wording to “canonical entity IDs”.
spec/PLAYBACK.md Documents expanded purpose/domain_lens enums and extensibility behavior.
spec/EXTENSIONS.md Adds extensions.collection extension documentation and inventory taxonomy.
spec/DEFINITIONS.md Replaces “Nova ecosystem” phrasing with “reference implementation”.
spec/CHANGELOG.md Aligns changelog wording with “reference implementation” and “canonical entity IDs”.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread spec/PLAYBACK.md
Comment on lines +83 to +85
The `domain_lens` field names the listener's role-frame. Original five
values (`buyer`, `consigner`, `compliance`, `journalist`, `collector`,
`general`) are joined by six use-case-named values added 2026-05-19:
@tymofiy tymofiy merged commit 95fa99b into main May 26, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants