Repository navigation
History and recipes APIs at services level, flow storage encapsulated - #74
Merged
Merged
Conversation
client.history(projectId): connected docs, graph-ordered timelines, deltas, models, and suggestions (change requests) with their lifecycle. The bimterop layout is stated once, privately, so the hidden-folder move and the platform-level API swap stay internal. Appends re-check the head and refuse with StaleHistoryError when it moved; the remaining race is the documented phase-2 server-side append. client.recipes: registry and runner for recipes, scripts that write suggestions in a native app language, declared by manifest (to, inputs, runtime, settingsSchema, self-documenting rules) plus one run function. Consumer example in core/examples/history.ts, indexed for the AI docs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
What
client.history(projectId): a project's connected documents (Revit, AutoCAD...), their version timelines ordered by the parent graph, deltas and full models, and change requests (suggestions) with their full lifecycle (queue, read payload, resolve).client.recipes: the registry and runner for recipes, scripts that write suggestions in a native app's own language, declared by a manifest (to,inputs,runtime: browser|cloud,settingsSchema, a self-documenting rules table) plus onerunfunction. Consumer example incore/examples/history.ts, indexed for the AI quickstart docs.Why shaped like this
bimteropfolders,revitflow_history.json,revitflow_ops.json, hidden deltas, schemarevitflow/ops@1). Wire format byte-compatible with the plugins; zero migration. When the layout moves into hidden project storage, or the platform grows the first-class history API (agreed phase 2), onlysrc/core/history.tschanges.synctakesexpectedLatestGuid, re-reads right before writing and refuses withStaleHistoryErrorwhen the head moved. Closing it needs the server-side append; documented in the module header as phase 2, as discussed.Not here on purpose
The .frag payload builder (OperationBuilder) stays out: it belongs in the fragments toolkit per flow's STATE.md. The platform-level catalog (recipes as published items) sits on top of the same manifest later.
Merging publishes to npm via the release workflow (changeset included, minor).
🤖 Generated with Claude Code