Code mark · per file
Cyril
Sealed on commit. The overlay verifies supplied signatures and ranks the signed records in its report. It does not check every deployed file or independently establish a signer's identity.
Early access · Registration No. DA-001 · Ed25519
A vermilion stamp for the files you ship. Link GitHub, lock your marks and choose where to enable hooks. Enabled hooks sign staged files and publish their fingerprints on push. On sites with the optional report, press Shift + D to see signed file records and their registry status. No source on the board. No badge clutter. Just the evidence.
Early access. Ship with us while it grows. Found a bug? Report it in 589 ManCave on Discord.
01
What happens when you commit
Git history can get squashed or rewritten. Signatures stick to the code itself.
01
Per file
Sign code on commit
A pre-commit hook signs staged file bytes and their recorded context. A changed file, path or repository context needs a new seal; the original signed record remains verifiable for its original claim.
02
Owner only
Claim the repo
Repo autograph is optional and off for new installations. When enabled, the registry records a repo mark after checking the GitHub owner. This records a claim; it does not prevent copying, rehosting or independently signing the same code.
03
Shift + D
Open the honor board
Shift + D checks signatures and counts the signed file records in the report. Historical claims without signatures are excluded. It does not verify the deployed page or its complete source coverage.
04
Git hooks
Choose what runs
Linking creates your identity. The Windows desk turns global hooks on. They sign on commit and publish on push. A hooked commit on a website also writes the local Shift+D script into that commit.
02
Invisible until someone asks
No floating badge. No footer sticker. Shift+D opens on the page you shipped, after Dev Autographs is installed and that signed commit is live.
Inspect this project's signed records. Press the keys, or open the live report.
your-client.com · example report
Waiting for Shift + D…
Dev AutographsSigned records
Honorary report
-
01
Cyril
100
Example data · coverage not checked
Shift + D
01
Shows here
Your site in a browser
Install Dev Autographs, sign the commit, and ship that commit. Shift+D opens the report on that site.
02
Shows here
A Windows app you build, when its window is that page
Chat apps, editors, and other desktop apps built with Electron, Tauri, or WebView2. Install Dev Autographs, sign the commit, and run that build. Shift+D opens inside the app.
03
Coming soon
A Windows app you build with its own native window
Buttons and panels that never load your page. The signed script stays in the repo. A later release can add a panel for that kind of window.
03
Two stamps. Different jobs.
One rides each file. One claims the whole work.
Repo mark · per project
C. Foday-Kailie
The registry checks the GitHub repository owner before accepting repo ink. The overlay displays the project's supplied mark; that label alone does not prove ownership.
04
Framework-aware setup
The CLI recognizes common project layouts. Review its generated integration and run your build before deploying the overlay.
Vite
Next.js
SvelteKit
Nuxt
Astro
Remix
Gatsby
Django
Plain HTML
Tauri (skipped on purpose)
05
What you actually touch
Ink GitHub, lock your marks, and leave global hooks on. A website commit writes the local Shift+D script.
01 Download and install +
- Get the latest Windows build from Installer Releases.
- Run the NSIS installer to install the desk app and CLI. Node.js 20+ is required for the CLI. The desk turns global hooks on for this Windows user. The CLI installs hooks only when you pass
--hooksor--global.
02 Link GitHub +
- Click Ink your GitHub. Approve the device in the browser.
- The signing key is created on this computer. Sign-in deposits it so the registry can store an encrypted copy. The next computer downloads that copy, and this one is signed out.
03 Shape your marks +
- Open Autograph. Set mark text, handwriting style, and an optional chip. Save a separate repo mark for projects you own.
- Marks live in your registry profile, not inside your source files. Automatic repo autograph is off for new installations; enable it in the Stamp Room when you want to publish that claim.
04 Sit back and work as usual +
- The Windows desk turns global hooks on after you link. Turn Global hooks off in Stamp Room to stop new signatures, and confirm the warning first. The CLI installs hooks only with
paw-prints install-hooksorlogin --hooks. - With hooks on, commit and push as usual. The hooks seal staged files on commit and publish fingerprints on push.
- On a website, that commit writes the local Shift+D script into the repo and stages it. It is generated on your computer.
paw-prints sync-overlayis the explicit refresh: it lists edits and does not stage them. - Press Shift + D after deploying that integration. To undo unchanged generated integration files, run
paw-prints remove-overlayand review the result.
05 Bugs and help +
- Report bugs or ask questions in Discord: 589 ManCave.
- Installer downloads and release notes: Installer Releases.
06
About us
Developer tools from Axiom Risk Group.
Dev Autographs is built and operated by Axiom Risk Group. We provide tools that help developers and teams sign contribution records, inspect code provenance, and maintain attribution across software projects.
Our work centers on clear records, practical signing workflows, and evidence that developers can inspect.
St. Paul, MN
Cyril Foday-Kailie
Technical Lead and Senior Superintelligence Engineer at Axiom Risk Group, based in St. Paul, Minnesota. His technical work focuses on code provenance, signing workflows, and developer tools.
He leads the design and engineering of Dev Autographs, including its Windows desk, signing tools, registry, website, and Agent 589. This work supports practical workflows for reviewing signed records and understanding a project's development history.
Drag Agent 589 onto any surface-like area. Drop him. Tap him for a tip.
Agent 589 on this page
- Axiom Risk Group
- Technical lead
- Code provenance
Put your name on it.
Early access. Free. Windows 10 and 11. The signing key is created on your computer, and the registry keeps an encrypted copy for the next sign-in.
On macOS or Linux, or no install? The web desk inks your GitHub in the browser and gives you a one-time identity setup script, with an explicit option for global Git hooks. Questions or bugs: 589 ManCave on Discord.