sstorytime

name	SSTorytime
description	read files of N4L notes and create a semantic knowledge store with graph methods based on semantic spacetime and promise theory. TRIGGER when user asks about notes on a certain subject. SKIP when user asks RDF questions.
allowed-tools	Bash, Read, Grep, Glob

SSTorytime

A semantic knowledge store for humans and AI -- compile notes and turn them into a searchable graph

Prerequisites

• go programming language
• latest postgres
• postgres contrib package
• Full functionality requires the webserver http_server to be running

Install

If Linux

• install postgres and postgres contrib packages
• install go language
• install SSTorytime repository

git clone [e-mail]:markburgess/SSTorytime.git
cd SSTorytime
make

• To initialize the database and schema:

make ramdb

• To install the example data provided with the project

 cd examples; make

• To add a single file of notes

 N4L -u MYFILE.N4L

Concepts

• A graph consists of nodes joined by arrows
• Arrows are directed edges in the graph
• Every arrow has an inverse, pointing in the opposite direction
• There are four type of arrow which express different role relationships between the texts:
  • LT (leads to),
    • Use "X (leads to) Y" when X and Y are events that are related by a causal arrow
  • CN (contains),
    • Use "X (contains) Y" when X is a physical thing that contains another physical thing Y
  • EP (express property),
    • Use "X (express property)" Y when X is a concept that contains another concept Y, or when X is a thing or event which has a concept attribute
  • NR (near to)
    • Use "X (near) Y" when X seems similar to Y somehow, e.g. sounds like, is equal to
• Each type of arrow may have many different names, which describe exact meaning
• Search commands are denoted by \command, e.g. \path, \sequence, \chapter

Tools

• Tools are compiled into src/bin of the SSTorytime repository

• To validate N4L file of notes

src/bin/N4L FILE.N4L

• To upload N4L notes:

 src/bin/N4L -u *.N4L

• To wipe entire existing database:

 src/bin/N4L -wipe

• To wipe all data and upload files to replace existing database:

 src/bin/N4L -wipe -u *.N4L

• To remove a single chapter from the database

 src/bin/removeN4L

• To sample 50 percent of a long ASCII text file, like a book, into a single chapter file of notes:

 src/bin/text2N4L -% 50 FILE.txt

This produces FILE.txt_edit_me.n4l

• To start a web interface to the database

- src/bin/http_server

• To obtain a command line text report about graph data.

 src/bin/graph_report -chapter CHAPTER

Workflow

• Step 1: A user writes notes in N4L. The compiler validates file.N4L based on arrows defined in SSTconfig/ directory
• Step 2: User compiles notes with the src/bin/N4L tool and they become a graph.
  • A user writes notes in files called SOMETHING.N4L
  • Use the compiler src/bin/N4L SOMETHING.N4L to validate
  • Upload data by adding flag N4L -u to search and visualize connections
• Step 3: Search the graph, edit notes, and repeat
• Step 4: Go back and edit notes regularly to add new knowledge, improve, and update.

Defining arrows

• The user can define new arrows by editing files in SSTconfig/
• the SSTconfig/directory should be readable in the directory where N4L is called or up to two directories above it

N4L usage

• Create or edit a text file containing lines with fields: first items (arrow) second item (arrow) third item, etc
• Lines may be labelled with @token to refer later as $token.1, $token.2, etc
• The ditto character " may be used to copy the previous line's field
• The $PREV.1, $PREV.2 may also be used to refer to the previous line's fields, as separated by arrows
• Each file is a work in progress. Revisit it regularly to add new comments, relationships, and make edits.

Example N4L for chinese with arrows called (eh), (ph), (he), and (hp) and (e.g.):

english (eh) hanzi (hp) pinyin

place/area/district (eh) 地方 (hp) dìfāng around /nearby/surroundings (eh) 周围 (hp) zhōuwéi (e.g.) wǒjiā zhōuwéi yǒu hěnduō chē (ph) 我家周围有很多车 (he) there are many cars around my house

$PREV.3 is the third item on the previous line

$PREV.3 (e.g.) wǒjiā zhōuwéi yǒu hěnduō shāngdiàn (ph) 我家周围有很多商店 (he) there are many shops around my house

Search Usage

To answer a question from the knowledge graph: call mcp__sstorytime__N4Lquery with the user's query. If the MCP server isn't available, fall back to curl -X POST .../searchN4L -d 'name=...'. Prefer \chapter scoping when the user has mentioned a topic area.

To obtain a Table Of Contents listing chapters and search contexts use

• \toc \limit 50 - for full list of chapters contents

• \toc PATTERN - list chapters matching PATTERN

• There are several independent kinds of search:

  • Random access lookup, match a search pattern

    • unicode text match, using postgres ts_vector or SQL string search

    • Submitting a quoted string to preserve spaces in a search pattern

    • Strings that may contain unicode accents can enclosed in parentheses () to unaccent characters, e.g. "nǐhǎo" can be matched by (nihao)

    • default matches substring of node description

      • use quotes to include spaces in search pattern, e.g. "several word sequence"

    • match whole node description

      • To use postgres ts_vector (okapi BM25 ranked) patterns, e.g. to join neighbouring lexemes separated by space

       strange<->kind<->of<->woman

to skip 2 lexemes

       strange<2>woman

• Use | character to delimit: e.g.

|a1|, "|deep purple|"

• Default searches match against all data in the whole graph
  • To limit any search to a particular chapter,

PATTERN \chapter CHAPTER

• To limit any search to a particular context keywords,

PATTERN \chapter CHAPTER \context CONTEXT

• To see the compiled notes in the exactly as they appear in .N4L files

\notes PATTERN

• To solve for connected paths from start to finish

\from START-NODE \to END-NODE

• To find an expanding cone of paths leaving from a node

\from START-NODE

• To finds a converging cone of paths arriving at a node

\to END-NODE

• To search looks for paths connected by

\sequence PATTERN

Special searches

• To retrieve an arrow definition, use its long or short name, or its arrow number to explain:

\arrow "LONG NAME PATTERN"
\arrow "SHORT NAME PATTERN"
\arrow "ARROW NUMBER PATTERN"

• To retrieve an exact node by its internal key value use (nclass,ncptr), e.g.

(1,14)