Skip to content

About

No description, website, or topics provided.

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

565 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Policy System

Policy System is a Open Source Software that can ingest EU regulations and internal business policies into a unified regulatory and compliance knowledge graph, and answer questions against it in natural language.

  • "What approved policies do we have in place that cover the Cyber Resilience Act's obligations for manufacturers?"
  • "What do I need to consider if I use library XYZ in the code base I'm working on?"
  • "Which governed capabilities have no working control yet?"

Answers are grounded in the graph — every claim traces to regulation text and policy content that was retrieved. AI is used to analyze questions, derive intent, create queries and converting the returned data into an answer. The actual queries are fully deterministic. Where AI is involved, measures have been implemented to ensure that data is accurate and reliable.

Features

Feature Description Business value Status
EU Regulation Ingestion Ingest an EU regulation by CELEX identifier (via Cellar/ELI), mapping its raw text into the compliance graph Removes manual regulation tracking and transcription; keeps coverage current with authoritative source text ✅ Implemented
Internal Policy & Regulation Ingestion Author internal business regulations, policies, standards, and controls from a structured intake document Brings internal governance into the same graph as external regulation for unified traceability ✅ Implemented
Natural Language Compliance Q&A Ask compliance questions in plain language via Claude Desktop or VSCode; answers are grounded in and traceable to graph data Makes compliance knowledge accessible without requiring Cypher or graph expertise ✅ Implemented
Regulatory Knowledge Graph Unified compliance spine linking Regulatory Instrument → Role/Requirement → Obligation → Capability → Policy → Standard → Control Single source of truth connecting obligations to concrete controls with full provenance ✅ Implemented
Regulatory Change Monitoring Polls EU sources for amendments to tracked regulations and triggers re-ingestion of affected content Keeps the graph current without manual regulation-watching effort ✅ Implemented
Curated Content Catalog Restore pre-ingested regulations and standards (e.g. CRA, GDPR) from vetted artifacts instead of running a full ingestion pipeline Faster onboarding and evaluation; avoids re-running expensive ingestion for common instruments ✅ Implemented
Passkey-Signed Privileged Actions Requires a signed passkey approval before a privileged action is carried out — every Graph Cleanup merge, release and unmerge, including a Capability merge started from a near-miss review Prevents high-impact actions (like conflating distinct obligations or capabilities) from happening without a human signing off ✅ Implemented
RBAC + ABAC Authorization Role- and attribute-based access control for who can read, ingest, or approve content in an instance Lets organizations restrict sensitive compliance data and approval actions to the right people ✅ Implemented
EU-Instrument Applicability Assessment MCP skill that interviews a Compliance Officer on markets, geographies, and products, then proposes a tiered likely/possible/excluded list of candidate EU regulatory instruments from general model knowledge, flagged against what's already ingested Surfaces regulatory blind spots and cuts down over-cautious manual scoping of applicable regulation, without claiming a precision the EU itself hasn't defined ✅ Implemented
Policy/Standard/Control Proposal Lifecycle Author and review a Policy, Standard, or Control as a proposal before it's committed to the graph Lets policy managers draft and review governance content with an approval step, instead of authoring directly into production ✅ Implemented
Guided Policy/Standard/Control Authoring MCP skill that walks a user field-by-field through drafting a Policy, Standard, or Control against quality rubrics for a Capability with a coverage gap Closes the loop from a detected gap to authored governance content, without a separate Policy Editor client ✅ Implemented
National Transposition & Directive Monitoring Track how an EU directive is transposed into national law per member state, and monitor each transposition for amendments Answers jurisdiction-specific compliance questions instead of only the EU-directive level 🗺️ Roadmap
PS Postgres Backup & Restore One physical backup and one restore of PS Postgres; graphs rebuilt from the log. Scheduled backups and WAL/RPO: #234 (planned) Protects the audit trail and the compliance graph against data loss and supports disaster recovery ✅ Implemented

Getting started

Evaluating Policy System

If you want to try Policy System and evaluate it on your own computer this is documented in the installation guide's Evaluator installation section.

Installation paths

Path Support level Verified
Evaluator Supported for evaluation on your own computer Live on a clean kind cluster; see Verification status
Production Experimental, not verified on AKS On kind only; see Verification status

Contributing to Policy Systems codebase

If you want to help develop and evolve Policy System we welcome your contributions. See CONTRIBUTING.md for development setup, coding standards, testing, and the contribution workflow.

Understanding the architecture

Architecture and domain documentation lives in docs/:

Repository layout

Every top-level entry in the repository and its purpose. Entries marked untracked exist only in a local checkout.

Path Purpose
.agents/ Agent skills used when developing the repo (init-takt-devcontainer, ps-pentest)
charts/ Helm chart policy-system and its tests
.claude-plugin/ Plugin marketplace manifest that distributes ps-skills/ps-plugin
.claude/ Claude Code project skills (skills/); local state files in it are not tracked
CONTRIBUTING.md Development setup, coding standards, testing and release workflow
.cspell.jsonc Spell-check configuration (pre-commit)
curated-content/ Curated, restorable instrument artifacts and catalog.json; see its README
default.code-workspace VS Code workspace file produced by the init-takt-devcontainer skill
deploy/ Local kind cluster definition used by scripts/deploy-ps-eval.sh
.devcontainer/ Dev container definition: image, FalkorDB compose service, post-create script
.dict Repository word list for the spell checker, referenced from .cspell.jsonc
Dockerfile PS Service container image build
.dockerignore Allow-list build context for the Dockerfile
docs/ Architecture, artifacts (guides and contracts), audits, coding standards, regulation texts, templates
.env.example Template of environment variables for local runs; copy to the untracked .env
.falkordb-data/ Local FalkorDB persistence volume (untracked, ignored; see CONTRIBUTING.md)
.git-blame-ignore-revs Revisions skipped by git blame (currently only a placeholder entry)
.gitattributes Line-ending normalisation (eol=lf)
.gitconfig Repository git settings (hooks path, aliases); include it from your local git config
.githooks/ Git hooks: pre-commit and pre-push
.github/ GitHub workflows, composite action, issue template, Copilot instructions and skills
.gitignore Ignore rules for caches, virtual environments, build output, logs and local state
.insitu.yml gh insitu task definitions for local checks and fixes
internal-sources/ Source documents and seed data for the internal Engineering Practices instrument
logs/ Local service logs (untracked, ignored; only .gitkeep is tracked)
.markdownlint-cli2.jsonc Markdown lint configuration (pre-commit)
node_modules/ Pinned pre-commit tool packages installed by npm ci (untracked, ignored)
package-lock.json Lock file for package.json
package.json Dev-only pins for prettier, markdownlint-cli2 and cspell used by pre-commit
.pre-commit-config.yaml Pre-commit hooks: formatting, lint, type check, spelling, repository checks
.prettierignore Paths prettier does not format
ps-cli/ ps-cli command-line client for PS Service
ps-service/ PS Service: the REST API, MCP server and ingestion pipeline
ps-skills/ Source of the Claude plugin (ps-plugin): skills, rubrics, MCP connector config
ps-test-support/ Shared test helpers (uv workspace member)
pyproject.toml uv workspace root and shared tool configuration
README.md This file
scripts/ Deployment, release and verification scripts
spikes/ Local throwaway experiments (untracked, ignored)
test-data/ EU regulation extraction samples and capability-merge decisions consumed by tools/graph-ingestion
tools/ Developer tools: graph ingestion and query, curated export, backup-restore verification, company merge, domain mapper, skill tooling
uv.lock Locked Python dependency set
.venv/ Python virtual environment created by uv sync (untracked, ignored)
.vscode/ Shared VS Code workspace settings

Target audiences

Policy System has been designed with the following roles in mind:

Role Primary use case
Compliance Officers Define governance processes; review regulations; select and ingest external regulations
Policy Managers Create, edit, and approve business policies and standards; manage content lifecycle; ingest internal regulations
Legal Counsel Review regulatory requirements and organizational responses; evaluate coverage gaps
Security Architects See technical controls mapped to the obligations they fulfil; design compliant solutions
Risk Managers Compliance scores with drill-down by obligation, policy, standard, and control
DevOps/Engineering Query compliance status of solutions; integrate automated checks into CI/CD
Auditors Review governance decisions and approval logs; trace obligations to controls with full provenance
Software Engineers Check what a Standard or Control requires before shipping; "is my service compliant?"
Security Engineers Find coverage gaps below the Policy level; reason about blast radius if a control fails
Engineering Managers Whole-team posture summaries and prioritised punch lists — open-ended synthesis, not single-entity lookups
System Admins Check service health and readiness; provision ps-cli's named targets/contexts; manage Policy-System global settings

About

No description, website, or topics provided.

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages