Add autonomous MrTrust target integration contract
All checks were successful
Build MrTrust / build (push) Successful in 2m45s

This commit is contained in:
2026-05-16 02:03:25 +02:00
parent 01148f4703
commit 84a5df7216
8 changed files with 282 additions and 1 deletions

View File

@@ -21,6 +21,8 @@ MrTrust does not bypass Microsoft Defender or SmartScreen. Windows can still sca
- `scripts/Sign-MrTrustProject.ps1` signs `.exe`, `.msi`, `.ps1`, and other Authenticode-compatible files.
- `scripts/New-MrTrustRelease.ps1` builds a distributable ZIP package.
- `docs/integration-prompt.md` is a prompt you can paste into other Windows projects.
- `docs/agent-target-integration.md` is the autonomous target-project integration runbook for agents.
- `mrtrust.integration.json` is the machine-readable integration contract.
- `MrTrust.exe` is standalone for normal users. It embeds the public certificates and runtime scripts.
## Quick Start For MrSphay
@@ -95,6 +97,12 @@ Then choose the all-users option in the GUI.
Yes. Give another agent this repository URL, the target Windows project, and `docs/integration-prompt.md`.
For autonomous work, the agent should read these files in order:
1. `mrtrust.integration.json`
2. `docs/agent-target-integration.md`
3. `docs/integration-prompt.md`
The agent's job is to modify the target project, not this repository:
- expose a visible "Open MrTrust" or trust setup path for users
@@ -121,3 +129,5 @@ If the target project is not signed, MrTrust cannot make it trusted.
## Recommended Project Integration
Use `docs/integration-prompt.md` in another Windows project. The prompt tells Codex or another assistant to add a visible trust check, a link or bundled copy of the standalone `MrTrust.exe`, and a signing step without hiding security changes from the user.
For agents that can inspect files autonomously, `docs/agent-target-integration.md` gives the decision tree, installer patterns, signing commands, and completion checklist.