Repository navigation
Conversation
OKF (Open Knowledge Format, GoogleCloudPlatform/knowledge-catalog) is a directory tree of markdown concepts with YAML frontmatter, untyped markdown links between them, and a deliberately forgiving conformance. This study maps it onto Cartocortex: a sheet becomes a directory tree (one concept file per topic, children in the directory named after their parent), topicLink and rels become OKF links, and recentring on any subject or note and a general graph view become projections derived from the same bundle. It records what already helps (model.ts, the per-format dispatch in files.ts, presentation mode), what is missing (path identity, directory persistence, a YAML subset parser, a graph layout) and a four-PR path. Study only, nothing is built yet. Agent: Vibe (Mistral, glm-5-latest-short) Relu-par-humain: Martin-PB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
Martin-PB asked for a study based on the OKF specification (Open Knowledge Format v0.2, GoogleCloudPlatform/knowledge-catalog): the compatibility of an OKF-conformant storage, the representation of mindmaps centered on a subject or on a note, and general graph views — with the full journey: start centered on a mindmap, let it evolve into a knowledge graph, then recenter on a new node to present in a meeting.
What was done
A single file:
docs/okf-storage.md, a study only (status "study only — specified, never executed", like the mobile study in PR #7). Conclusions: compatible and a good match — a sheet becomes a directory tree of files (one concept per topic, children in the directory named after their parent),topicLinkandrelsbecome OKF's untyped markdown links, and centering on a subject or a note as well as the general graph view are projections derived from the same bundle, never storage modifications. The study details the field-by-field mapping, what already helps, what is missing (path identity vs UUID, directory vs single-file persistence, a YAML parser, a graph layout), and a four-PR path (OKF reader/writer, derived views, graph view, live bundle).What the agent did
model.ts(Rel,topicLink,float, 16 layouts,searchover text and note,prune, thebranchindex driving presentation colors and steps),files.ts(docBytes/parseDocReportdispatch, atomicwriteSafely,keepsPathfor.jsononly),package.json(v0.1.2, no parsing dependency).docs/mobile-port.md, and verified the round-trip byte by byte after the push (zero mojibake).Human checks
Doc-only from
main: no possible conflict with the stacked PRs; no README line added, to avoid any conflict with PR #7, which touches the same "Not yet" section.Agent: Vibe (Mistral, glm-5-latest-short)
Reviewed-by: Martin-PB