Sense: introduction

Hi all,

Just a quick note about one of the projects I've been working on over
recent months...

Draft slides:
https://docs.google.com/presentation/d/1_xrTXd-rgKlmTu2DWe5C491EHqRkoaJXuBzem6ZaKUw/edit#slide=id.p

I am updating the slides to illustrate various updated considerations since
it was first produced, particularly the insights about geometric / vector
db  and related considerations associated with data-structures, as well as
other related considerations / updates...  but it is very much a work in
progress.
fwiw; i find stuff like this interesting,
https://github.com/htm-community
https://www.youtube.com/watch?v=6VQILbDqaI4&list=PLCbmz0VSZ_voTpRK9-o5RksERak4kOL40&index=69

overall, combined, at least in theory - ends-up with something that's
different to existing LLM systems / models / architectures...  but,

The view is that systems need to be able to be exported in more traditional
RDF formats, so that there's backwards compatibility to some form of
existing / emerging standard, like solid.

I envisage there to be many different types of implementations in future,
so the portability considerations, i think, to be important; both, in-terms
of forming a method to support the ability for users to be migrated to
something else for whatever reason, needs a target specification.  Also,
I'm not entirely sure what the broad-ranging capabilities are, in-terms of
migrating off a system...  how many systems, are like - hotel california,

'you can check in any time you like, but you can - never leave'[1]..

which then feeds into (draft) considerations about the other safety reports
/ protocols requirements[2]...  again - a document / documents, i'm working
on updating, originally not intended for the w3c community...  Nonetheless,
I hope the note might be found helpful, as an interim note.

 Timothy Holborn.

[1] https://www.youtube.com/watch?v=09839DpTctU
[2]
https://docs.google.com/document/d/1KwMdyGDPZ-9NZS8EyCreDKf-Px81w0ADZEokKNHZAJw/edit#heading=h.54kz1wuee7pv