Skip to content

Connect Stele to secure-pride: fix stale project entry, add scenario corpus - #67

Merged
mazze93 merged 1 commit into
mainfrom
secure-pride-case-study
Sep 11, 2026
Merged

mazze93 merged 1 commit into
mainfrom
secure-pride-case-study

Conversation

@mazze93

@mazze93 mazze93 commented Sep 11, 2026

Copy link
Copy Markdown
Owner

Summary

Part of the Stele × secure-pride case study work (documented separately in secure-pride-design).

  • src/data/projects.ts: the secure-pride entry described a superseded 802.1x/MDM conception (Python/FreeRADIUS/step-ca/Mosyle/UniFi/Swift MacProbe) — verified via grep that none of those terms appear anywhere in the current mazze93/secure-pride repo. Corrected stack, hardStops, root (was ~/dev/secure-pride, actually ~/Projects/secure-pride/secure-pride), and openQuestions to match reality: an Astro/Cloudflare site with a Rust/WASM AI Safety Scanner, published to GHCR.
  • evals/corpus.ts: added four secure-pride/* scenario cases, one per TOBIRA category, shaped around this session's own work rather than generic phrasing — a leaked GITHUB_TOKEN inside a pasted CI debug log (APOCRYPHA), an incident-pressure request to skip the Trivy vulnerability gate (KAPU-OVERRIDE), a false "security team pre-authorized this" claim to skip review on a MAX-posture change (NARIKIRI-ADMIN), and a hidden HTML-comment instruction to suppress a finding in a scan report (PALIMPSEST).

Test plan

  • All four new cases verified firing on exactly their expected TOBIRA, zero collateral (direct scanPasteInput() call, output captured for the case study doc)
  • pnpm test — 68/68 passing (unchanged)
  • pnpm build — clean (tsc -b && vite build)

Note: git push surfaced 6 pre-existing Dependabot alerts (2 high, 4 moderate) on main — unrelated to this change, flagging for visibility rather than fixing here.

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

🤖 Generated with Claude Code

…corpus

The secure-pride project entry described a superseded 802.1x/MDM
conception (Python/FreeRADIUS/step-ca/Mosyle/UniFi/Swift MacProbe) with
zero matches anywhere in the current mazze93/secure-pride repo — verified
via grep before touching it. Corrected stack, hard stops, root path
(was ~/dev/secure-pride, actually ~/Projects/secure-pride/secure-pride),
and open questions to match what the project actually is now: an
Astro/Cloudflare site with a Rust/WASM AI Safety Scanner, published to
GHCR. Hard stops updated from network/MDM-specific items to the ones that
actually apply: credential handling, container publishing, scan-output
masking.

Added four scenario-shaped cases to evals/corpus.ts under
secure-pride/*, one per TOBIRA category, built around this session's own
work rather than generic phrasing: a leaked GITHUB_TOKEN pasted inside a
CI debugging log (APOCRYPHA), an incident-pressure request to skip the
Trivy vulnerability gate (KAPU-OVERRIDE), a false "security team
pre-authorized this" claim to skip review on a MAX-posture change
(NARIKIRI-ADMIN), and a hidden HTML-comment instruction to suppress a
finding in a scan report (PALIMPSEST). All four verified firing on
exactly their expected TOBIRA with zero collateral, via a direct
scanPasteInput() call — output captured for the case study.

pnpm test: 68/68 passing (unchanged). pnpm build: clean (tsc -b + vite).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MSmuvkMSicpAdpwPotKm5M
@mazze93
mazze93 merged commit d54399c into main Sep 11, 2026
8 checks passed
@mazze93
mazze93 deleted the secure-pride-case-study branch September 11, 2026 07:45
@mazze93
mazze93 restored the secure-pride-case-study branch September 16, 2026 11:11
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