Document supervised BNL verification with real screenshots - #109
Merged
Merged
Conversation
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.
Add a source-grounded GroundControl case study for the BNL public playground, with saved production/terminal screenshots, captions, hashes and links to the actual browser scorecards.
This records what happened: an operator used the authenticated persistent terminal to run bounded Rust/Node/Chromium checks on the VPS; GitHub held review/source; Vercel published the existing portfolio. It does not claim an autonomous Loop run, built-in BNL integration or new CI service. Captions clearly separate real public state and test-only inputs. The GC terminal crop excludes host identity and the shell prompt.
Adds a screenshot registry, links it from the root/documentation indexes, and clarifies that seeded screenshots are demonstrations rather than measured live evidence. Application code, architecture and Loop direction are unchanged. Relevant current product boundaries were checked against docs/LOOP.md, AGENTS.md and terminal source at 68e2c23.
Verification: file checksums, Markdown/image links, retained 31/31 actual-WASM browser scorecard, 30 portfolio tests, and independent public execution at portfolio release cb61c49. Repository CI/build gates will run for this docs-only change.