@open-automaton/kryten v0.0.1
@open-automaton/kryten
"If you don't GOSUB a program loop, you'll never get a subroutine."
Kryten is a HESL which allows you to create and execute plans of action based on verbal conversations through an LLM running on ollama and generate basic personality and perspective in a deterministic way. While this is a generalized agent system, it's intended use is around generating realistic long term NPC interactions (underneath static options), rather than contributing to the AI hype hellscape. It also supports explicit pattern matching so you can build a fixed set of options and rely on the LLM to be otherwise conversational.
It currently does not support plan evaluation, but will eventually support bidirectional planning (generating it's own work as well as accepting external work).
In addition it will eventually support automated mutation and testing of it's own axiomatic rules through AB experiments (personality modification through experimentation)
It's currently in a pre-alpha state, and only runs in the client, but this will change.
Main Loop
- Natural Language
- extract parts of speech along with:
- actions
- subjects
- sentiment
auto-calibrate grammar
- extract parts of speech along with:
- Ontology and Knowledge Base
RPA
- Automaton
- DuckDuckGo
- bluesky
- npm
- RSS
- RDF/OWL
- json-schema/swagger
- Automaton
Scoring
- aggregation
averaging
- Testing
- AB zscore based testing for long term goal-based self improvement
- AB zscore based testing for long term goal-based self improvement
- LLM
- conversational interaction based on dynamic/programmatic scripting
- produce example plans
Usage
import {
Kryten, Personality, PersonalityComponent
} from '@open-automaton/kryten';
const bot = new Kryten({
voice: {
name:'Zarvox',
pitch: 1.0,
rate: 1.0
},
personality: new Personality({
seed: 'fdfds-fdsfds-dsffzgfsd',
components: [
new PersonalityComponent({
name: 'PrimaryDirective',
text:'You are the robot Kryten from the BBC series Red Dwarf'
}),
...PersonalityComponent.choose([
'agent', 'state'
])
]
});
});
const stop = bot.hesl();
bot.command('terminate', stop);Testing
Run the es module tests to test the root modules
npm run import-testto run the same test inside the browser:
npm run browser-testto run the same test headless in chrome:
npm run headless-browser-testto run the same test inside docker:
npm run container-testRun the commonjs tests against the /dist commonjs source (generated with the build-commonjs target).
npm run require-testDevelopment
All work is done in the .mjs files and will be transpiled on commit to commonjs and tested.
If the above tests pass, then attempt a commit which will generate .d.ts files alongside the src files and commonjs classes in dist
10 months ago