01Source & scope
Identify the organisation, question, source versions and time period. Make permitted inputs and exclusions visible.
The Aprentiz platform
Aprentiz is being built to connect private AI, organisational knowledge and governed workflows. Its purpose is to keep the evidence, human judgement and follow-through together throughout professional work.
For the people who own the outcomeCompliance, legal, operations and technology teams working on decisions that need a clear source basis and a responsible owner.
The connected journey
Each stage should leave something useful for the next person: a defined scope, inspectable support, a recorded decision or evidence of what changed.
Identify the organisation, question, source versions and time period. Make permitted inputs and exclusions visible.
Use private AI and retrieval to compare material. Keep source links, contradictions, gaps and unknowns attached to the work.
The responsible professional reviews the evidence, records a rationale and decides whether to proceed, hold or request more information.
Assign the next action. Test the change against its original acceptance criteria. Preserve unresolved issues and later reconsideration.
Connect the source basis, workflow version, decisions and results so another authorised person can review what happened.
The complete system
The two Proving Grounds sit above a shared architecture for identity, context, private models, knowledge, governance, verification and retained evidence.
Workflow Proving Ground + Implementation Proving Ground
Identity · permissions · context · workflow
Admitted documents, retrieval,
policy and bounded memory.
Generation, embeddings
and qualified verification stages.
Requirements, evidence, decisions,
actions, retests and closure.
Exact source text, provision state
and explicit temporal uncertainty.
Sources → decisions → actions → retests → review
GRC & Aprentiz Guard
Governance, risk and compliance connect requirements to actions and retests. Guard provides a distinct source-verification function. Both are part of the complete platform design.
The GRC design carries admitted requirements through assessment, policies, controls, evidence, named decisions, actions, retests and controlled closure. Missing evidence and unknowns stay visible.
Guard’s deterministic core checks exact source text and source-stated provision status against versioned evidence. It separates support from citation attribution and preserves uncertainty about time or missing history.
The platform remains in development. Built and tested components, a private research demonstration and a fully qualified client installation are different stages. Each workflow and destination needs its own acceptance evidence.
A practical place to begin
A defined regulatory change. A recurring policy review. An AI-assisted operational workflow. Start with the current process and the evidence its owner needs to make a decision.