Repository navigation
Conversation
Demo build outputs (decompiled sources, reversed manifests and plists, app binaries, and output.txt) are only trustworthy if they came from an actual build plus reverse engineering or scanning run. Nothing in the instructions said so explicitly, and the demo instructions applied only to `demos/**/*.md`, so an assistant editing output.txt or MastgTest_reversed.java loaded no demo guidance at all. - Widen applyTo from `demos/**/*.md` to `demos/**` so the rules load when any demo file is edited, not just the write-up. - State that build artifacts must be generated and never written, edited, or reconstructed by hand or from memory, calling out AI assistants explicitly. - Note the two consequences that bite in practice: r2 script addresses shift on every rebuild, and editing run.sh changes output.txt. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diolor
changed the title
This branch has not been deployed
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
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.
Description
[AI generated]
An AI assistant can produce a convincing
MastgTest_reversed.java,output.txt, or r2 disassembly that never came from a build. It reads correctly and looks verified, so it survives review — a fabricated artifact is worse than a missing one.Demos written or modified with AI therefore have to be verified by actually building the MASTestApp and running the reverse-engineering or scanning pipeline against it. Nothing in the instructions asked for that, and
mastg-demo.instructions.mdapplied only todemos/**/*.md, so editingoutput.txtorMastgTest_reversed.javaloaded no demo guidance at all.These artifacts also drift on their own: changing a demo's
run.shsilently invalidates its committedoutput.txt, and one untouched demo's output no longer reproduced under a newer semgrep. Both are only visible if you run it.AI Tool Disclosure
This contribution does not include AI-generated content.
This contribution includes AI-generated content.
AI tools used: Claude Code
Models and versions: Claude Opus 5
Prompt summary: Asked the assistant to review an in-progress branch for missing content and incorrect cross-references. It found the
applyTogap and the absence of any rule against hand-writing artifacts; I then asked it to draft both changes. Wording reviewed and adjusted before opening.Contributor Checklist