Skip to content

Release the complete Taproot knowledge layer - #2

Merged
kcsfelty merged 6 commits into
mainfrom
feat/core-knowledge-layer
Jul 20, 2026
Merged

Release the complete Taproot knowledge layer#2
kcsfelty merged 6 commits into
mainfrom
feat/core-knowledge-layer

Conversation

@kcsfelty

@kcsfelty kcsfelty commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

  • implement the complete Taproot Item/Property knowledge layer, including canonical Wikibase-shaped entities, revisions, lifecycle, attribution/audit history, search, RDF projection, migration, integrity, and repair
  • atomically coordinate canonical entities, immutable revisions, audit events, search terms, RDF ownership, and Diamond quad patches in one D1 batch
  • replace the local Diamond dependency with the public @gnolith/diamond@^0.3.2 release
  • prepare @gnolith/taproot@0.1.0 as a public MIT package with project-specific documentation, governance, support, templates, pinned CI/security workflows, and an OIDC-only release workflow

Correctness and integration evidence

  • 19 tests pass, including 12 Workerd/D1 integration and example scenarios
  • rollback injection proves canonical JSON, revisions, audit events, terms, RDF ownership, and Diamond quads fail atomically
  • concurrent same-revision edits permit exactly one writer
  • migration, malformed input, empty commands, size limits, shared RDF nodes, integrity inspection, repair, redirects, and audit chains are covered
  • Taproot writes are queried through Diamond SPARQL on the same D1 database
  • packed tarball installs into a completely fresh temporary project with registry Diamond and passes a public-API D1/SPARQL smoke test

Release-quality validation

pm run check

  • coverage: 78.42% statements, 72.72% branches, 72.44% functions, 78.42% lines with enforced thresholds
  • production dependency license allowlist passes

pm audit reports zero vulnerabilities

pm audit signatures verifies 769 registry signatures and 85 attestations

  • release metadata and the 48-file tarball pass
    pm run release:check -- v0.1.0

Release and security impact

The repository remains private and this PR remains draft until every new CI/security check passes. After merge, the repository will be made public and protected before the initial npm publication. npm trusted publishing requires the package to exist first, so the initial

@kcsfelty kcsfelty changed the title Implement the Taproot knowledge layer Complete the Taproot knowledge layer Jul 20, 2026
@kcsfelty kcsfelty changed the title Complete the Taproot knowledge layer Release the complete Taproot knowledge layer Jul 20, 2026
@kcsfelty kcsfelty closed this Jul 20, 2026
@kcsfelty kcsfelty reopened this Jul 20, 2026
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@kcsfelty
kcsfelty marked this pull request as ready for review July 20, 2026 23:58
@kcsfelty
kcsfelty merged commit c62fc8a into main Jul 20, 2026
9 checks passed
@kcsfelty
kcsfelty deleted the feat/core-knowledge-layer branch July 20, 2026 23:58
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