-
Notifications
You must be signed in to change notification settings - Fork 0
feat: sigils #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
feat: sigils #8
Conversation
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
…itions - Change sigil identifiers from dash-based (link-v1) to @-based versioning (link@1) - Add comprehensive TypeScript type definitions for all sigil types - Update all examples and documentation to use new naming convention - Add TypeScript version support guidance for implementations
- Rename link@1 to query@1 and alias@1 to cursor@1 for clarity - Add detailed comparison of query vs cursor write behavior - Query sigils replace themselves when written to - Cursor sigils redirect writes to target facts - Update all examples and documentation to use new names
Updates sigil RFC to reference new schema query capabilities for automatic sigil resolution and graph traversal operations.
Changes spread@1 to merge@1 with new sources array API instead of separate source and additions fields. Supports merging multiple sources in order with later sources taking precedence.
jsantell
reviewed
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
seefeldb
reviewed
Jun 18, 2025
Gozala
commented
Jun 18, 2025
seefeldb
reviewed
Jun 18, 2025
seefeldb
reviewed
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Gozala
commented
Jun 18, 2025
Replace the previous multi-sigil approach with a simpler foundation based on two fundamental reference types: - Immutable references (by value): Use IPLD links for content that never changes with cryptographic integrity guarantees - Mutable references (by address): Use embed sigils for facts that can be updated over time with automatic change propagation Update embed sigil with new field names (the->accept, of->source, at->path, from->space) and add replace field to control write behavior. Remove mount sigil in favor of embed with replace="source". Restructure blob/file sigils to use either reference type. Rewrite charm sigil to use TypeScript modules instead of spell system.
seefeldb
reviewed
Jun 19, 2025
seefeldb
reviewed
Jun 19, 2025
seefeldb
reviewed
Jun 19, 2025
seefeldb
reviewed
Jun 19, 2025
seefeldb
reviewed
Jun 19, 2025
seefeldb
reviewed
Jun 19, 2025
- Add inline references for embedded data using IPLD data model - Split binary content into separate blob and file reference types - Add dedicated section explaining IPLD data model and DAG-JSON usage - Reorganize document structure for better clarity - Update examples and TypeScript definitions throughout - Remove implementation-specific sections to focus on protocol spec
seefeldb
approved these changes
Jun 20, 2025
seefeldb
reviewed
Jun 20, 2025
|
We call the path parameter a JSONPath, but it isn't a JSONPath. |
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.
No description provided.