PARAF · DRAFT

For individuals, professional teams and organisations that value control over their context

Useful intelligence. Memory and permission under your control.

PARAF is a privacy-first intelligence layer for individuals and organisations. It is designed around locally controlled memory, explicit consent and clear limits on what assistance may do, so useful context can support everyday work while people decide what is retained, shared and authorised.

A review stand and poised pen connect to a local-memory cabinet through a visible manual consent control.
PARAF · The consent instrument · Concept illustration

The problem

Assistance needs context. Trust needs clear boundaries.

Memory without a clear purpose

Retained context is difficult to trust when people cannot understand why it is kept or how it will be used.

Permission without a clear scope

An approval can become ambiguous when access to information is treated as permission to act on it.

Help without visible limits

Assistance is harder to assess when the sources it uses and the external services it relies on are unclear.

What it does

What you get.

Connect helpful memory and reviewable assistance with deliberate control over their use.

Keep memory purposeful

  • Organise retained context around the work it is intended to support.
  • Make the basis for remembering, revising or removing context understandable.
  • Define local storage and retention boundaries for the agreed environment.

Make consent specific

  • Distinguish permission to read information from permission to use or share it.
  • Make the proposed action and its intended destination clear before approval.
  • Keep approval tied to a defined purpose and scope.

Bound the assistance

  • Prepare drafts and suggestions with their supporting context available for review.
  • Make available capabilities and external service routes visible.
  • Separate preparation from the decision to execute or hand off work.

Why this matters

Context can make assistance more useful, but it also makes control more important. People need to understand what is remembered, what a proposal relies on and what their permission allows. PARAF is designed to keep those choices visible as assistance becomes part of everyday work.

How the record works

Keep the basis for a decision in view.

What context is retained?

Make the material used for assistance and its purpose understandable.

What is being proposed?

Distinguish a draft or suggestion from an authorised action.

What permission applies?

Keep the intended use, destination and approval scope together.

What crosses a boundary?

Make any agreed sharing or external service route part of the review.

Who uses it

The same record, seen from every chair.

Individuals

Use relevant context while retaining a clear say over memory, sharing and proposed actions.

Professional teams

Define how shared context supports work and who may authorise its use.

IT and privacy teams

Evaluate storage, access, external dependencies and capability boundaries for the intended setting.

Evaluation

Start with a focused workflow.

Start with a defined assistance workflow. Agree the context it may use, where that context is kept and which permissions are needed before evaluating the experience.

Agree the scope

  • The purpose and retention rules for local memory
  • Permitted capabilities and the people who can approve them
  • External dependencies, sharing boundaries and review requirements
Discuss a pilot

Questions to evaluate together

  • Can people understand what context supports a proposal?
  • Is consent clear about purpose, action and destination?
  • Are local and external boundaries visible before use?

Evidence for the questions that matter.

Evaluate the relevant product and conditions. Request scoped evidence for access, provenance, recovery, human review and offboarding before agreeing a pilot.

Who can access the information?
Ask for the product's access boundaries and applicable isolation tests.
Where does the information come from?
Agree the sources and inspect a representative source-to-record example.
What happens when something fails?
Agree operational ownership and request relevant monitoring and recovery evidence.
What can we review and take with us?
Confirm review history, retention, export formats and offboarding within the agreed scope.
Technical evaluation

For investors and partners

A distinct proposition around agency and trust.

PARAF extends the portfolio from operational records into personal and organisational assistance. Its relevance for investors and partners lies in the relationship between useful memory and deliberate control. A focused evaluation can explore that experience, its boundaries and its practical fit without assuming unrestricted autonomy or universal privacy guarantees.

Partnership discussion

Identity

PARAF brings the Optimized Core emphasis on human judgement and accountable action to intelligence assistance. Its focus is the relationship between useful context, explicit consent and the capabilities people choose to permit.

remember → propose → review → authorise

Useful context. Deliberate consent.

A review stand and poised pen connect to a local-memory cabinet through a visible manual consent control.
PARAF · The consent instrument · Concept illustration

Define assistance on your terms.

Describe your team and the workflow you want to evaluate, with an anonymised example if you like. We discuss scope, connections and readiness before any data is shared.

JPH van Mastrigt · Founder & Technical Director