Input
Domain change requests are captured in a structured way. The model helps with wording and orientation, but it does not replace professional judgment.
Funktion8 for regulated notarial process work
Notariat as Code
NoC turns notarial procedures into versioned, reviewable and approvable operating artifacts. The LLM is the input surface; domain truth is created through review, approval and traceable change.
- Leading language
- German
- Change flow
- Enterprise GitOps
- Execution
- Local notarial workstation
Target model
A controlled workspace for notarial digitalization.
NoC separates installable plugins, executable workflows and concrete use cases. Card reader, XNP, registry and portal paths are treated as gates, not loose integrations. Every domain change is versioned, validated and approved before productive use.
Operating model
From prompt to approved process version.
Versioning
Policies, workflows, use cases, knowledge graphs and SBOM artifacts exist as traceable repository changes.
Approval
Sensitive steps use dual control, review and documented rationale. Completion means a validated state merged into `main`.
Governance
Rules first, automation second.
Law and regulation
Legal, regulatory and audit-proof requirements take precedence over automation convenience.
Data protection and DPA
No real secrets or personal data in the repository. SaaS processing of personal data requires DPA review.
Local workstation
NoC executes notarial gates locally in the approved workspace. Omnistation is not an execution location for NoC.
Multilingual operation
German leads for German law and notarial use cases; English is an orientation and mirrored translation.
Artifacts
The work surfaces are deliberately separated.
Plugins
Installable interfaces and workstation adapters, such as card reader, registry or portal paths.
Workflows
Executable notarial process chains with deterministic checks, gates and evidence points.
Use cases
Concrete notarial matter types with their own knowledge graph and domain case structure.
Next step