Rawer

Under Construction

there are many to-dos

#

Lark

I'm at desk by 9:50, that me up with the lark.

So much to do...

December, ok. That means I can start danny.ayers.name/todo/2024-12.md. I'm still juggling the todo lists, that file will point to project-specific files like transmissions/todo, and each of these areas has a todo/next-steps.md.

This tells me I need to push #:farelo (project management stuff) up my priorities. That depends to a great extent on my knowledge base. I've got a significant amount of local content-knowledge, but navigating it is painful, I need to get #:semem running.

Sifting the above points me to danny.ayers.name/entries/2024-11-29_carrot.md, writing down the project descriptions and todos quasi-formally (markdown that can be transformed into RDF and used in #:farelo) under danny.ayers.name/projects.

#:todo use the word 'sift' more frequently, it's more visualisable than 'filter' #:todo use the word 'primitives' in #:transmissions docs (I heard it used in a tech podcast I heard 5 minutes of before getting up, it'll be useful)

But first thing today, tidy up some nuts & bolts in #:transmissions.

Before that, I need to get the latest Claude export.

<antArtifact identifier="project-handover" type="text/markdown" title="Resource Ontology Project Handover">

14:17 When I went to my todos, they were lacking structure. So I did a little #:yak around #:MarkMap. Just had a #:dogwalk, back to desk :

Message limit reached for Claude 3.5 Sonnet until 4 PM.

I need to do a bit on #:squirt !!

posters : #:squirt, #:chauvin, #:semem

  • #:fam - refactor for #:transmission - so it uses processors, but has simple.js

  • #:farelo-proximate, update #:trellis, #:foolicious, #:foowiki using #:fam - RDF-Ext inside

Using the RDF vocabularies you know of together with those in your project knowledge, please create an rdf/owl turtle version of the Model Context Protocol schema...

...later : Model Context Protocol Ontology

#

Rees-Mogg

Glorious description of Jacob Rees-Mogg from Matthew Parris on BBC Radio 4 just now :

He was pantomime in the House of Commons.
Bar staff's idea of a gentleman.
A shin-kicker, under the table.
Basically, he's the stupid person's idea of an intelligent person.

Before I got up I did a bit more #:ontops for #:ns related to #:transmissions and all the things. Modeling file access, the aim being to decouple from using a filesystem. Good start, but I'm sick of copy & pasting from Claude. The src/applications/claude-json-converter doesn't yet handle Claude Artifacts, so I've just been moving towards adding support.

I need to pull out the relevant JSON nodes. It's looks like the are `` I'd already made src/processors/json/Blanker.js to give a simple view of confusing JSON structure like Claude's conversations.json. I just got Claude to tweak it to preserve some values. so it'll Ran out of Claude tokens for now. Dogwalk time.

Where the pre() & post() thing?

This needs flagging up better :

| Running >>> :  (SD.p10) BLK a Blanker
* Warn : Processor.getPropertyFromMyConfig(), property not defined : http://purl.org/stuff/transmission/preserve

Ops, a breakage slipped in :

 ./trans claude-json-converter.nop

runs all the transmissions.

:ccc40 a :JSONWalker ;
     trm:configKey :messagesConfig .

#####

     t:MessagesWalker a trm:ServiceConfig ;
         trm:key t:messagesConfig ;
         trm:pointer "content" .

should be :

:ccc40 a :JSONWalker ;
     trm:config :messagesConfig .

#####

     t:messagesConfig a trm:ProcessorConfig ;
         trm:pointer "content" .
  1. TransmissionsBuilder bits?
  2. #:xyz rename trm:ServiceConfig -> trm:ProcessorConfig
:xyz a rpp:Refactoring, rpp:Task ;
     rpp:target :pivotN .

:pivotN a um:Pivot ;
    um:targetDate "2024-12-05" .

#

Scaffold

*I need to do a little Docker tidying. It relates to my #:tbox scaffolding. Also I've a feeling The Scaffold, who sang "Lily the Pink" had some connection with the Liverpool dockers.

Bunch of stuff running that I'd forgotten about. My (very weedy) remote server was falling over thanks to TrustGraph. This desktop machine can run it fine, though doesn't need to right now.

locate wekan
/home/danny/HKMS/wekan/docker-compose.yml
/space/hkms-apps-bits/hkms-apps-from-server/wekan
/space/hkms-apps-bits/hkms-apps-from-server/wekan/docker-compose.yml
...
docker compose -f /home/danny/HKMS/wekan/docker-compose.yml down -v
docker ps

Ok, that just leaves LibreChat, which I'd also forgotten about, but want to use.

I want to add my latest node bits along with Fuseki to the #:tbox container. Claude..!

#

Carrot

In bed activity this morning was developing terms for the #:rpp ontology to cover incentives : carrot & stick.

#:urgent Leonardo mail - I promised Mari I'd do it today, That pushes up some #:home #:services things up the list...

The past week or so I've' a flurry of "new" (sub)projects added to my ToDos. Not exactly new, because they slot nicely into what I have already, but it is a good reminder that I need to nudge on my #:farelo project management bits. Prioritization for productivity, innit.

High on that todo subgraph is capturing project info using #:fam, HTML-form based entry (with auto-generated forms). But deciding which fields to focus on first is tricky. Need more data to inform...

So, #:paliwan, pali wan, kama pini tu, is write some things - from one-line todos to project-level bits down in plain markdown, once I have a few, ask Claude to translate into RDF using #:rpp vocab (later, ask for a script to do the translation automatically - would be a good mini-app for testing a small LLM in #:transmissions).

For now I'll put material under /home/danny/github-danny/hyperdata/workspaces/danny.ayers.name/projects

Ooh, this is rather nice. An extra bird is documenting my projects, high on the todos, this should help lubricate.

I could do with sorting out both the Claude (for artifacts) and GitHub (for project list) #:transmissions

#

MozzPoly

Setting up HAL9000, it asked for a domain name. It'll be running at home, New Place, aka Mozzanella Polytechnic. So I went with mozzpoly.hyperdata.it.

https://github.com/modelcontextprotocol/servers

  • fix laptop

  • Home network

  • CV for Leonardo

  • semem is lightweight, componentized trustgraph

  • fuseki xmpp etc in docker

#:ops distracted - Model Context Protocol! It ties in nicely with the current #:transmissions activity

#:todo write out how I've been using AI, search, everything, myself. Rephrase into a form that AI can help with

#:todo pull runCommand() out of /home/danny/github-danny/transmissions/tests/integration/test_apps.spec.js

#:todo a processor disable flag would be useful (create the instance, just bypass run) - see Claude chat on messaging explain

Model Context Protocol

https://github.com/danja/chauvin.git

/home/danny/github-danny/hyperdata/workspaces/hyperdata/articles/chauvin/about.md

/home/danny/github-danny/hyperdata/workspaces/hyperdata/entries/2024-11-28_mcp-start.md

/home/danny/github-danny/hyperdata/workspaces/hyperdata/todo/mcp.md

I should use /journal under hyperdata for this...

Home Network

  • set up tunnelling to desktop
  • vnc

Transmissions

rpp:Signature? better, trm:

Model Context Protocol

My gut says the server is worth making standalone, at least in the first instance.

https://github.com/danja/chauvin.git

#:todo sort inconsistency in loading from config, some use configKey /home/danny/github-danny/transmissions/src/applications/test_fs-rw/config.ttl uses key something uses the instance URI : preferred

Links