docs: the 0.16 wave for readers — the executor block, deploying through a forge, provenance on the cards - #359
Merged
Merged
Conversation
…gh a forge, provenance on the cards, ops that touch the estate, the carved entity on the chant side README: render provenance on Helm in the opening line; a Deploy executors section under .behold.json. docs/using/acting: Deploying through a forge. docs/using/reading-the-graph: What was deployed, from where (release chip + pane, the helm deployed-from row, the carved mark) and Ops that touch the estate. docs/using/carve: the carved entity on the chant side; the stale 'not here yet' (chant#1636 shipped) replaced with what is actually not here. docs/using/agents: the provenance attrs and the executor routes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SfqZdPzrxxkCJkHgzzMacq
lex00
added a commit
that referenced
this pull request
Sep 2, 2026
…roven on GitHub (#361) Since 0.16.0: version-2 carve manifests read and the emitted file joins a node graphed from src/ (#352 — 0.16.0 read every fresh 0.54 carve as nothing carved); the follow stream can die honestly and a restarted behold re-adopts the run (#350, #165 §6); a declaration outside the project is dropped and named, not drawn (#354, chant#2058); the executor contract against the real forge — workflows read from the repository root, no other env's workflow ever stands in, a lost run re-adoptable, the env read off the YAML chant names it in (#355, #358, chant#2060); the helm lane asserts the ledger's render identity reaches the card (#360); docs for the wave (#353, #359); every vitest run keeps .vitest-last.json (#351). Claude-Session: https://claude.ai/code/session_01SfqZdPzrxxkCJkHgzzMacq Co-authored-by: Claude Fable 5.1 <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.
Docs only; the site builds (10 pages). README gains render provenance in the opening line and a Deploy executors section under
.behold.json. The acting guide gains Deploying through a forge. The graph-reading guide gains what was deployed from where (the release chip and pane, the Helm deployed-from row, the carved mark) and Ops that touch the estate. The carve guide describes the carved entity on the chant side and replaces its stale not-here-yet section. The agents guide names the provenance attrs and the executor routes.🤖 Generated with Claude Code
https://claude.ai/code/session_01SfqZdPzrxxkCJkHgzzMacq