Let’s talk
Internal IP Programme

Eudaimonia

An AI Mentorship Framework, Documented to Patent Filing

Internal ip programme — no customer

A long-running internal framework for AI mentorship, covering prompt architecture, learning modules, assessment methods and explicit safety boundaries, documented through to patent filings.

Industry
Internal / BrainGenz IP
Location
Internal
The problem

Designing an AI system whose failures affect a person's development rather than a balance sheet requires far more behaviour to be specified in advance, and safety boundaries that hold without a human reviewing every interaction.

  • Developmental failure modes are hard to detect and slow to surface
  • Safety boundaries must hold without per-interaction human review
  • Personalisation across modules multiplies the behaviour to specify
  • Assessment needs a defined method rather than a model's judgement
  • The work has to be documented to a standard that supports IP filing
What we built

A documented framework covering prompt architecture, learning modules, assessment methods and safety boundaries, maintained across versions and platform variants with formal IP documentation.

  • Specify system behaviour and boundaries before implementation
  • Structure personalisation and developmental guidance as separate modules
  • Define assessment methods explicitly rather than leaving them to a model
  • Maintain protocol libraries and curriculum artifacts across versions
  • Document to a standard supporting patent filings and formal entity records

How it was built

Where the stakes are developmental rather than financial

Most of the studio's work has failure modes that cost money. This programme is about systems whose failure modes affect a person's development, which changes what a safety boundary has to do and how much of the behaviour has to be specified rather than learned.

Specification as the deliverable

The output is architecture specifications, prompt systems, protocol libraries and curriculum artifacts across many versions and platform-adapted variants, alongside formal entity and patent documentation. It is the place the studio works out how a system should behave before writing the system.

Where it stands

An internal IP programme, not a product and not a client engagement. No users.

Before
    After
    • A documented framework with patent filings
    • Internal IP programme, with no users
    Stack
    Artifacts
    Architecture specificationsPrompt systemsProtocol librariesCurriculum artifacts
    IP
    Patent filingsFormal entity documentation
    Talk about work like thisBack to the work