Skip to content

docs: Update serialization spec#3085

Open
aborgna-q wants to merge 3 commits into
mainfrom
ab/spec-envelopes
Open

docs: Update serialization spec#3085
aborgna-q wants to merge 3 commits into
mainfrom
ab/spec-envelopes

Conversation

@aborgna-q

@aborgna-q aborgna-q commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Adds an updated short overview of the serialization steps and formats, to replace the deprecated JSON format description.

This doesn't get into the details of the different hugr-model formats, we should add that as sub-pages in a follow up.

Includes some references to migration logic, including the changes is #3080.

Closes #2937

@aborgna-q aborgna-q requested a review from a team as a code owner June 2, 2026 09:57
@aborgna-q aborgna-q requested a review from croyzor June 2, 2026 09:57
Comment thread specification/serialization.md Outdated
- Reasonably small sized files/payloads.
- Ability to send over wire. Nexus will need to do things like:
- Reasonably small files and payloads.
- Ability to send over the wire. Nexus will need to do things like:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

indent these pls

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Cleaned up the list. We don't really need the "nexus wants" subpoints.

Comment thread specification/serialization.md Outdated
## The `hugr-model` intermediate serialization format

`hugr-model` is the serialization-oriented representation of HUGR. It sits
between the runtime graph implementation and the concrete wire formats.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this leaves me with a feeling that i don't know what "runtime graph implementation" or "concrete wire formats" mean

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Is this better?

hugr-model is the serialization-oriented representation of HUGR. It sits
between the in-memory HUGR objects and the serialized formats.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

yes, thanks!

@aborgna-q aborgna-q requested a review from croyzor June 2, 2026 14:36
The AST format is the unresolved, text-like representation used by the parser
and printer. It keeps names and syntactic structure close to the textual format.
Resolving the AST produces the table format by assigning IDs, checking scoped
names, and creating implicit imports where required.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

it feels like there's a missing link between the capnproto/sexp payloads and the table/ast formats. They're the same two things, no?

@aborgna-q aborgna-q requested review from croyzor and removed request for croyzor June 3, 2026 14:16
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.

[Spec]: Replace legacy JSON definition with envelope description

2 participants