Build NDF knowledge compiler format 0.2 - #1
Merged
Conversation
added 12 commits
August 10, 2026 15:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Authority and compatibility
Markdown, ASL, source, tests, and evidence remain Git-tracked sources of truth. SQLite is derived and untracked. PTO-SPEC ASL remains authoritative; the adapter only normalizes its NDF regions. Format, IR, JSON output, CLI spelling, and plugin API remain experimental.
Verification
Follow-up
After merge and CI success, tag the merged commit as v0.1.0. PTO-SPEC parity and pinning must consume that exact release commit.