Skip to content

docs(core): left-of-line page — captures, side-by-side, static snapshot (#1104) - #1124

Draft
lex00 wants to merge 7 commits into
mainfrom
docs/1104-left-of-line-page
Draft

docs(core): left-of-line page — captures, side-by-side, static snapshot (#1104)#1124
lex00 wants to merge 7 commits into
mainfrom
docs/1104-left-of-line-page

Conversation

@lex00

@lex00 lex00 commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

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)

Docs build green (148 pages).

🤖 Generated with Claude Code

lex00 added 2 commits July 26, 2026 23:34
…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.
lex00 added 2 commits July 26, 2026 23:53
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.
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.

1 participant