29 connected domain projects
AI governance, third-party risk, controls, privacy, audit readiness, resilience and assurance workflows connected through explicit records and review dependencies.

ABDULLAH AL OWASIAgentic GRC / controls assurance / accountable AI
A decision-grade operating model for AI-assisted compliance: agents can gather, draft, compare and prepare; accountable reviewers retain scope, materiality, control-effectiveness, exception, risk-acceptance, release and sign-off decisions.
Single source of truth
AI governance, third-party risk, controls, privacy, audit readiness, resilience and assurance workflows connected through explicit records and review dependencies.
Distinct decision spaces with bounded scope, evidence requirements, calculations, reviewer gates and handover outputs.
Common evidence, risk, control, issue and ownership objects keep cross-domain reasoning traceable without pretending unrelated decisions share one score.
Inspectable views for evidence freshness, exceptions, ownership, treatment, control status and management reporting.
Delegation boundary
Automation is treated as a preparation layer, not as delegated authority, certification, legal judgment or an audit opinion.
Capability map
Inventory the current operating model, rank the highest-value review workflows, surface broken or missing components and produce a bounded 30-day action plan.
Separate implementation, audit/assurance and strategic-governance viewpoints so recommendations are evaluated against the right decision authority.
Request, normalize and cross-check evidence; track freshness, exceptions and missing support before a reviewer relies on it.
Review system or process changes for downstream effects on authorization, logging, privacy, retention, vendor obligations and approved operating boundaries—even where the change is technically valid.
Define allowed tools, data classes, actions, approval conditions and escalation paths before autonomous workflows cross material boundaries.
Open D28 →Track source, dates, review state and decision lineage so generated conclusions remain distinguishable from verified observations.
Open D27 →Review prompt-injection exposure, credential handling, destructive actions, package/source provenance, permission escalation and explicit approval requirements as governance risks around autonomous execution.
Maintain use-case inventory, accountable owners, evaluation evidence, oversight, release prerequisites and material-change review.
Open D14 →Convert evidence expiry, control drift, vendor change, authorization change and unresolved exceptions into named review queues and decision triggers.
Open D29 →Separate framework interpretation from local implementation facts. Confirm current source material and applicability before a mapping or conclusion is treated as authoritative.
External automation benchmark
grcskills.com ↗ publishes 60 open agent skills across gap/readiness, statements of applicability, risk, audit preparation, evidence, vendors, policies, privacy, AI systems, incidents and continuity. The useful benchmark is not that agents can produce more documents; it is that routine GRC preparation is becoming automatable.
This portfolio therefore concentrates on the layer that remains consequential: evidence validity, control effectiveness, authorization, exception handling, treatment, residual risk and accountable sign-off.
The external library is linked as a public reference. It is not bundled into this repository, and its outputs are not represented as Abdullah Al Owasi's own authored methods.
Decision-grade review routes
Review who or what can act, under which identity, and where privilege or conflicting authority requires escalation.
Inspect D24 →Keep generated, observed and reviewed evidence states distinct and traceable.
Inspect D27 →Bound autonomous tool use and data access before execution.
Inspect D28 →Re-open decisions when risk, evidence, model behavior, supplier state or operating assumptions materially change.
Inspect D29 →Implementation boundary
The public system demonstrates review logic, synthetic scenarios, browser-local records, scoring, evidence states, decision exports and human authorization gates. It does not claim a production autonomous-agent runtime, live PR security scanner, client telemetry, independent certification, legal advice or an audit opinion. Production integrations require authorized data access, security review, tenancy controls, monitoring and an agreed implementation scope.