Skip to content

Explore

Work sample

More work

Work examples and collaboration

Contact

Direct inquiry and collaboration

Explore the books

EnglishDeutsch

Collaboration · AI & workflows

Good work begins with a clear handover.

Karl Philipp Nolte · Workflows, AI and knowledge systems

I work on ways to make requirements, open questions and the next decision easier to see. Start with a concrete briefing example, then explore the projects behind this approach.

See the briefing exampleContact Karl

A work sample · For small agencies

What is missing before the team starts?

One brief, two deadlines, no clear approval. A fictional project shows how this can become a handover that people can review.

Explore the three examples

Project start / Draft

Deliverable
One service page. No shop.
Open question
8 or 15 October — which deadline applies?
Before starting
Agree the deadline and review responsibility.

Synthetic example. Not a client result.

Work examples

AI Product Proof

Local synthetic reference demo

Grounded AI Workflow Reference Demo

Problem

Document based AI workflows can sound convincing even when a source is outdated, a capability is only planned or evidence is insufficient.

What exists
  • Approved synthetic corpus and hard allowlist.
  • Six demonstration cases, including support, overclaim blocking and No Answer.
Boundary

It is not a production assistant and does not include a generative model integration.

Explore the example

Knowledge Product

Public reader and research system

Nexus Knowledge and Publication System

Problem

A large bilingual research and writing project can confuse readers if book, protocols, research notes and claims boundaries are not separated.

What exists
  • Bilingual reader routes and topic paths.
  • Book, protocol, whitepaper and research entry points.
Boundary

The system is a publication and knowledge product. Scientific, health and commercial claims remain bounded and require careful source review.

Explore the example

Workflow Product

Prototype and paid pilot check preparation

Dialog Based Field Service Assistant

Problem

Small field service teams lose time when technician messages arrive incomplete and office staff must reconstruct what happened.

What exists
  • Sanitär pilot scope and shared field service core.
  • Clarification logic, preview gating and structured report draft boundaries.
Boundary

This is not an autonomous service system and has no external validation yet.

Explore the example

Pilot in preparation

Berufskompass

Materials for a guided pilot with an education partner have been prepared. They support career reflection through personal strengths, working conditions, life experience and small next steps.

It is not a diagnostic tool, not a job guarantee and not yet externally validated.

Product Decisions

What connects the work

A clear task, results that can be checked, and a responsible decision determine the next step.

Scope before expansion

Each case starts with one narrow problem, a visible boundary, and a deliberate stop point before platform expansion begins.

Evidence before claims

Each example states its current stage and limits. Supporting evidence from the private working archive can be requested for a specific discussion.

Human review stays visible

AI and workflows may structure preparation, yet accountable humans review critical outputs before any external decision or release.

Release maturity is stated

Each example explains what you can use today, what has been tested locally, and what still needs to be tried with real users.

Method

Working method

The same pattern appears in AI workflows, publication systems and service operations.

  1. Clarify the task

    Identify who needs help, what is unclear, and which decision a useful result should support.

  2. Set a manageable scope

    Define the smallest useful behavior, document exclusions and avoid pretending that future work is already implemented.

  3. Build checkable artifacts

    Build demos, drafts and templates with explicit review criteria. Clearly distinguish public examples from evidence held privately.

  4. Validate and decide

    Use tests, checklists, feedback or human review to decide whether to continue, narrow, pause or stop.

Artifacts

Checkable artifacts

These documents describe the technical basis of the examples. They are held in the private working archive; appropriate access can be discussed for a specific review.

  • Grounded AI demo quickstartPrivate source · currently not publicly accessible
  • Grounded AI interview guidePrivate source · currently not publicly accessible
  • Employer viewPrivate source · currently not publicly accessible
  • Claims and scope boundaryPrivate source · currently not publicly accessible

Fit

Where this work is relevant

These examples offer starting points for professional discussions, product work and technical collaboration.

  • AI Product Management and responsible AI workflow design.
  • Data, knowledge and documentation products that need traceability.
  • Technical platform Product Ownership with Engineering collaboration.
  • Workflow systems where review, uncertainty and handover matter.

Where the work stands

The website is publicly available. The AI example is a local demo, and the service assistant is being prepared for a pilot. Their usefulness in everyday business still needs to be tested with real users.

  • No production AI assistant is claimed.
  • No customer case study is implied without external validation.
  • No health, revenue, ROI or automation guarantee is made.
  • No private application or client data is exposed.

Contact

Professional contact

For hiring, product review or institutional conversations, send a short note with the context and the case you want to discuss.

Emailhello@wateristheholygrail.com
SubjectProfessional Work inquiry - Product cases
Open mail clientOpen LinkedIn

Please do not send confidential source material or personal data in the first message. A short context is enough.