docs(core): left-of-line page — captures, side-by-side, static snapshot (#1104) - #1124
Draft
lex00 wants to merge 7 commits into
Draft
docs(core): left-of-line page — captures, side-by-side, static snapshot (#1104)#1124lex00 wants to merge 7 commits into
lex00 wants to merge 7 commits into
Conversation
…t, committed captures (#1084) A CRUD items API (DynamoDB + Lambda + HTTP API + implied IAM) expressed twice: chant declarables and a plain-JS CDK app. One capture procedure profiles both synths with node --cpu-prof — the CDK side profiles the app subprocess via cdk.json, since profiling the CLI measures the wrong process — and one analyzer applies the same two measurements to both: - project-code boolean: did any frame from the estate's own source files execute? chant: false, doubly pinned (no sampled project frame + the run fails unless every file reports [fold:fold]). cdk: true. - trusted-computing-base bytes: distinct third-party files observed executing; the synthesizer/definition-library split falls out of each estate's package.json rather than a curated list. parity.mjs keeps the pair honest: identical resource surface, exactly two documented expansion-style deltas (both enlarge the CDK template), anything else fails. Captures are committed with machine-local path prefixes sanitized; timing appears in no output (not a benchmark). exhibits/render.mjs regenerates static timeline SVGs via spicypath's headless renderers: package-attributed colors, search-dim on project files, a derived marker at the first project frame — present near t=0 on the CDK exhibit, absent by construction on the chant one. On-demand via just leftness-capture; not part of gating CI. Closes #1084
…apshots (#1104) A Core Concepts page carrying the measured comparison from test/leftness: the one-question table (project code executed: chant no, cdk yes), the two static timeline exhibits (CDK lit with a first-project-frame marker near t=0; chant busy with an empty highlight and no frame to mark), boundary caveats stated (app-subprocess profiling, sampled-vs-enforced negative), and capability/delivery adjacency — the loomster reality sits in the same paragraph as the structural claim. Timing appears nowhere. Exhibits served from docs/public/leftness; regeneration procedure lives with the harness. Page publication is gated on the bar recorded on #1107, hence draft.
6 tasks
Each exhibit now links to the deployed viewer with the scenario encoded in URL state — Timeline mode, search highlight, and the first-project- frame marker restore on open. Both links validated in a real browser.
…1104) 'your code starts here' instead of a class name; the search-box preset is dropped — a viewer shouldn't need to know what ItemsStack means.
Contributor
Author
|
Status check, not a decision. This is a deliberate draft and merging it is the publish click recorded as a maintainer decision on #1107, so it stays as-is. Two things have moved since 2026-07-27. The stack is gone. #1120 merged, so the harness is out of this diff and what remains is the page. The gating measurement is stale. The bar on the PR body is stated against loomster's resource-bearing real src, and loomster is pinned to chant ^0.21.0 while chant is now 0.52.1. Fold has changed materially in between — call-form composite calls (#1174, #1965) and method-call folding after lexicon expression helpers (#1966), which took the chant corpus 89/108 to 95/108, now 97/111. Whether the bar is met cannot be read off the 0.21.0-era number either way. Re-measuring loomster on current chant is the prerequisite for the publish decision. Recorded here so the next person does not re-derive it. |
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.
For #1104. Draft on purpose: publication is gated on the publish bar recorded on #1107 (real infrastructure folds everything except should-never-fold patterns; loomster's resource-bearing real src folds none today). Merging this is the maintainer's publish click.
Stacked on #1120 (the harness) — the last commit here is the page; the rest is the harness and disappears from the diff when #1120 merges.
AC check (#1104)
test/leftness/).docs/public/leftness/*.svg) — readable with no viewer; Timeline mode so left means before; search-dim + first-project-frame marker (spicypath FG-064/FG-065).Docs build green (148 pages).
🤖 Generated with Claude Code