Practice Development

An active workspace where developers plan, design, and manage the workflow of building new AI systems — with every task, decision, and milestone grounded in the regulations that must be implemented as part of the design and development process. Governance by Design, delivered.

Workflow

Development Workflow

Visual, collaborative, and regulatory-aware. Every tool developers need to manage AI system development — with compliance built into the workflow, not bolted on after.

Kanban Boards

Workflow

Visual workflow management for compliance tasks — cards linked to regulatory requirements, drag-and-drop between stages, WIP limits, and team assignment. Every column represents a compliance stage, every card traces to the regulation that requires the work. Move tasks from 'Identified' through 'In Progress' to 'Evidence Attached' with full traceability.

Sprint Tracking

Velocity

Velocity metrics, burndown charts, and compliance task completion rates. Sprint planning that accounts for regulatory milestones alongside feature milestones — because a system that ships features but misses Annex IV documentation deadlines is not truly 'done'. Track compliance velocity as a first-class metric.

Collaborative Canvas

Design

Shared workspace for architecture review, data governance planning, threat modelling, and system design — all contextualised with applicable regulatory requirements. When your team designs a new model pipeline, the canvas surfaces the Article 9 data governance obligations, the Annex IV documentation requirements, and the Article 15 accuracy standards that apply.

Task Assignment

Traceability

Assign development, data governance, cybersecurity, and compliance tasks to team members — each task traces to the regulation that requires it. A task isn't just 'implement data validation'. It's 'implement data validation per Article 10(2)(f) — input data relevance verification'. The regulatory context is embedded, not bolted on.

Context

Regulatory Context in Every Task

System characteristics propagate into task descriptions, acceptance criteria include regulatory references, and governance gates are checkpoints in the development flow — not post-hoc paperwork.

System Characteristics Propagation

When you classify an AI system in the Navigator, its risk tier, applicable regulations, and specific obligations propagate into the development workspace automatically. Every task created for that system inherits its regulatory context — no manual cross-referencing, no forgotten requirements.

Regulatory Acceptance Criteria

Article 9

Task acceptance criteria include regulatory references alongside functional requirements. A task to implement training data validation doesn't just require 'data is validated' — it requires 'data is validated per Article 10(3) requirements for training data quality, with evidence of bias examination per Article 10(2)(f)'.

Governance Gates

Annex IV

Governance gates are checkpoints in the development flow — not post-hoc reviews. Before a system moves from design to implementation, the governance gate verifies that Annex IV Section 1 documentation exists. Before deployment, Article 14 human oversight measures are verified. Gates prevent regulatory debt from accumulating.

Obligation Traceability Matrix

EU AI Act

A live traceability matrix connects every development artifact — code commits, test results, design documents, review decisions — to the regulatory obligation it satisfies. When an auditor asks 'how did you satisfy Article 15 accuracy requirements?', the matrix provides the complete evidence chain.

Ecosystem

Integrations

Practice Development connects to the tools your team already uses — Jira, GitHub, GitLab, Trello, and Asana. Regulatory context travels with every exported task.

GitHub / GitLab

Bi-directional sync between compliance tasks and source control. Link commits to regulatory requirements, map pull requests to governance gates, and surface compliance status in your existing development workflow.

Jira

Export compliance tasks to Jira boards. Regulatory context, acceptance criteria, and obligation references travel with each task. Teams that standardise on Jira keep their workflow — with governance context embedded.

Trello & Asana

Lightweight integration for teams using Trello or Asana. Compliance cards and tasks sync with regulatory metadata intact. Status updates flow back to the Practice Development workspace for consolidated tracking.