A Key's Day
Can someone who does not write code explain how one key leaks during an ordinary workday, and what a team has to do before it is actually fixed?
The problem
Sales and business teams hear terminal, Git, pipeline, verification, and rotation without seeing how those words connect.
A rep who cannot separate finding a secret from checking whether it still works, or a notification from a fix, overstates or undersells in front of a security buyer.
Without a repeatable answer: The workflow gets explained with slides and jargon. Non-coders memorize terms without the day behind them.
My contribution
I designed the story, the cast, and the lesson structure for sales and enablement readers, and built the site with an AI coding assistant. It is independent work, not employer training. Truffle Camp is the separate hands-on curriculum design; this is the story series a reader can open today.
One example
Part 1 (Code): one story from workstation to rotation, then four more parts on the same engine. This version tests: Can a non-coder follow one key through a day and tell detection, verification, notification, and rotation apart?
- Who uses it
- A rep, SE, or new hire before a conversation with a security team, or anyone asked to explain a leaked credential to the business.
- Decision it enables
- Whether the reader can separate finding a copy, checking that it still works, telling the owner, and replacing it.
- What it produces
- A five-part walkthrough: Code, People, Systems, Agents, and Coverage. Each part ends with the old key shut off and confirmed.
Workflow and next steps
- Inputs → review → output
- A made-up key → one developer's day, step by step → the copies it leaves → the old key shut off and confirmed.
- Planned next
- A walkthrough with a non-coder reader, then one practice exercise on which control would help.
- Technologies in this repo or a linked project
- A static site in HTML, CSS, and JavaScript with one shared lesson engine, hosted on Vercel. No account, database, or model.
Metric to test
I have no learner results yet. The site counts anonymous steps reached, with no cookies. The test I want: after one part, a reader explains detection versus verification in their own words.
Links
How it works
Project overview
Live and public, with five parts merged. A walkthrough with a non-coder reader is still open.
Five public parts with 66 steps in total, a named cast, and a jump-to-topic index. The key is invented and progress is not saved.
What I was working from
A five-part interactive series, live and public: Code (18 steps), then People, Systems, Agents, and Coverage (12 steps each). One made-up key moves through an ordinary day, and every part ends with the old key shut off. Independent lesson. The key is invented, nothing is scanned, and progress is not saved.
Workflow
Workstation → Editor → Pre-commit → Repository → Pipeline → History → Detect → Verify → Analyze → Notify → Rotate
In plain language
One story engine shared by five parts → A made-up key and a named cast → Optional detail with cited sources → A jump-to-topic index
Implementation notes
Proposed architecture. The technology section identifies what each project uses today.
Static HTML, CSS, and JavaScript · One shared lesson engine · Lint, format, content, and test checks on every change · Static hosting on Vercel
Part · Step · Copy of the key · Cast member · Source
Live, public lesson series. An independent project, not employer training. Source repository is private.
Goals
- Explain what a secret is and how one secret ends up with several copies.
- Name places outside source code where a copy can remain.
- Separate detection, verification, analysis, notification, and rotation.
- Show why rotation is the step that removes access, and why it is hard.
Out of scope
- Scanning real code or handling real credentials.
- Replacing official product documentation.
- A course platform: no accounts, scores, or saved progress.
Metrics I would watch
These are not results unless the section above says they are on record.
- Lesson checks pass on every change
- A reader explains detection versus verification in their own words
- Hypothesis: a rep explains a leaked key to a security buyer without overclaiming.
If a non-coder watches one key move through a real workday, the vocabulary sticks because each word arrives at the moment it matters.
Tradeoffs
- One made-up key and one story vs. a broad reference.
- A static site with no saved progress vs. a course platform.
- Optional detail folded away vs. everything on screen.
What I would build next
- A walkthrough with a non-coder reader.
- Recheck tool details against official sources.
- One practice exercise: which security control would help here?
Explore related work
Truffle Camp
A secrets-security learning path with a written module and one synthetic practice question.
Try the exampleCompetitive Intelligence Engine
Help sellers turn competitive research into useful buyer conversations. Explore a source-backed field brief and a proposed review workflow.
Try the example