01
Policy is disconnected from planning
A feature can be technically valid while its implementation plan already conflicts with internal privacy, security, or governance requirements.
Policy-aware development for Claude
Built for IBM Bob 2.0 Hackathon · LexHack 2026
Make policy part of the development loop.
RegTrace brings your company's policies into Claude's workflow before code is written, while implementation is happening, and after the code is complete.
Claude Desktop
Local repository access
Your policy documents
Claude + RegTrace
feature
Export customer profiles to external CRM
RegTrace · plan review
↳ Policy requires explicit consent
↳ Add consent gate before external transfer
RegTrace · post-code review
customer_export.py
↳ CRM call executes without consent gate
Claude · fix applied
RegTrace · fresh review clear
The gap
Coding agents know your code.
They do not automatically know your rules.
Company policies often live in PDFs, documents, wikis, and legal text. Development happens somewhere else. RegTrace connects those two worlds inside the coding workflow itself.
02
Code review happens too late
Requirements discovered after implementation create rework. RegTrace introduces policy review before the first code change.
03
Generic advice misses the repository
RegTrace gives Claude the actual local project, grounding policy reasoning in real files, functions, integrations, and data flows.
Workflow
One development loop.
Policy checked at every critical moment.
Attach the relevant policy documents to the Claude conversation, provide the local repository path, and let RegTrace enforce the review sequence.
Input
Feature request
→
01
Claude creates a plan
→
02
RegTrace reviews the plan
→
03
Claude implements
Result
Policy-aware implementation
←
06
Fresh final review
←
05
Claude fixes supported issues
←
04
RegTrace reviews code
Example
A feature can work perfectly
and still conflict with policy.
RegTrace is designed for exactly that gap: functional software whose behavior conflicts with requirements supplied by the organization.
Customer CRM export
Policy-aware review
Company policy
Customer personal data may only be exported to an external service after explicit user consent.
Implementation
def export_customer(customer):
if customer.export_consent:
audit.log("consent-observed")
crm.send(customer.email)
RegTrace review
Policy issue found · customer_export.py
The consent condition only controls logging. The CRM transfer still executes when explicit consent is absent.
Claude correction
def export_customer(customer):
if not customer.export_consent:
raise PermissionError(...)
crm.send(customer.email)
Fresh review
The reviewed path is now consistent with the supplied policy. RegTrace does not claim universal legal compliance.
Install & try
Download it.
Install it in Claude Desktop.
RegTrace is a local MCP extension. Download the project from GitHub, install the Python dependencies,
then load the mcp-adapter folder as an unpacked extension in Claude Desktop.
INSTALL
Four quick steps
1
Download RegTrace from GitHub and extract the ZIP.
2
Run the Python dependency installation command.
3
Claude Desktop → Settings → Extensions → Advanced settings → Extension Developer → Install unpacked extension.
4
Select
mcp-adapter, restart Claude, attach your policies, and give Claude your local project path.
Ready to try it?
The button below downloads the current
main branch directly from GitHub as a ZIP.
PowerShell
cd PATH\TO\regtrace
python -m pip install -r .\mcp-adapter\requirements.txt
cd .\mcp-adapter
python -c "import server; print('REGTRACE MCP OK')"
Claude tools
regtrace_review_plan
regtrace_review_fix
Python 3.10+ required. If python is not available on PATH, update the MCP manifest command to your local Python executable.
RegTrace
Attach the policies.
Point Claude at the repo.
Build with the rules in the loop.
Plan review before coding. Real source review after coding. Fixes applied by Claude. Fresh review after every change.